Events

Every event Nodium emits — the ones your webhooks receive — is also written to a numbered log, kept 30 days. Read it from a cursor instead of depending on webhook deliveries: the webhook is a doorbell, the log is the truth. Each entry is the webhook envelope (id, event, workspace_id, external_id, occurred_at, data) plus its seq.

Start without after: data is empty and next_after is the current head — store it as your first cursor. Then call with after set to the last next_after you kept, and repeat while next_after moves: a page may be empty and still move forward (events of other clients are skipped). When a call returns the same next_after you sent, you are up to date; come back when a webhook rings, or every minute. Keep next_after only after you have stored the page.

Entries come in seq order and none is skipped: an entry is returned only once every earlier one is settled, so a recent entry can appear a moment after the webhook that announced it. Deduplicate on id (a webhook delivery and the log carry the same one). seq is unique across the whole log, not per client: expect gaps.

A key that sees every client of the account reads all of them, unless the Nodium-Tenant header names one; a key pinned to one client reads that client only. Entries older than your plan's content retention keep their envelope but an empty data.