Streaming API Developer Guide

Getting Started with Streaming API
Code Examples
Client Connection Considerations
Clients and Timeouts
Clients and Cookies for Streaming API
Supported CometD Versions
Streaming API Calls Blocked by Security Settings
Debugging Streaming API Applications
Using an Experience Cloud Site with Streaming API-Based Features
PushTopic Events (Legacy)
Generic Events (Legacy)
Monitoring Event Usage
PDF

Note: This release is in preview. Features described here don’t become generally available until the latest general availability date that Salesforce announces for this release. Before then, and where features are noted as beta, pilot, or developer preview, we can’t guarantee general availability within any particular time frame or at all. Make your purchase decisions only on the basis of generally available products and features.

Using an Experience Cloud Site with Streaming API-Based Features

If you use an Experience Cloud site and enable features that use Streaming API in the background, such as in-app or push notifications, HTTP POST requests are sent to the /cometd/ endpoint. Sending many CometD requests can be problematic sometimes and can cause hitting HTTP request rate limits. If your Experience Cloud site is hosted on a third-party Content Delivery Network (CDN), the HTTP POST requests will be sent to the CDN. The volume of requests depends on the number of users that are simultaneously logged in to the site. Each logged-in user gets their own Streaming API session so the more users are logged in, the more POST requests are generated.