> For the complete documentation index, see [llms.txt](https://pmsgz.gitbook.io/nectar/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pmsgz.gitbook.io/nectar/advanced/web-apis/server-sent-events.md).

# Server-Sent Events API

## Overview

Server-Sent Events API allows web apps to receive a stream of updates from a server over a HTTP connection without resorting to polling.

Unlike WebSockets, Server-Sent Events are a one-way communication channel, ie, the messages flow from server to client only.

Server-Sent Events API can be useful when you have some rapidly updating data to display, but you don't want to poll the server, for example, stock price ticker, scorecard, or live updates.

## Demo

<https://nectar.website/demo/web-apis/server-sent-events/>

## Usage

You can refer to the code present in `/partials/web-apis/server-sent-events.html` file and use it accordingly.

The PHP file which serves the live data is located at `/assets/custom/php/server-sent-events.php`.

## Reference

<https://developer.mozilla.org/en-US/docs/Web/API/Server-sent_events/Using_server-sent_events>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://pmsgz.gitbook.io/nectar/advanced/web-apis/server-sent-events.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.