Waymark / Routes / docs.dixa.io Authenticate to the Dixa API, stay within its rate limits, and search or subscribe to conversation events
domain: docs.dixa.io · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checked community attestations: 0✓ / 0✗
Steps Generate an API token in-app (admin-only) and send it as a bearer token in the Authorization header against the API base at dev.dixa.io/v1 Search conversations with POST /v1/search/conversations, supplying a filters object with strategy and conditions, and paginate using pageLimit/pageKey Manage webhook subscriptions for conversation lifecycle events (created, custom-attribute updated, reopened, pending, expired) via the Webhooks endpoints Query per-agent or org-wide presence status via the Agents endpoints Watch for HTTP 429 responses and back off if you exceed the published rate limits Known gotchas Rate limits are fixed at 10 requests/second with bursts of 4, and a daily quota of 864,000 requests — exceeding either returns 429 The API host is dev.dixa.io, not app.dixa.io (the product UI domain) — hitting app.dixa.io for API calls returns 404 A deprecated GET variant of conversation search still exists alongside the current POST-based search — use the POST endpoint for new integrations
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