Read a conversation thread
Reads the live message thread for one fan, normalized to a stable shape. Message bodies are not stored on our side; they are re-read live at request time. If the underlying read fails the response degrades to an empty list with error=true instead of failing. Requires a read-scoped key.
Authorization
bearerAuth Your al_live_<prefix>_<secret> API key. Mint and manage keys in the dashboard.
In: header
Path Parameters
Identifier of the fan whose thread to read.
Query Parameters
Maximum number of messages to return (most recent).
1 <= value <= 10050Response Body
application/json
application/json
curl -X GET "https://example.com/api/admin/inbox/conversations/string/messages"{ "messages": [ { "msg_id": "m_55120", "ts": 1719762000, "direction": "in", "text": "hey are you online?", "price_cents": 0, "is_opened": false, "can_purchase": false, "media": [] }, { "msg_id": "m_55121", "ts": 1719762600, "direction": "out", "text": "just for you 💋", "price_cents": 1500, "is_opened": true, "can_purchase": false, "media": [ { "id": "med_771", "type": "photo" } ] } ], "error": false, "fan_id": "fan_8841920"}{ "detail": "Not authenticated"}List inbox conversations
Returns the unified DM inbox thread list for your account, ordered waiting-first (fans awaiting a reply rise to the top, longest wait first, then the rest by most-recent activity). Requires a read-scoped key.
Compose a 1-on-1 inbox message
Queues a single direct message to one fan. Every outbound is screened and paced before delivery; live delivery is gated and currently runs in shadow mode (intent is recorded, nothing is delivered). The response status is 'sent', 'shadow', or 'blocked'. Requires a write-scoped key.