Tixallo
Developers

Tixallo API Documentation

Integrate tickets, customers, companies, conversations, inboxes and webhooks into your own product, internal tools or back-office automations.

What you can build

The Tixallo API is a JSON-over-HTTPS interface for support data. Every workspace has its own API keys and sees only its own tickets, customers and conversations. Use it to keep tickets in sync with your own product, push events from third-party tools, or back office your help-desk operations into a data warehouse.

Common integrations include creating tickets from your product's in-app forms, mirroring customer records from your CRM, posting replies from automation pipelines, and reacting to ticket events via webhooks.

Where to start

If you're new to the API, read the two short pages below in order. They cover the base URL, the headers every request needs, and how API keys work.

Getting started

Base URL, required headers, and a five-step workflow from sign-up to your first API call.

Authentication

Bearer token authentication, key handling, rotation and what to do if a key is exposed.

API reference

Every live v1 endpoint with request bodies, responses, and what's planned vs app-managed.

Examples

Copy-paste snippets in curl, Node.js and Python for every live endpoint.

Webhooks

Events Tixallo dispatches, payload shape, signature verification and retry policy.

Error handling

Status code matrix, the current error response shape, and when to retry.

Rate limits

Per-key budget, the 429 response, and Node/Python backoff examples.

Resources at a glance

  • Tickets — list, fetch and create tickets, and post messages onto an existing conversation.
  • Customers — created and resolved automatically by email when you create tickets; customer details are returned alongside ticket payloads.
  • Companies — surfaced on the customer object so you can group tickets by account.
  • Conversations — every ticket has an ordered list of public messages exchanged with the customer.
  • Inboxes — managed in the Tixallo app; tickets created via the API land in your default workspace inbox.
  • Webhooks — Tixallo fires events such as ticket.created and ticket.message.created to URLs you configure inside the app.

A 30-second taste

List your most recent tickets:

curl https://tixallo.com/api/v1/tickets \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json"

You'll receive a JSON object with a data array of ticket records. Internal notes are never returned over the public API.

Manage your API keys in Tixallo

API keys are scoped to a single workspace and are created and revoked from inside the Tixallo app. Treat them like passwords — never embed them in front-end code or commit them to source control.

Create a Tixallo accountSign in