post
https://your_server_endpoint/your_opening_hour_group_webhook_uri
Recent Requests
Log in to see full request history
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Loading…
Event Types
Opening Hour Group webhooks can be of any of the following event types:
| Event Type | Description |
|---|---|
| opening_hour_group.update | a critical information related to an opening_hour_group changed which requires a partner data re-fetch |
Changes That Trigger Webhook Updates
T-Gate Webhooks are only meant to be sent in case of critical updates which would affect the creation of orders.
Below is a list of all Critical updates that triggers the opening_hour_group.update webhook.
| Entity Change | Description |
|---|---|
| is_force_closed | For Branch Special Timings, Force closure of an opening_hour_group which means that it has no effect on any of the entities its assigned on. (ON/OFF) |
| start_date | For Branch Special Timings, changes in the start_date of an opening_hour_group |
| end_date | For Branch Special Timings, changes in the end_date of an opening_hour_group |
| opening_hours | Changes in intervals, time_range or week_days which reflects on the create, update or destruction of the opening_hours Array of object of an opening_hour_group. |
Opening Hour GroupsT-Gate does not send webhooks for the creation or destruction of an opening_hour_group as they are always connected to other entities. If an entity, such as a branch, assigns an opening_hour_group, it will automatically become available for fetching, and update webhooks will be activated. Conversely, if all entities unassign an opening_hour_group, it will no longer be available.