Activate, deactivate or advance series
One or several Fiscalbase series at once, in one transaction: a punto's numbers and switches saved together, or all its series turned off. Each change is a series' id with active, next_number or both. Only Fiscalbase series (409 series_not_fiscalbase otherwise: take another system's over with POST /v1/ec/series/{id}/continue). Documents already numbered keep their number. next_number only moves forward, like the initial sequence number of the SRI's Facturador: to continue after the last number another system used (422 at changes.<index>.next_number if the series already handed it out). Turning one on outside sandbox checks that the SRI still lists its establishment as open. Any refusal changes no series. series.updated says what changed on each.
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.
Fiscalbase-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.
application/json- body
changes*array<>1 <= items <= 100The changed series
application/json- response
object*"series_update""series_update"data*array<>Each series of the establishment or point, already changed.
curl -X PATCH 'https://api.fiscalbase.io/v1/ec/series' \
-H 'Content-Type: application/json' \
-d '{
"changes": [
{
"id": "497f6eca-6276-4993-bfeb-53cbbbba6f08"
}
]
}'{
"object": "series_update",
"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"
}
]
}Open a series POST
Opens a Fiscalbase series in your key's environment. Outside `sandbox`, the establishment must be listed as open for the RUC in the SRI registry; its address comes from there. One already there is `409 series_exists`, with its `series_id`. A punto another system used in the last 24 months is `409 series_used_elsewhere`, with `suggested_establishment` and `suggested_emission_point`, and the other system's `series_id` when its series of the type is there: take that one over with `POST /v1/ec/series/{id}/continue`. Send an `Idempotency-Key` to retry safely.
Where to issue GET
The punto to issue a type from: one where Fiscalbase already issues it, else the head office (or the lowest open establishment the SRI registry lists) and its lowest emission point no other system used in the last 24 months, so its numbers never collide with another system's (the SRI's error 45).