Overview

Webhooks play a crucial role in the integration cycle by notifying partners whenever an important change occurs within the T-Gate system. These notifications ensure that your application stays updated in real-time, enabling you to respond promptly to various events such as order updates, menu changes, and more. By leveraging webhooks, you can streamline your operations and enhance the overall user experience.

For more detailed information about webhooks, their usage, and how to set and use them in T-Gate, please refer to the General → Webhooks Guide.

📘

Webhooks Response

Webhooks are sent from T-Gate Servers to our Partner APIs. Partners should then respond with a 200 ok status code with no body.

For more details about failures and retry policies, please refer to General → Webhooks Guide.

📘

Webhooks Data

Webhook requests contains only the id and event_type that triggered the webhook, partners should then take the corresponding action according to that event type by fetching newly created entities, re-fetching updated entities or marking the removal of destroyed ones.

For more details on the recommended practices by T-Gate technical team, please refer to Partner API → Best Practices Guides