Digital certificate
The digital certificate that signs every DTE — where it's uploaded in Simplo and how to monitor its validity.
Every DTE is digitally signed with your company’s digital certificate (the same type of certificate you use to operate on the SII portal). It’s one of the two initial setup requirements, along with folios (CAF): without a valid certificate, nothing can be signed or emitted. See the SII’s official page on the digital certificate (in Spanish) and Electronic invoicing in Chile for more on the rest of the requirements (CAF, certification, environments).
Endpoints
Section titled “Endpoints”| Method | Path | Description |
|---|---|---|
GET |
/api/v1/billing/empresa/certificado |
Status and validity of the company’s digital certificate. |
POST |
/api/v1/billing/empresa/certificado/pfx |
Upload the digital certificate in PFX format. |
The certificate is uploaded once per company, either through your Simplo
account (Facturación → Configuración) or the PFX endpoint. Both
endpoints are session-only (your account’s JWT): a billing:dte API key
can’t call them (403 BILLING_API_KEY_ROUTE_NOT_ALLOWED). In the
sandbox there’s no certificate to upload — a synthetic one is
provisioned when you create your key.
With the SDK
Section titled “With the SDK”const status = await simplo.company.certificate.status();// { has_certificado, fecha_vencimiento, ... }Watch fecha_vencimiento (“expiration date”) from your account (the
certificado.expiring webhook event exists in the contract, but webhook
delivery isn’t live yet) and renew the certificate before it lapses to
avoid interrupting emission.
Related
Section titled “Related”- Folios and CAF — the other initial requirement
- Webhooks — the
certificado.expiringevent - Quickstart — the full setup flow