List the signing certificates
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.
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 certificates
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/businesses/497f6eca-6276-4993-bfeb-53cbbbba6f08/certificates'{
"object": "list",
"data": [
{
"holder": "string",
"holder_identification": "string",
"holder_identification_type": "cedula",
"kind": "natural_person",
"issuer_name": "string",
"subject": "string",
"issuer": "string",
"serial_number": "string",
"valid_from": "2019-08-24T14:15:22Z",
"valid_until": "2019-08-24T14:15:22Z",
"id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
"object": "certificate",
"uploaded_at": "2019-08-24T14:15:22Z",
"replaced_at": "2019-08-24T14:15:22Z",
"current": true
}
],
"next_cursor": "string",
"prev_cursor": "string"
}Read the business's RUC again GET
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`).
Upload the signing certificate POST
The .p12 and its password are verified (the certificate must belong to the business and be valid) and sealed: the API can no longer open them; only the signing process can. The last certificate you upload signs `test` and `live` documents while it is valid; when it expires no earlier one signs, even if still valid: upload a new one.