Upload digital certificate

POST 
/v1/certificates

Uploads an A1 digital certificate via multipart/form-data. The private key and password are encrypted at rest and are never returned by the API. The endpoint detects duplicates by thumbprint and automatically associates the certificate with a person based on the extracted CNPJ/CPF.

Accepted type values:

• pfx — send file (binary PFX/P12) and password.
• cert_key — send cert_file (certificate PEM) and key_file (key PEM).
• combined_pem — send file (PEM containing certificate + key).
• cert_key_password — send cert_file, key_file and password (password-protected key).

Request

Responses

201

Certificate uploaded and stored successfully.

400

Request body failed validation.

401

Missing or invalid bearer token.

403

Token is valid but lacks permission for this operation. With code insufficient_scope, details.required carries the one minimal set of scopes that, added to details.granted, would let the request through: the resource scope (billing/{resource}, or billing/all off the catalogue) then the bare verb — e.g. ["billing/customers", "delete"].

404

Resource not found in the current organization.

422

Request body failed validation.

429

Rate limit exceeded.

500

Unexpected server error.