List sandbox keys
Account and platform
List sandbox keys
Cursor-paginated sandbox keys, keyset on (createdAt, id), oldest first.
GET
List sandbox keys
Plaintext is never returned —
id is the key hash, the same opaque
round-trip id the shipped GET /v1/keys exposes, and the value
DELETE /v1/sandbox/keys/{id} takes. An org that has never minted a
sandbox key gets an empty page; listing never provisions the partition.
Authorization
This route requires theadmin scope.
A missing or invalid credential returns 401 authentication_error. A valid credential without the scope returns 403 permission_denied, and the problem body names the exact scope required.
Headers
These are request conventions the contract does not declare as parameters, so they do not appear in the schema tables below.Success responses
Errors
Every error is an RFC 9457
application/problem+json body carrying a stable code, a requestId, and a suggestedAction where Exo has one. See Errors.Authorizations
An Exo API key (exo_...) sent as the X-Exo-API-Key header.
Query Parameters
Opaque cursor from nextCursor.
Page size, coerced into [1, 100].