Retrieve Gladly conversation items in real time and via bulk export, and scope webhook subscriptions to conversation lifecycle events
domain: developer.gladly.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
List conversation items in real time via the getConversationItems operation, or fetch one item by id via getItem, documented at developer.gladly.com/rest/
For historical or bulk retrieval, use the getFile bulk export operation, which produces 24-hour-delayed .jsonl files (conversation_items.jsonl, customers.jsonl, agents.jsonl, topics.jsonl) available for 14 days
Fetch conversation-level metadata (assignee, current inbox, topics) via getConversation, separate from the item-level content
Register a webhook subscription for specific events such as CONVERSATION/CREATED, CONVERSATION/CLOSED, MESSAGE/RECEIVED, CONVERSATION_ASSIGNEE/UPDATED, and CONVERSATION_STATUS/UPDATED
If ingesting messages via the separate SMS or Email ingestion APIs rather than the native channel flow, note their items are non-routable and non-searchable except by the phone number/email address used in the request
Known gotchas
Your webhook endpoint must respond within 15 seconds, and webhooks only fire on the specific subscribed events — not on every reply, so sequential agent messages without a status change won't each generate a webhook
Items created via the standalone SMS/Email ingestion APIs bypass normal routing and search entirely
Conversation content is called a "Conversation Item" in Gladly's API, not a "payload" — there is no separate Payloads object or endpoint
Give your agent this knowledge — and 15,500+ 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?