List a series' skips
Each time a document in the series left behind a number the SRI already had registered (error 45), from newest to oldest. It explains the numbers the series skipped.
AuthorizationBearer <token>Your API key, which acts for the one business it was created for: fb_live_… keys work at api.fiscalbase.io and issue in live, and fb_sandbox_… keys work at api-sandbox.fiscalbase.io and issue in sandbox, on the simulated SRI. A key sent to the other host is refused with api_key_wrong_host, which names its host.
id*stringuuidlimit?integerHow many per page, from 1 to 100.
1 <= value <= 10020cursor?stringThe next_cursor or prev_cursor of a previous response. Without a cursor, the first page.
length <= 200Fiscalbase-Environment?stringThe environment the call acts in. Required with a person's session; a key's own environment is the one that counts, so a key may leave it out, and naming another is 422 environment_mismatch.
"sandbox""test""live"Fiscalbase-Business?stringThe business the call acts for. With a person's session, the one the call is about (without it, a call about one business is 422 business_required and a list covers every business of the organization); a key acts for its own, so naming another is 422 business_mismatch.
uuidFiscalbase-Channel?stringWhich of Fiscalbase's own integrations a key's call comes from, recorded as the channel of the documents it issues: a record, not a permission. Without it, api. A person's call is always console.
"api""mcp"Fiscalbase-Agent?stringThe AI agent a key's call comes from, as its client names itself (the MCP server sets it); recorded with the request and shown in the console's request log.
The skips
application/json- response
object*"list""list"data*array<>next_cursor*|The next page (older); null if there are no more.
prev_cursor*|The previous page (newer); null on the first.
curl -X GET 'https://api.fiscalbase.io/v1/ec/series/497f6eca-6276-4993-bfeb-53cbbbba6f08/renumberings'{
"object": "list",
"data": [
{
"id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
"object": "renumbering",
"series_id": "0f6582ac-1e7e-41dc-a63a-24fccd074d0c",
"document_id": "b792e8ae-2cb4-4209-85b9-32be4c2fcdd6",
"refused_number": "string",
"number": "string",
"mode": "automatic",
"created_at": "2019-08-24T14:15:22Z"
}
],
"next_cursor": "string",
"prev_cursor": "string"
}List a series' gaps GET
The runs of numbers missing from the series, the highest first: `open` ones, perhaps sales nobody imported, and the ones settled as `annulled`.
Change an emission point and its establishment PATCH
One administrative act, in one transaction: `point` changes the emission point's name or code on all its series in your key's environment (another system's punto takes a name too, like the system that issues there), and `establishment` changes its establishment's name, address or code on every series the establishment has. Each part says only what changed, and at least one is given. A code changes only while nothing was numbered under it (`409 emission_point_already_numbered`, `409 establishment_already_numbered`); outside `sandbox` a new establishment code must be listed as open in the SRI registry, whose address it takes unless one is given. Either refusal leaves both as they were. `series.updated` says what changed on each series.