Key Link

Register signing keys in bulk

Accepts a set of signing keys certified by a single validation key and queues them for registration in the background. Returns a job id to poll. A workspace can have one bulk registration at a time; submitting another while one is QUEUED or IN_PROGRESS is rejected with 409. Bulk registrations from different workspaces share a limited number of slots, so a job may wait QUEUED behind another workspace's before it starts. Keys already registered in the workspace are recognized and skipped, so resubmitting the same request after a failure is safe and only processes what is missing. Every key must carry its own proof of ownership; a bulk registration has no interactive step in which one can arrive later.

post/key_link/signing_keys/bulk

Request

Headers

Idempotency-Keystring

A unique identifier for the request. If the request is sent multiple times with the same idempotency key, the server will return the same response as the first request. The idempotency key is valid for 24 hours.

Request body

validationKeyIdstring required

The id of the validation key that signed every certificate in this request, as returned when the validation key was registered. Not the signingDeviceKeyId of any signing key.

Example request

{
  "validationKeyId": "fb5d0a66-ca01-44f0-9080-8c3282964a23",
  "keys": []
}

Response

Registration is queued

jobIdstring required

Id of the registration job. Poll it for progress.

Example response

{
  "jobId": "46a92767-5f93-4a46-9eed-f012196bb4fc"
}

Changes

No recorded changes to this operation across all 1 revision of this API.