The nightly check found numbers missing from a series, perhaps sales nobody brought in
application/json- body
id*stringThe event's id, also its webhook-id header: deduplicate by it.
uuidtype*"series.gap_detected""series.gap_detected"timestamp*stringdate-timebackfill?truePresent, and true, only on a delivery a backfill replayed (POST /v1/webhook-endpoints/{id}/backfill).
truedata*Any 2xx within 15 seconds acknowledges it; anything else is retried.
{
"id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
"type": "series.gap_detected",
"timestamp": "2019-08-24T14:15:22Z",
"data": {
"id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
"object": "series",
"business_id": "f59fcbb7-848d-4242-af07-a8bb7e3ab37c",
"environment": "sandbox",
"type": "invoice",
"establishment": "string",
"emission_point": "string",
"establishment_address": "string",
"establishment_name": "string",
"emission_point_name": "string",
"issued_by": "fiscalbase",
"active": true,
"next_number": 1,
"last_number_seen": 0,
"last_seen_on": "2019-08-24",
"seen_this_month": 0,
"issued_today": 0,
"gaps": {
"count": 0,
"oldest_missing": 0
},
"created_at": "2019-08-24T14:15:22Z",
"updated_at": "2019-08-24T14:15:22Z",
"gap": {
"from": 1,
"to": 1
}
}
}The nightly check found another system reusing a number on its series Webhook
Anterior
Stream events GET
Your key's business's events in its environment, as [server-sent events](https://html.spec.whatwg.org/multipage/server-sent-events.html), from the moment it opens: the same events, in the same envelope, as the webhooks POST (`id`, `type`, `timestamp`, `data`, the resource as its `GET` answers it; every type and its `data` is in the document's `webhooks`). Each event is one message whose `data` is that JSON and whose `id` is the event's; they come in the order they were stored. A `read_only` key opens it too. Resume with `Last-Event-ID`, which an `EventSource` sends by itself when it reconnects, or with `since`: the events after that one are sent first, from those kept (90 days), then the new ones. A stream opened without either starts after the business's newest event, whose `id` it sends first with no message, so a client that hears nothing still resumes from there. A comment line every 18 seconds keeps it open; after about 90 seconds it ends, with `retry: 1000`, and the client opens it again from its last event. A key holds at most 5 open at once: one more is `429 event_streams_exhausted` with `Retry-After`.