stet
API reference

Check for audience/channel conflicts

Read-only. The same conflict check `schedule` and `send-now` run before dispatch — a channel reached by two-or-more targeted audiences with differing visible blocks for that channel.

GET/api/broadcasts/{id}/validate

Authorization

AuthorizationBearer <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/validate"
{
  "conflicts": [
    {
      "channelId": "string",
      "channelName": "string",
      "audienceIds": [
        "string"
      ],
      "audienceNames": [
        "string"
      ],
      "reason": "differing_blocks"
    }
  ]
}
{
  "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"
}

Upload a sending-profile avatar image

Requires `write` (`sending_profile:manage`). NOTE: this endpoint takes no `{id}` — it is a standalone upload that returns a URL; pass that URL as `avatarUrl` on a create/update call to attach it to a profile. PNG, JPEG, WebP, or GIF; max 2MB.

MCP server

Install and connect the Stet MCP server, `@stethq/mcp`.