API reference
List per-channel send results
Failed sends first, then pending, then everything else; channel name ascending within each group.
GET
/api/broadcasts/{id}/sendsAuthorizationBearer <token>
A Stet API key (prefix bk_), created under Settings → API keys. The whole API requires the Growth plan or higher; keys are scoped read or write — composing and sending require write.
In: header
Path Parameters
idstring
Response Body
curl -X GET "https://app.stethq.com/api/broadcasts/string/sends"{
"sends": [
{
"id": "string",
"channelId": "string",
"slackChannelId": "string",
"channelName": "string",
"audienceName": "string",
"status": "pending",
"errorMessage": "string",
"sentAt": "2019-08-24T14:15:22Z",
"slackTs": "string",
"permalink": "string",
"replyCount": 0,
"reactionCount": 0
}
],
"summary": {
"delivered": 0,
"failed": 0,
"pending": 0,
"total": 0
}
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string"
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string"
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string"
}List sending profiles
Oldest-first (id tiebreak) — onboarding relies on this ordering to pre-fill the first profile.
Render the Slack Block Kit preview
Read-only — the exact render the send pipeline would post. Either `aggregate=1` (the union across every targeted audience, annotated with per-block visibility) or `audience_id` (one audience's exact render) is required; `audience_id` must be an audience actually targeted by this broadcast.