Retry one failed send
Requires `write` (`broadcast:send`). Direct guarded re-post through the same rate-limited path the pipeline uses (not a workflow re-enqueue) — see docs/api/broadcast-lifecycle.md §4. The send must currently be `failed`.
/api/broadcasts/{id}/sends/{sendId}/retryA 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
Response Body
curl -X POST "https://app.stethq.com/api/broadcasts/string/sends/string/retry"{
"retried": 0,
"status": "empty"
}{
"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"
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string"
}Retry every failed send
Requires `write` (`broadcast:send`). Same direct guarded re-post path as the single-send retry, fanned out with a concurrency cap of 5. `retried: 0` (with `status: null`) when there was nothing to retry.
Revoke an API key
**Dashboard-session only** — this operation does not accept `bk_` Bearer auth. Requires capability `apikey:manage` (Admin role). Sets `revokedAt`; the row is kept (not deleted) for audit history.