General Settings
General Settings
Breadcrumbs

Webhooks

Webhooks are a form of integration between systems that allows the automatic sending of information from one application to another in real-time, whenever a specific event occurs. This tool automates processes and connects the platform to other solutions you use in your business, ensuring instant communication between systems whenever important actions occur, such as a new sale, status update, or subscription cancellation, without the need for manual queries or additional processes.

In Guru, you can configure webhooks for subscriptions, e-tickets and sales according to your operation's needs, defining what data you want to send, where to send it, and in what situations. Additionally, you can:

  • Create multiple webhooks for subscriptions, e-tickets and sales and configure them to send subscription, e-ticket, and sales data to your own app or system; and

  • Configure the rules for sending your webhooks, such as destination URL, sending status, products or marketplaces to which you want to associate the webhook, and the number of simultaneous sends.

After configuration, the trigger happens automatically as soon as the event occurs, keeping your integrations active, your systems synchronized, and operational workflows running without manual intervention.

This feature is useful when you need to update data in another system and/or take action according to the status of the subscription, e-ticket, or sale in question, ensuring that the destination system receives all necessary information securely and organized.

If desired, you can configure a URL, i.e., the webhook deactivation to receive a notification if any webhook is automatically deactivated.

How the webhook works

When a subscription, e-ticket, or sale is updated, Guru sends1 a POST type request to the configured URL containing all data related to the element that underwent the change.

The data is sent in JSON format and must be correctly read and interpreted by the destination application. Consult the developer documentation to learn more.

The webhook only sends the information. The destination system or application is responsible for interpreting and taking the necessary actions according to the information received in the post.

Important: the number of webhooks sent per client will be simultaneously 40.

Multiple sends of the same subscription, e-ticket, or sale may occur even if the status has not changed, as it may undergo different updates from the payment processor.

Guru checkout fields sent in the Webhook:

  • src no checkout = trackings.source in the webhook;

  • sck no checkout = trackings.checkout_source in the webhook;

  • utm_X no checkout = trackings.utm_X in the webhook.