AIXBT Docs
API v3Reference

List my delivery destinations

GET
/v3/alerts/destinations

Read-only list of destinations connected in product Settings (Telegram, Discord, signed webhooks). Creation, secret rotation, and repair stay in Settings; subscriptions reference these ids.

Authorization

ApiKeyAuth
x-api-key<token>

API key. The Authorization header is accepted as an equivalent carrier. Responses echo the credential class in X-API-Key-Type.

In: header

Response Body

application/json

application/json

application/json

application/json

curl -X GET "https://example.com/v3/alerts/destinations"
{
  "data": [
    {
      "id": "66a10a2b1c9d440000aa0001",
      "kind": "telegram",
      "label": "Team channel",
      "status": "active"
    },
    {
      "id": "66a10a2b1c9d440000aa0002",
      "kind": "webhook",
      "label": "prod ingest",
      "status": "active"
    }
  ],
  "meta": {}
}

{
  "code": "credential_required",
  "message": "Provide an API key via the x-api-key header."
}

{
  "code": "rate_limited",
  "message": "Minute limit reached.",
  "details": {
    "limit": 30,
    "window": "minute"
  }
}
{
  "code": "internal_error",
  "message": "Unexpected error."
}

Update an alert subscription PATCH

Partial update: pause/resume, rename, change cadence, selector, threshold, or destinations. Semantics are identical to creation.

Get the filter vocabularies GET

One discovery surface for every value a v3 filter accepts. Closed vocabularies (grades, sentiments, stances, sort keys, activity modes, rankings, universes, asset types, series measures) are versioned with the contract; catalog-derived sets (project categories, intel categories, chains) are composed from their owning catalogs at read time and carry their own versions.