Skip to main content
Tensorlake webhooks send signed HTTPS notifications when sandboxes, applications, and application requests change state. Use them to react to lifecycle changes without polling an API. Each webhook belongs to one project. It receives only events produced by that project and only the event types selected for that destination.

​
Supported events

See the event reference for event names, payload fields, and examples.

​
Create a webhook

1

Prepare an HTTPS endpoint

Your endpoint must accept POST requests over HTTPS. Before processing an event, verify its Svix signature using the destination’s signing secret.
2

Open your project's Webhooks page

In Tensorlake Cloud, select an organization and project, then select Webhooks in the project navigation.
3

Add the destination

Select Create webhook, enter a name and absolute HTTPS endpoint URL, then select at least one lifecycle event.
4

Verify delivery

Open the webhook details page, copy the signing secret, and send a synthetic event with Test webhook.
Only organization administrators and project administrators can create or edit webhook destinations. Project members can view destinations for projects they can access.

​
Delivery contract

Webhook delivery is at least once and is not ordered. The same event can be delivered more than once, and a later lifecycle event can arrive before an earlier one. Design your receiver to:
  • verify the signature before parsing or processing the payload;
  • deduplicate events by the stable event_id;
  • use source_revision and source_ordinal when ordering events from the same producer is necessary;
  • durably record accepted work before returning a 2xx response; and
  • process expensive or failure-prone work asynchronously.
Tensorlake uses Svix to sign messages and deliver them to your endpoint. Svix retries failed endpoint attempts. A successful response from your endpoint acknowledges that delivery attempt; it does not change the underlying Tensorlake resource.

​
Next steps