Webhooks

Webhooks let your server react to what happens in Tiquo without polling the Admin API. When an event you subscribe to happens, such as a new order, a confirmed booking or a paid membership, Tiquo sends an HTTPS POST request with a signed JSON payload to the endpoint URL you choose.

Use webhooks to sync Tiquo with your own systems, trigger internal workflows, or keep a data warehouse up to date.

How it works

1. You add an endpoint URL in Settings > Webhooks and choose the events it receives.
2. Tiquo gives you a signing secret for that endpoint.
3. When a subscribed event happens, Tiquo sends a POST request to your endpoint. The request body describes the event, and its tiquo-signature header lets you confirm it came from Tiquo.
4. Your endpoint replies with a 2xx status. If it doesn't, Tiquo retries the delivery for about 44 hours.

Payloads carry IDs and key fields rather than full records. To get everything about an order or customer, call the Admin API with the ID from the payload.

Before you start

• Permission: managing webhooks needs the Manage API keys permission, the same permission as Settings > Admin API.
• Endpoint: your endpoint must use HTTPS and be reachable on the public internet. Tiquo doesn't send to localhost, private network addresses, or URLs that include a username or password, and it doesn't follow redirects. See endpoint requirements.

Add a webhook

1. Open your Tiquo dashboard.
2. Go to Settings > Webhooks.
3. Select Add webhook.
4. Enter a name and the endpoint URL.
5. Choose the events this endpoint should receive. See Events.
6. Optionally add custom headers, for example an Authorization header your endpoint expects.
7. Select Create webhook.
8. Copy the signing secret. It is shown only once.

Then select Send test from the webhook's menu. Tiquo sends a webhook.test event so you can check that your endpoint receives and verifies requests:

{
  "id": "evt_test_1794185870123",
  "type": "webhook.test",
  "created": "2026-11-13T10:15:02.123Z",
  "data": {
    "message": "Test webhook from Tiquo",
    "webhookId": "pn8hpmdry7g3mjmj3hgex83rhs8hx42s",
    "webhookName": "Production sync"
  }
}

The request Tiquo sends

Every delivery is a POST with a JSON body and these headers:

Any custom headers you added are sent too. The names above are reserved, so custom headers can't use them.

Manage webhooks

Each webhook in Settings > Webhooks shows its endpoint, events, status, and how many deliveries succeeded and failed. From its menu you can:

• Send test: send a webhook.test event.
• Edit: change the name, URL, events, and custom headers.
• Rotate secret: create a new signing secret. The old secret stops working immediately, so update your endpoint straight away.
• Delete: remove the webhook. Deliveries still waiting to be sent are cancelled.

The switch beside each webhook pauses or resumes it. A paused webhook receives no events, and retries already scheduled for it are cancelled.

Recent deliveries lists the latest 50 delivery attempts across your webhooks, with each one's HTTP status and any error. Select Replay to send that event again. Replay is available while the webhook is on and the event is less than 30 days old. See Delivery and retries.

Custom header values

Custom header values are stored encrypted and aren't shown again after you save them. When you edit a webhook, leave a header's value blank to keep the saved value, or type a new one to replace it.

Zapier webhooks

When you turn on a Zap that uses a Tiquo trigger, Zapier creates a webhook for it automatically. These webhooks are marked Managed by Zapier and can't be edited, paused, rotated, tested, or deleted from Tiquo. Turn the Zap off or delete it in Zapier to remove its webhook.

Limits

To send several kinds of event to the same system, subscribe one webhook to all of them rather than creating a webhook per event.