Where to issue
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).
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.
type*string"invoice""credit_note""debit_note""withholding""delivery_note""purchase_settlement"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.
The punto
application/json- response
object*"series_suggestion""series_suggestion"type*string"invoice""credit_note""debit_note""withholding""delivery_note""purchase_settlement"establishment*stringemission_point*stringestablishment_address*string|nullexisting*booleanWhether Fiscalbase already issues this type there.
curl -X GET 'https://api.fiscalbase.io/v1/ec/series/suggestion?type=invoice'{
"object": "series_suggestion",
"type": "invoice",
"establishment": "string",
"emission_point": "string",
"establishment_address": "string",
"existing": true
}Activate, deactivate or advance series PATCH
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.
Get a series GET
Siguiente