Keep customer conversations organized, with shared profiles and team notes.
Inbox API
Read customer conversations, add internal notes, send replies and update conversation status from your own code.
Getting started
Read conversations, add team notes and update their status from your own tools.
curl "https://enoughstack-app-7r9ib.ondigitalocean.app/api/public/v1/inbox/conversations?status=open&channel=email&limit=50" \ -H "Authorization: Bearer $ENOUGHSTACK_API_KEY"
curl -X POST https://enoughstack-app-7r9ib.ondigitalocean.app/api/public/v1/inbox/conversations/con_123/messages \
-H "Authorization: Bearer $ENOUGHSTACK_API_KEY" \
-H "Content-Type: application/json" \
-d '{"kind": "note", "body": "Investigating the export issue."}'Notes stay internal. Use kind: "reply" to reply to the customer; email replies require the configured, verified Inbox sender and an expected_reply_to address matching the conversation.
Inbox conversations
- GET
/inbox/summaryOpen and unread counts, response time and satisfactioninbox:read - GET
/inbox/conversationsPage through conversations; filter by status, channel, unread or qinbox:read - GET
/inbox/conversations/{conversation_id}One conversation with its messages and customerinbox:read - PATCH
/inbox/conversations/{conversation_id}Change its status or unread stateinbox:write - POST
/inbox/conversations/{conversation_id}/messagesSend a reply or add an internal noteinbox:reply - GET
/inbox/conversations/{conversation_id}/attachments/{attachment_id}Download a conversation attachmentinbox:read
Inbox email and messenger settings
- GET
/inbox/email/settingsGet Inbox email settingsinbox:read - PUT
/inbox/email/settingsSet the Inbox senderinbox:manage - POST
/inbox/email/verifySend an Inbox forwarding verification emailinbox:manage - GET
/inbox/messengerGet Inbox messenger settingsinbox:read - PUT
/inbox/messengerConfigure the Inbox messengerinbox:manage
API keys
Workspace requests carry a key with the specific permission listed for each action. Create keys, narrow existing permissions and set expiration under Developers. Full keys are shown once.
Manage API keysInteractive docs
Every endpoint with request and response schemas, generated from the API itself. Use “Authorize” with one of your keys to try requests.
Open API docsConventions
- Scopes
- OpenAPI marks each authenticated operation with
x-required-scope, such asemail:draft,email:sendorinbox:reply. A key needs the permission listed for that operation. - Errors
- Always
{"error": {"code": "...", "message": "..."}}. Codes includeunauthenticated,insufficient_scope,not_found,validation_error. - Pagination
- Lists return
paging.next; pass it back asstarting_after. Up to 100 items per page. - Operation outcomes
- Mutations return
X-Operation-IDandOperation-Locationheaders. Follow the operation URL to inspect progress, errors and the resulting resource. Provider accepted means a provider accepted the request; delivered requires delivery evidence. - Webhooks
- Queued deliveries run in the background with signed HTTPS requests and retries. Delivered means the endpoint returned a successful HTTP response. Unknown means acceptance could not be confirmed; simulated means no request was sent. Receivers should deduplicate by event ID.
- Versioning
- The version is in the path (
/v1). Fields are only ever added.
Recorded webhook delivery
{
"id": "dlv_001",
"webhook_id": "wh_001",
"event": "contact.created",
"event_id": "evt_001",
"status": "queued",
"response_code": null,
"duration_ms": null,
"attempt_count": 0,
"max_attempts": 5,
"payload": {
"id": "ct_0231",
"list_id": "lst_audience",
"email_address": "maya@northwind.studio",
"status": "subscribed",
"tags": ["customer", "team"]
},
"at": "2026-10-06T09:14:02Z"
}