Docs API reference
Sign in

Webhook Events

2 endpoints

GET /{account_slug}/webhooks/events

list webhook events

Returns a paginated list of all webhook events for the specified account. Each webhook event includes the event type, state, and associated data.

Requires authentication

Path parameters

Name Description
account_slug string Required The unique slug identifier for your Tito account

Query parameters

Name Description
page integer Page number for pagination (default: 1)
event_slug string Filter by event slug

Response fields

Field Description

Error responses

  • 401 – unauthorized - no bearer token provided or token is invalid

Example request

curl -H "Authorization: Bearer YOUR_API_TOKEN" \
  https://api.pro.tito.io/{account_slug}/webhooks/events
GET /{account_slug}/webhooks/events/{id}

show webhook event

Returns detailed information about a specific webhook event, including the full payload data.

Requires authentication

Path parameters

Name Description
account_slug string Required The unique slug identifier for your Tito account
id string Required The unique identifier for the webhook event

Response fields

Field Description
id integer Unique identifier for the webhook event
webhook_event string The type of webhook event
state string Current delivery state of the webhook event
attempts integer Number of delivery attempts
created_at string Timestamp when the webhook event was created
data object The webhook payload data
data.type string The type of triggerable object
data.id integer The ID of the triggerable object
data.object object The full object data (Order or Ticket)

Error responses

  • 401 – unauthorized - no bearer token provided or token is invalid
  • 404 – not found - webhook event ID does not exist or is not accessible

Example request

curl -H "Authorization: Bearer YOUR_API_TOKEN" \
  https://api.pro.tito.io/{account_slug}/webhooks/events/123
← Previous Tickets

API token

Paste your test-mode API key below to personalise the curl examples on this page. This key is stored only in your browser and is never sent to our servers.