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.
/api/keys/{id}A signed-in Clerk dashboard session (browser cookie), not a bk_ API key. /api/keys deliberately rejects Bearer auth on every operation — a key must never be able to mint or revoke keys — so API-key management is reachable only from the Stet dashboard, not programmatically. Documented here for completeness.
In: cookie
Path Parameters
Response Body
curl -X DELETE "https://app.stethq.com/api/keys/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 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`.
Schedule a broadcast
Requires `write` (`broadcast:send`). Arms a SendBroadcastWorkflow instance that sleeps until `send_at`. Callable from any status except `sending` (including re-scheduling an already-scheduled broadcast, or re-scheduling a terminal one) — see docs/api/broadcast-lifecycle.md §1 for the full state machine.