Skip to content

Custody Destination Invalid

URI: https://docs.ankatech.co/errors/custody-destination-invalid
HTTP Status: 422 Unprocessable Content

When you see this

A prepare or verify step named a destination key-encryption key that is not one of this tenant's on the destination backend. The key service accepts a destination only for the tenant the request names, so no key is staged or unwrapped under it.

This problem is answered by the key service to the platform's own administration service while it drives a key custody move, one bounded re-wrap step per call. It is never answered to a browser, an SDK or an API client, so its instance names an internal call and is not reproduced here. An operator sees its effect on the move instead: the move's state on the tenant's key custody read, and the audit trail of the move.

Response Example

{
  "type": "https://docs.ankatech.co/errors/custody-destination-invalid",
  "title": "Custody Destination Invalid",
  "status": 422,
  "detail": "The destination does not name a key-encryption key of this tenant on the destination backend.",
  "correlationId": "6a0c2f9e-3d71-4b58-8e24-c1f5a7d9b036",
  "timestamp": 1793696400
}

Content-Type: application/problem+json — the response follows RFC 9457 Problem Details. The detail is fixed: it names no tenant, key, key-encryption key or count.

How to Resolve

  1. The window aborts before its swap and the tenant reopens on its unchanged source.
  2. Contact support with the move id: the destination recorded on the move does not match the tenant.

For full schema definitions, examples, and interactive testing, see the Developer Hub Reference.