Events

The account event log: every event, with or without a webhook, in order. Read it with GET /v1/eventos?apos=<cursor> and store the proximo_cursor of each response (it comes even when the page is empty). Events come in order, and the cursor only moves forward; never use dates to paginate.

The cursor is opaque text: store it and send it back exactly as it came, without interpreting it. The seq of each event is the same kind of cursor. Until 02/10/2026 it was a number; a numeric cursor stored before that date is still accepted in apos.

Without apos, reading starts at the oldest event still stored. Filter by type with tipos (comma-separated). Each event has id (the same X-Sudrel-Event-Id as the webhook), tipo, ocorrido_em, ambiente, empresa_id, recurso (tipo, id and url to read the current state) and dados.

dados is filled in when the body was stored (there was a webhook subscribed to the type, and always for received documents); otherwise it is null and recurso.url tells where to read the current state.

Retention: 90 days. A cursor older than that returns 410 cursor_vencido, with cursor_mais_antigo: continue from it and check through the read routes what may have changed in the gap.