Get an emission point
A punto and every series it has in your key's environment, whoever issues on them.
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.
code*string^\d{3}$point*string^\d{3}$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*"issuing_point""issuing_point"establishment*string^\d{3}$emission_point*string^\d{3}$series*array<>Its series. Opening a punto answers the invoice and withholding series it opened or kept, in live; reading one answers every series of the punto in your key's environment.
curl -X GET 'https://api.fiscalbase.io/v1/ec/establishments/string/emission-points/string'{
"object": "issuing_point",
"establishment": "string",
"emission_point": "string",
"series": [
{
"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"
}
]
}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.
Take over another system's series POST
For a business moving off another system: the series becomes Fiscalbase's, turned on, handing out the number after the highest seen there (or `next_number`, when later), and `series.updated` says what it was. Stop issuing there from the other system first: what it issues later collides (`series.collision_detected`). Outside `sandbox`, the SRI must still list its establishment as open. One Fiscalbase already issues on is `409 series_already_fiscalbase`. Send an `Idempotency-Key` to retry safely.