Skip to main content
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 the admin 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

X-Exo-API-Key
string
header
required

An Exo API key (exo_...) sent as the X-Exo-API-Key header.

Query Parameters

cursor
string | null

Opaque cursor from nextCursor.

pageSize
integer | null

Page size, coerced into [1, 100].

Response

Successful Response

data
SandboxKey · object[]
required
hasMore
boolean
default:false
nextCursor
string | null