unreadable_pfx
The .pfx/.p12 file could not be parsed, or the certificate inside it could not be read.
The .pfx/.p12 file could not be parsed, or the certificate inside it could not be read.
| Code | unreadable_pfx |
| Type | invalid_request_error — Malformed or incomplete input |
| HTTP | 400 |
| Retriable? | No |
What to do
Re-export the .pfx from the certificate store with its default settings. An implausible key-derivation work factor, a malformed certificate, and an unreadable validity window all land on this code.
Retrying the same request will fail the same way. Change the request, not the frequency.
The envelope
{
"error": {
"type": "invalid_request_error",
"code": "unreadable_pfx",
"message": "…",
"hint": "Re-export the .pfx from the certificate store with its default settings. An implausible key-derivation work factor, a malformed certificate, and an unreadable validity window all land on this code.",
"retriable": false,
"doc_url": "https://docs.facturia.cl/errors/unreadable_pfx",
"request_id": "req_01K2R7Q9M4T2VB"
}
}Program against code, never against message — the prose can be rewritten, the code cannot (§5.8).
hint and retriable arrive in the response with these exact values: they are a function of code and come from the same dictionary GET /v1/error_codes serves, so the envelope and the dictionary cannot disagree. Both are English on the wire by design — one registry, one language. More in The error envelope.
See also
Every code
The error envelope
The machine-readable copy of this page lives at GET /v1/error_codes, unauthenticated.