Inbox
See contact
Returns profile, tags, and activity without direct identifiers.
GET
/inbox/contacts/{id}inbox:readBEHAVIOR
The read looks for the identifier within the account linked to the key and returns 404 when it does not belong to the operation.
EFFECT
Does not change resources or trigger publication.
REPETITION
The operation is safe to repeat. On 429 or 5xx, use exponential backoff with jitter.
Request
idstring · pathResource identifier.minLength 2 · maxLength 100mandatoryAuthorization
Bearer ach_live_...Accept
application/jsonScope
inbox:readExecutable example
curl
curl 'https://achadu.com/api/v1/inbox/contacts/resource_id' \
-H 'Authorization: Bearer ach_live_...' \
-H 'Accept: application/json'Response and errors
Every response includes request_id. Lists add pagination; mutable resources return the persisted state after the operation.
200 application/json
{
"data": {
"id": "conv_01J...",
"channel": "instagram",
"status": "open",
"priority": "normal",
"intent": "find_offer",
"sentiment": "positive",
"unread_count": 1
},
"request_id": "req_01J..."
}200Operation completed.400Invalid parameter, body or transition.401Missing, invalid, expired or revoked key.402The account plan does not release this interface.403A chave precisa do escopo inbox:read.404Feature does not exist in this account.409The current state prevents this operation.413The JSON body exceeds 128 KB.429The 120 requests per minute window has been exceeded.