Read the business's RUC again
Asks the SRI's registry about a live business now and says where it differs from the business's own fields. Nothing changes until a person takes it (POST /v1/ec/businesses/{id}/registry/apply).
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*stringuuidFiscalbase-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.
What the registry says, and how it differs
application/json- response
object*"business_registry""business_registry"business_id*stringuuidruc*stringlegal_name*stringstatus*stringACTIVO, SUSPENDIDO… as the SRI reports it.
read_at*stringdate-timestale*booleantrue when the SRI couldn't be reached and this is the last answer kept.
changes*array<>Where the registry differs from what Fiscalbase holds. POST /v1/ec/businesses/{id}/registry/apply takes the legal name, the regime and the accounting; a resolution (special_taxpayer, withholding_agent) is written with PATCH /v1/ec/businesses/{id}. Empty when they agree.
curl -X GET 'https://api.fiscalbase.io/v1/ec/businesses/497f6eca-6276-4993-bfeb-53cbbbba6f08/registry'{
"object": "business_registry",
"business_id": "f59fcbb7-848d-4242-af07-a8bb7e3ab37c",
"ruc": "string",
"legal_name": "string",
"status": "string",
"read_at": "2019-08-24T14:15:22Z",
"stale": true,
"changes": [
{
"field": "legal_name",
"current": "string",
"registry": "string"
}
]
}Update a business PATCH
Only the fields you send change. On a `live` business, the legal name, the regime and whether it keeps accounting come from the SRI registry and cannot be edited (`422`). Documents already issued keep the data they were signed with. The `portal` settings need a plan with portal branding (`403` `portal_branding_plan_required`).
List the signing certificates GET
The certificates the business uploaded, from newest to oldest, with when each was replaced: `current` marks the one that signs and the rest are the history. Only what they say: the .p12 and its password are sealed and the API does not return them. A `sandbox` business has none.