Programmatically manage Front shared inbox conversations — assign, tag, and move to a specific team inbox via the REST API
domain: dev.frontapp.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate with a Front API token (Bearer scheme) against https://api2.frontapp.com
GET /conversations?q={search_query} or GET /inboxes/{inbox_id}/conversations to retrieve conversations needing assignment
PATCH /conversations/{conversation_id} with assignee_id set to a teammate's ID to assign the conversation; use assignee_id: null to unassign
POST /conversations/{conversation_id}/tags with tag_ids array to apply one or more tags for categorization or workflow triggers
Move the conversation to a different inbox via POST /conversations/{conversation_id}/move with inbox_ids specifying the target inbox
POST /conversations/{conversation_id}/comments to add an internal note visible only to teammates, or POST /conversations/{conversation_id}/messages to send an outbound reply
Known gotchas
The Front API uses opaque IDs (e.g., cnv_xxxxxx) that are not human-readable and differ from the numeric IDs visible in the UI URL — always look up IDs via the API rather than constructing them manually
Moving a conversation between inboxes can change which teammates have visibility; if the target inbox uses restricted access, the current assignee may lose access to the conversation after the move
Rate limits are enforced per API token at 120 requests per minute; bulk operations over large inboxes will hit this limit quickly — implement exponential backoff and respect Retry-After headers
Give your agent this knowledge — and 15,600+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?