Skip to main content
The Replies API gives you full access to your unified inbox — threads from both campaign replies and direct inbound emails. Use it to build custom CRM workflows, automate reply routing, or surface conversation context in your own product.

API Endpoints

All reply endpoints require the replies:read, replies:create, or replies:update scope depending on the operation. Use replies:all to grant full access.

List Conversations

GET /api/public/v1/replies Returns a paginated list of reply threads across your workspace. Supports filtering by campaign, read status, category, and starred state.

Query Parameters

Response Format

Get Thread Details

GET /api/public/v1/replies/threads/{thread_id} Returns full metadata for a thread including lead info, campaign context, and message history.

Get Thread Messages

GET /api/public/v1/replies/threads/{thread_id}/messages Returns the individual messages in a thread in chronological order.

Send a Reply

POST /api/public/v1/replies/threads/{thread_id}/reply Sends a reply within an existing thread. The system automatically routes it through the correct inbox, cancels pending sequences for that lead, and threads the message.

Request Body

Sending a reply automatically cancels any pending follow-up sequences for that lead within the campaign.

Mark Thread as Read

PATCH /api/public/v1/replies/threads/{thread_id}/read Marks a thread as read (or unread). Useful for syncing read state with your own CRM.

Star / Unstar a Thread

PATCH /api/public/v1/replies/threads/{thread_id}/star Toggles the starred state of a thread.

Required Scopes