The journey of the document
Every step it went through, from newest to oldest: accepted, signed, received, authorized or returned, the RIDE generated, each email sent and each correction.
Your API key, which acts for the one business it was created for: fb_sandbox_… issues in sandbox, fb_test_… in test, the tax authority's testing service, and fb_live_… in live.
In: header
Path Parameters
uuidQuery Parameters
How many per page, from 1 to 100.
1 <= value <= 10020The next_cursor or prev_cursor of a previous response. Without a cursor, the first page.
length <= 200Response Body
application/json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
curl -X GET "https://example.com/v1/ec/documents/497f6eca-6276-4993-bfeb-53cbbbba6f08/events"{ "object": "list", "data": [ { "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "object": "document_event", "document_id": "b792e8ae-2cb4-4209-85b9-32be4c2fcdd6", "type": "string", "revision": 0, "data": { "property1": null, "property2": null }, "created_at": "2019-08-24T14:15:22Z" } ], "next_cursor": "string", "prev_cursor": "string"}Check a document's status now POST
Asks the SRI right now whether it has decided on a `submitted` document, without waiting for the next scheduled check; the answer arrives through the usual flow (the status changes and the webhook is sent). A `pending` document is already being signed or sent, and one the SRI has already decided has nothing to ask: both come back as they are, with nothing queued. Each document is checked at most once every 10 seconds: repeating it sooner answers `429` with `Retry-After`, and the SRI receives a single question however many times it is pressed.
Download the authorized XML GET
The SRI `autorizacion` with the signed document inside, the same as the download from the SRI portal.