Chimely
Api

Read own preferences

GET
/v1/inbox/preferences

Authorization

SubscriberEnv SubscriberHash SubscriberId
X-Chimely-Environment<token>

In: header

X-Chimely-Subscriber-Hash<token>

Optional when the environment has require_subscriber_hash = false.

In: header

X-Chimely-Subscriber<token>

In: header

Response Body

application/json

application/json

curl -X GET "https://example.com/v1/inbox/preferences"
{
  "preferences": [
    {
      "category": "string",
      "channel": "in_app",
      "enabled": true
    }
  ]
}
{
  "error": {
    "code": "invalid_request",
    "message": "string"
  }
}

Status timeline for one notification GET

The append-only delivery timeline — the "did it send?" answer. Statuses appear as they happen: `created` (accepted and durable), `delivered_hint` (a real-time hint announcing it was published), `seen` and `read` (subscriber actions; watermark moves apply them asynchronously, so a just-clicked "mark all read" may take a moment to appear here). Entries are ordered by `occurred_at`. Unknown future statuses must be ignored by clients. Broadcasts have no per-recipient timeline (they are never materialized per subscriber).

Read a subscriber's preferences (admin) GET

Next Page