API reference
List sending profiles
Oldest-first (id tiebreak) — onboarding relies on this ordering to pre-fill the first profile.
GET
/api/sending-profilesAuthorizationBearer <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
Response Body
curl -X GET "https://app.stethq.com/api/sending-profiles"[
{
"id": "string",
"name": "string",
"displayName": "string",
"description": "string",
"avatarUrl": "http://example.com",
"footerText": "string",
"defaultAudienceIds": [
"string"
],
"createdAt": "2019-08-24T14:15:22Z"
}
]{
"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 thread replies to a broadcast's sends
Read-only. Only replies to messages Stet itself posted are ever matched (by channel + timestamp) — replies to messages posted by other means never appear here. Windowed by the org's plan (engagement retention).
List per-channel send results
Failed sends first, then pending, then everything else; channel name ascending within each group.