Upload the signing certificate
The .p12 and its password are verified (the certificate must belong to the entity 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.
Your API key, which acts for the one business it was created for: fb_sandbox_… issues in sandbox, fb_test_… in test, the tax authority's testing service, and fb_live_… in live.
In: header
Path Parameters
uuidRequest Body
multipart/form-data
TypeScript Definitions
Use the request body type in TypeScript.
The .p12 (or .pfx) file.
binary1 <= length <= 200Response Body
application/json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
curl -X POST "https://example.com/v1/ec/entities/497f6eca-6276-4993-bfeb-53cbbbba6f08/certificates" \ -F file="string" \ -F password="string"{ "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"}List the signing certificates GET
The certificates the entity 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.
Re-read the data from the SRI registry POST
Reads again the legal name, accounting and regime of a `live` business from the SRI registry, which changes them when the taxpayer does. What you wrote yourself (trade name, addresses, contact, resolutions) is left alone, and the regime stays as it was if the registry does not say. `409` for a `sandbox` business, whose data is made up; `503` if the registry does not respond.