Reference · built on requestConnectorSupport & service desks

Dixa

Conversations, end users, queues, tags, and SLA events from Dixa through the Dixa API v1 and outbound webhooks.

Request accessPricing ↗

About

Dixa is a conversational customer service platform. It holds conversations across channels, end users, agents and teams, queues, tags, custom attributes, ratings, and internal notes. The Dixa API v1 is served from dev.dixa.io and also exposes analytics, search, business hours, templates, and knowledge.

Through Fibric, an operator reads conversations as webhook events arrive, including the SLA events, checks the end user and queue, and proposes a message, an internal note, a tag, a transfer, or a close for your approval. Calls stay under the per-second and daily quota of the token. Approved actions leave a record of what changed, why, and how to reverse it.

This is a reference listing. It documents what Fibric would read from Dixa and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Conversations through GET /v1/conversations/{conversationId}, search, and the activity log
  • Messages and internal notes on a conversation
  • End users, agents, teams, and queues
  • Tags, custom attributes, and ratings
  • Webhook events: CONVERSATION_CREATED, CONVERSATION_ENQUEUED, CONVERSATION_ASSIGNED, CONVERSATION_MESSAGE_ADDED, CONVERSATION_RATED, and CONVERSATION_CLOSED
  • SLA events: SLA_PENDING, SLA_BREACHED, SLA_ACHIEVED, and SLA_VOIDED
  • Analytics, business hours, and templates

Proposed actions

  • Target capability: propose a message through POST /v1/conversations/{conversationId}/messages
  • Target capability: propose an internal note through POST /v1/conversations/{conversationId}/notes
  • Target capability: propose a tag through PUT /v1/conversations/{conversationId}/tags/{tagId}, or a custom attribute change
  • Target capability: propose a transfer to a queue, a claim, a close, or a reopen
  • Target capability: propose offering a rating on a closed conversation

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Act on an SLA breach

    SLA_PENDING and SLA_BREACHED events arrive by webhook. The operator proposes a transfer to a staffed queue or an internal note with the reason.

    With Breach Watch

  • Route by language

    The operator reads the first message, proposes a transfer to the queue for that language, and tags the conversation.

    With Language Routing

  • Hand off from a chatbot

    When a chatbot conversation stalls, the operator proposes a claim or a transfer to an agent queue with a note summarizing the exchange.

    With Bot Handoff

  • Spot a sentiment spike

    The operator watches CONVERSATION_RATED and message events for a cluster of unhappy replies and proposes a digest to the team lead.

    With Sentiment Spike

Requirements

  • A Dixa organization and an administrator to create API tokens and outbound webhooks
  • An API token with the Dixa API version selected and permissions scoped to the actions the operator needs
  • An outbound webhook under Settings > Integrations > Webhooks, subscribed to the events you need
  • An HTTPS endpoint that checks the shared secret in each event and guards against duplicate event_id values
Authentication
A Dixa API token, created by an administrator under Settings > Integrations > API Tokens, sent as a Bearer token in the Authorization header.

Limits

  • Rate limit is 10 requests per second with a burst of 4, and 864,000 requests per day per token; excess returns 429
  • Webhook delivery order is not guaranteed; use event_id to de-duplicate
  • 4XX responses are not retried; 5XX and network errors are retried up to 3 times at 1-minute intervals
  • After roughly 15 consecutive delivery failures, retries stop until a delivery succeeds

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Dixa ↗

Questions and answers

How is the Dixa API rate limited?
10 requests per second with a burst of 4, and a quota of 864,000 requests per day per token. Requests over the limit receive HTTP 429 Too Many Requests.
What happens when a webhook delivery fails?
A 4XX response is not retried and needs manual attention. A 5XX or network error is retried up to 3 times with 1 minute between attempts. After roughly 15 consecutive failures, retries stop until a delivery succeeds. Events carry an event_id for de-duplication and are not guaranteed to arrive in order.
Who can create an API token?
Only Dixa administrators. Go to Settings > Manage > Integrations > API Tokens, add a token, select the Dixa API version, and scope its permissions. The token is sent as a Bearer token in the Authorization header.
Ask about Dixa

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Dixa through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy