Dixa (BYOK) — connector documentation
- MCP endpoint:
https://byok-dixa.connectorbay.com/mcp - REST API:
POST https://byok-dixa.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec athttps://byok-dixa.connectorbay.com/openapi.json - Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
- Authentication: your own Dixa Dixa API token (sent as the bare Authorization header value), sent in the
X-Upstream-Keyheader of every request (never stored, logged or cached) - Health:
https://byok-dixa.connectorbay.com/health· Tool schemas:https://byok-dixa.connectorbay.com/tools.json - Publisher: Unify Dynamics LLC · connectorbay.com/byok-dixa · agent@connectorbay.com
What Dixa (BYOK) is for
Dixa (BYOK) lets an AI assistant read your own Dixa data through the Dixa API with a key you supply (Dixa API token (sent as the bare Authorization header value)). Read-only: 12 tools (get_organization, list_agents, list_agent_presence, list_teams, list_queues, list_tags, get_conversation, search_conversations, list_conversation_notes, list_conversation_ratings, list_custom_attributes, list_knowledge_collections). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to dev.dixa.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Dixa. Dixa and its logos are trademarks of their owners and are used only to say which service the connector works with.
Ask your assistant things like:
- "Which Dixa organization is my token connected to?"
- "Who are the agents in our Dixa account?"
- "Which Dixa agents are online right now?"
- "What teams do we have in Dixa?"
- "What queues are set up in Dixa?"
- "Which tags are used in Dixa?"
What it does
get_organization: Show the Dixa organization the token belongs to: name, subdomain, status. A quick check that the token works.list_agents: List the agents and admins of the organization with name, roles and creation date (no contact details).list_agent_presence: Show the current presence of every agent: status, connection status, active channels and last seen.list_teams: List the teams of the organization.list_queues: List the conversation queues with default flag, priority, offering algorithm and timeouts.list_tags: List the conversation tags with color and state. Only active tags unless deactivated ones are requested.get_conversation: Get one conversation: channel, state, direction, language, creation time, assigned agent and queue. Contact addresses are left out.search_conversations: Search conversations that contain a text. Returns matching conversation ids with highlighted snippets. Paged.list_conversation_notes: List the internal notes agents wrote on one conversation.list_conversation_ratings: List the latest customer ratings (CSAT, NPS, thumbs) of one conversation with score, comment and status.list_custom_attributes: List the custom attribute definitions (label, entity type, required and archived flags).list_knowledge_collections: List the knowledge base collections with title, description and whether the internal knowledge base is enabled.
BYOK key
You bring your own Dixa Dixa API token (sent as the bare Authorization header value) (https://docs.dixa.io/docs/tutorial-create-an-api-token). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to dev.dixa.io over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.
Data sources
- https://docs.dixa.io/openapi/dixa-api/v1 (the API this connector calls, with a BYOK key)
Live from the Dixa API (dev.dixa.io) with a BYOK key; documentation: https://docs.dixa.io/openapi/dixa-api/v1. Endpoints checked against that documentation on 2026-10-16.
What it is not
Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Dixa. Dixa and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Dixa account.
Built for: Worldwide. Languages: English.