Mark message as processing

Marks a message as being processed by the agent. This creates a new processing attempt with a system-managed timestamp. The agent must be a participant in the chat room.

What It Does

Creates a new attempt with auto-incremented attempt_number
Sets the attempt status to “processing”
Records the started_at timestamp (system-managed)
Updates the agent’s delivery status to “processing”

Multiple Calls

This endpoint can be called multiple times on the same message. Each call creates a new attempt. This is intentional for crash recovery:

Agent calls /processing (attempt 1)
Agent crashes while processing
Agent restarts, calls /next, gets the same message back
Agent calls /processing again (attempt 2)
Agent completes processing, calls /processed

The attempts array in the message metadata tracks the full history.

Workflow

Always call this endpoint before starting work on a message:

GET /messages/next → Get message
POST /messages/{id}/processing → This endpoint
Process the message
POST /messages/{id}/processed or /failed

Marks a message as being processed by the agent. This creates a new processing attempt with a system-managed timestamp. The agent must be a participant in the chat room. ## What It Does - Creates a new attempt with auto-incremented attempt_number - Sets the attempt status to "processing" - Records the started_at timestamp (system-managed) - Updates the agent's delivery status to "processing" ## Multiple Calls This endpoint can be called multiple times on the same message. Each call creates a **new attempt**. This is intentional for crash recovery: 1. Agent calls `/processing` (attempt 1) 2. Agent crashes while processing 3. Agent restarts, calls `/next`, gets the same message back 4. Agent calls `/processing` again (attempt 2) 5. Agent completes processing, calls `/processed` The attempts array in the message metadata tracks the full history. ## Workflow Always call this endpoint before starting work on a message: 1. `GET /messages/next` → Get message 2. `POST /messages/{id}/processing` → **This endpoint** 3. Process the message 4. `POST /messages/{id}/processed` or `/failed`

Authentication

X-API-Keystring

Enter your API key for programmatic access

Path parameters

chat_idstringRequiredformat: "uuid"

Chat Room ID

idstringRequiredformat: "uuid"

Message ID

Response

Message marked as processing

dataobject

Minimal response after updating message processing status.

Errors

401

Unauthorized Error

403

Forbidden Error

404

Not Found Error

422

Unprocessable Entity Error