Receive Events with Webhooks
Everything the platform does is an Event; a Webhook brings them to your endpoint.
Every noteworthy occurrence – an Identity becomes ready, mail is refused, a mention arrives, a limit is near – is an Event with a stable evt_ id. Events are idempotent records: list them, read them, replay them.
curl -H "Authorization: Bearer $TIGBY_API_KEY" https://api.tigby.eu/api/eventsRegister a Webhook
A Webhook is a delivery target you register – in the console or on POST /api/identities/{handle}/webhooks – with the event types it wants. Deliveries are signed with HMAC per Identity; verify the signature before trusting the body.
The envelope carries the Event's own evt_ id under a fresh request id and timestamp – deduplicate on the evt_ id, and a replay or a retry can never double-book.
Retries
A delivery that fails is retried after 30 s, 5 m, 30 m, 2 h, 6 h and 24 h – seven attempts in all – then marked failed. The deliveries list shows every attempt: when, how long, which status. Replaying an Event creates a fresh delivery with the same evt_ id.
Answer fast
Return 2xx quickly and do the work afterwards; a slow endpoint is a failing one. Anything your handler needs beyond the envelope, read back from the API with the Event's id.