Developer portal
POST /pqc/transparency/keys/retire
Admin endpoint to retire a transparency signing key and publish a rotation notice.
POST /pqc/transparency/keys/retireAuth: admin
Summary
Admin endpoint to retire a transparency signing key and publish a rotation notice.
Example
Response
{
"status": "success",
"retired": true,
"replaced_by": "key_2026_02"
}Try it live
Paste your tenant API key to call the live API with your credentials. Leave blank to use the public sandbox key when configured, or click “Show example response” for the static fixture below.
Request body
| Field | Type | Required | Description |
|---|---|---|---|
| key_id | string | Yes | Signing key identifier to retire. e.g. key_2025_11 |
Errors
| Code | Meaning | Typical cause | Suggested fix |
|---|---|---|---|
| 404 | Not found | Scan, schedule, share link, or resource id does not exist or expired. | Verify id and tenant scope; share links expire per expiresHours. |
| 422 | Unprocessable entity | Invalid payload shape, unsupported scenario, or infeasible constraints. | Fix field errors in response detail; relax constraints and retry. |
| 429 | Too many requests | Per-key rate limit exceeded (default 300 requests per minute) or public endpoint limit. | Backoff with jitter; cache results; request higher limit for production. |
| 500 | Internal server error | Unexpected backend failure; includes requestId in response. | Retry with exponential backoff; contact support with requestId if persistent. |
See the full errors reference.
Found an issue? Report documentation feedback