POST /service/{service_id}/publish
Send one or more messages to Fanout subscribers. Each message specifies a channel, and Fanout will deliver the message to all subscribers of its channel.
IMPORTANT: For compatibility with GRIP, this endpoint requires a trailing slash, and the API token may be provided in the Authorization header (instead of the Fastly-Key header) using the Bearer scheme.
Authorization: API token with at least Engineer permissions.
Servers
- https://api.fastly.com
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
service_id |
String | Yes |
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/json" |
host |
String | No |
Request body fields
| Name | Type | Required | Description |
|---|---|---|---|
items[] |
Array | No | |
items[].channel |
String | No | |
items[].formats |
Object | No | |
items[].formats.ws-message |
Object | No | |
items[].formats.ws-message.content |
String | No |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.