List the signing certificates
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.
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
uuidQuery Parameters
How many per page, from 1 to 100.
1 <= value <= 10020The next_cursor or prev_cursor of a previous response. Without a cursor, the first page.
length <= 200Response Body
application/json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
curl -X GET "https://example.com/v1/ec/entities/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"}Change an emission point PATCH
Its name or code, on all the point's series in your key's environment. The code can only change while the point has not numbered any document (`409`).
Upload the signing certificate POST
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.