API & webhooks

Open to your ecosystem.

TicketBase is not a walled garden: a REST API with granular scopes, real-time webhooks and the universal integration for external systems connect your ticket system to your ERP, shop, accounting and automation tools.

One API key, and you're running.

Every instance ships its own API at https://<tenant>.repairspot.dev/api. Authentication happens via the X-API-Key header, and you create keys yourself in the settings, including scope selection.

API keys with granular read/write scopes
Webhooks push events in real time (e.g. message.created)
Docs built right into your instance

terminal – curl

# Fetch tickets
curl https://<tenant>.repairspot.dev/api/tickets \
  -H "X-API-Key: YOUR_API_KEY"

# Reply to a ticket via API
curl -X POST https://<tenant>.repairspot.dev/api/tickets/TICKET_ID/reply \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "bodyText": "Your device is ready for pickup." }'

New: universal integration

Your ERP, your shop, your own software. No pre-built connector needed.

The “external systems” interface connects any backend bidirectionally: Odoo, your shop system or software you built yourself. A universal order and customer API instead of vendor lock-in on Shopify & co., built for merchants where shop, ERP and support are separate systems.

Receive events

Your ERP, shop or own software sends signed events to TicketBase. They arrive as ext.* events in automations, or you pass them on to n8n & co.

Live context in the ticket

The context provider queries your system live: order status and customer data from your ERP appear right in the ticket sidebar, so your team sees the full picture while replying.

Trigger actions

Via automation webhooks, TicketBase triggers actions in your system: if-then rules in the ticket system, executed in your backend.

In detail

Integrations without vendor lock-in.

REST API with scopes

API keys get granular permissions (scopes): one key may only read tickets, another may also reply. Write access is locked by default until you explicitly grant it.

Real-time webhooks

Events like message.created are pushed to your endpoint instantly for every new message on every channel, including a flag for whether it opened a new ticket. Status changes and tag events arrive too, including automatic transitions like reopen when a customer replies to a resolved ticket, with machine-readable automatic/reason fields and absolute download URLs.

Automations without code

If-then rules across all channels: conditions like subject, text, channel or customer trigger actions such as priority, tags, assignment, an internal note or a webhook to n8n & co. With an execution log and loop protection.

n8n & Make without code

Webhook in, HTTP request out: TicketBase plays nicely with n8n, Make and similar automation tools. Mirror new tickets into your CRM, for example, or build Slack notifications.

Lexoffice & webhook forwarding

Forward receipts and attachments from tickets straight to Lexoffice for accounting, or to any webhook destination of your choice. Self-service setup, no code changes.

Built-in API documentation

The API docs are built right into your instance, with all endpoints, parameters and examples for your developers.

RepairVision integration

For repair shops: TicketBase connects to the RepairVision workshop software via API key. You get the customer’s ongoing repairs right in the ticket, plus automatic “ready for pickup” notifications via WhatsApp or email. Currently in early access.

Build TicketBase into your workflows.

Create an API key, set up a webhook, go. All self-service, all included in the trial.

Start your 14-day free trial Book a demo

No credit card required · GDPR-compliant · hosted in Germany