Tableo Restaurant API
Webhooks

Send a test webhook delivery

Sends a synthetic webhook.ping event to the webhook's URL, regardless of which event types it is subscribed to via events[].

The delivery is signed with the webhook's secret and recorded in the delivery history (visible via GET /api/restaurant/webhooks/{webhook_id}/deliveries), so you can use it to verify that your endpoint is reachable, that signature verification works end-to-end, and that 2xx responses are recorded.

webhook.ping is NOT a subscribable event — it can only be produced by this test endpoint.

POST
/api/restaurant/webhooks/{webhook_id}/test

Authorization

bearerAuth
AuthorizationBearer <token>

Supports two token types:

  1. Restaurant tokens — API tokens with restaurant-api ability, issued per restaurant.
  2. User tokens — Personal access tokens with mobile-access ability (e.g. for the mobile app). When managing multiple restaurants, include X-Restaurant-Id: <id> header.

In: header

Path Parameters

webhook_id*integer

Webhook subscription ID.

Response Body

application/json

application/json

application/json

curl -X POST "https://devrms.tabdevx.com/api/restaurant/webhooks/0/test"
{
  "data": {
    "delivery_id": 99,
    "event_id": "evt_ping_770e8400-e29b-41d4-a716-446655440099",
    "event_type": "webhook.ping",
    "status": "pending",
    "target_url": "https://api.example.com/webhooks/tableo"
  }
}
{
  "error": {
    "code": "string",
    "message": "string",
    "details": {}
  },
  "meta": {
    "timestamp": "2019-08-24T14:15:22Z"
  }
}

{
  "error": {
    "code": "NOT_FOUND",
    "message": "Booking not found.",
    "details": null
  },
  "meta": {
    "timestamp": "2026-03-18T10:00:00Z"
  }
}