What a team's sandboxes can start from: its own templates and the installation's.
API key access: read.
apiKeyAuthorizationBearer <pyo_…>An API key from the dashboard's API keys page: Authorization: Bearer pyo_…. Keys can expire, and an expired one gets a 401.
team*stringThe team's id.
templates, each with id, teamId (null for the installation's), name, source (kind and image), state ("pending", "building", "ready" or "failed", from its servers, and "unavailable" for base or desktop while Pyo has no image for it), builtin, servers, error and createdAt. Pyo's own base and desktop come first, are always listed and are ready to use: servers make them on first use, so their servers are those that have them. Each of the other templates' servers is a sandbox server that may use it, with id, name, state ("pending", "building", "ready" or "failed"), phase while building ("queued", "pulling", "unpacking" or "snapshotting"), pulled and unpacked of imageBytes (asked of the server as the list is read, while it builds), pullMs, unpackMs and snapshotMs, bytes (disk it takes there), snapshots and error.
application/jsoncurl -X GET 'https://your-pyo.example.com/api/v1/sandbox-templates?team=string'{}