post
https://your_server_endpoint/your_branch_webhook_uri
Recent Requests
Log in to see full request history
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Loading…
Event Types
Branch webhooks can be of any of the following event types:
| Event Type | Description |
|---|---|
| branch.update | a critical information related to a branch 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 branch.update webhooks.
| Entity Change | Description |
|---|---|
| is_force_closed | Force closure of a branch (ON/OFF) |
| timezone | Timezone change, as it affects the working hours of a branch |
| currency | Currency change, as it affects ordering price. |
| Address | Address change, since a branch is a physical entity. |
| services | Changes like creation of a new service, updating an existing one or removing a service from a branch triggers the branch webhook |
| force_closed_in_brands | Changes in the force_closure under a certain brand (ON/OFF). |
Additional AttributesChanges on other attributes such as name, logo...etc do not trigger webhooks and it's the responsibility of a partner to check for updates on them.