Webhooks
Get notified when a project's translations change, instead of polling. Register an HTTPS endpoint, subscribe it to the events you care about, and TextSetu POSTs a signed payload whenever one occurs. Payloads follow the Standard Webhooks spec — verify the webhook-signature header with any compatible library. Delivery is at-least-once and unordered, so treat webhook-id as an idempotency key. Failed deliveries are retried five times over roughly seven hours, and every attempt is inspectable and replayable via the delivery log.
List subscribable event types
The catalog of events an endpoint can subscribe to, with a short description of when each fires.
List webhook endpoints
Every webhook endpoint registered on the project.
Create a webhook endpoint
Register an HTTPS URL to receive the events you subscribe it to. TextSetu generates a signing secret and returns it once.
Get a webhook endpoint
Fetch a single endpoint's configuration and health.
Update a webhook endpoint
Change the URL, description, event subscription, or enabled state. The signing secret is untouched — use the rotate endpoint for that.
Delete a webhook endpoint
Remove the endpoint. Its delivery history is removed with it; export anything you need first.
Rotate the signing secret
Issue a new signing secret. The previous secret keeps working for a grace period so you can roll over without dropping deliveries.
Send a test event
Queue a `ping` event so you can confirm the endpoint is reachable and your signature verification works before relying on it.
List webhook deliveries (paginated)
The delivery log — every attempt to send an event to an endpoint, with its outcome. Filter by endpoint, event type, or status.
Get a webhook delivery
A single delivery including the exact payload sent and the endpoint's response.
Replay a delivery
Re-send a past delivery's original payload — useful after fixing an outage on your side.