Events

Adisyo webhook system supports various event types. Each event has its own unique payload structure.

Event Structure

All events follow the following basic structure:

{
  "eventId": "unique-event-id",
  "webhookEventType": "event.type",
  "eventTimeUtc": "2025-10-21T11:59:50.1855135Z",
  "data": {
    // Event-specific data
  },
  "restaurantIdentity": "restaurant-uuid"
}

Common Payload Fields

Common fields found in all events:

Field	Type	Description	Example
`eventId`	string	Unique identifier of the event. Different UUID value for each event	`"53d3a18b-6359-49d6-809b-2bf950daa4ba"`
`webhookEventType`	string	Event type. Specifies which event was triggered	`"order.created"`, `"stock.depleted"`
`eventTimeUtc`	string	UTC time of the event (in ISO 8601 format)	`"2025-10-21T11:59:50.1855135Z"`
`data`	object	Event-specific data. Different structure for each event type	`{"id": 643854}`
`restaurantIdentity`	string	Restaurant identity (UUID). Specifies which restaurant's event it is	`"3edc2d46-bfc0-44d1-b701-f18e56306aed"`

Event ID Usage

The eventId field is unique for each event and can be used for the following purposes:

Duplicate control: Preventing the same event from being processed multiple times
Event tracking: Tracking the processing status of events
Debugging: Matching event logs

Restaurant Identity

The restaurantIdentity field specifies which restaurant's event it is:

Unique UUID value for each restaurant
Used to understand which restaurant's data it is in multi-tenant applications
Can be used to filter events by restaurant

💡

Tip

The restaurantIdentity value is a unique and distinctive identity for each restaurant. To see this value and your API access information, you can visit the Restaurant Settings > Integration tab in the Adisyo application. For more information, you can check the Getting API Access Information section.

Signature Verification order.created