Developer Overview

Everything on the rest of this site is written for server owners and staff who configure TicketWave through the dashboard. This section is different.

These pages are written for developers. They assume you can run a small web service, read JSON and are comfortable with a terminal. You do not need any of this to use TicketWave.

Do I need this section?

You want to…	Where to go
Set up ticket categories, panels or logging	Dashboard Guides
Look at ticket history and analytics	Dashboard Guides
Get a Discord notification when a ticket opens	Log Channels
Push ticket events into your own app, CRM or database	This section
Trigger a Zapier / n8n / Make automation	This section

The short version: if the destination is Discord, use Log Channels. If the destination is your own code, use webhooks.

What is available

Webhooks

Receive ticket events as HTTP requests in real time

Event Reference

Every event type and its exact payload

Example Server

A complete, runnable Express receiver

Webhooks are a premium feature. You can read these pages and build against them at any time, but a server needs premium before TicketWave will deliver events to it.

Ground rules

A few things hold true for everything in this section:

HTTPS only. Plain http:// endpoints are rejected.
Public hosts only. Private, loopback and link-local addresses are refused, so localhost will not work while developing — see the tunnelling note.
Verify signatures. Every request is signed. If you do not check the signature, anyone who learns your URL can post fake tickets into your system.
Answer fast. Do your real work after you reply, not before.

Next Steps

Webhooks (How delivery, signing and retries work)
Event Reference (The payload of every event)
Example Server (Copy, run, receive)

Overview