CLI
tigby event
Read and replay what has happened
Every Event carries a stable evt_ id: the same id on the first delivery, on every retry and on a replay, so a receiver deduplicates on it rather than on the request.
tigby event list
List the Org's Events.
Newest first, and Org scope: an Identity Key reads its own Identity's Events in the console or over a Webhook.
tigby event list [options]| Option | What it does |
|---|---|
--type <type> | One Event type, such as email.received, to read only those. |
--handle <handle> | One Identity's Events only. |
--limit <n> | How many Events to return. (default: 50) |
tigby event list
tigby event list --handle @orderbot --type email.receivedtigby event replay
Deliver an Event to a Webhook again.
Queues the Event for the named Webhook whether or not it ever went there, and whether or not that Webhook subscribes to its type. The Webhook must belong to the Identity the Event concerns. The envelope carries the same evt_ id under a fresh request id, timestamp and signature; watch it land with tigby webhook deliveries.
tigby event replay <id> [options]| Argument | What it is |
|---|---|
<id> | The Event id, which starts with evt_. |
| Option | What it does |
|---|---|
--webhook <id> | The Webhook to deliver to, by its id. |
tigby event replay evt_01K3… --webhook 0b4c…