Skip to main content
PUT
/
api
/
sandboxes
/
{id}
/
tags
Set Sandbox Tags
curl --request PUT \
  --url https://app.opencomputer.dev/api/sandboxes/{id}/tags \
  --header 'Content-Type: application/json' \
  --header 'X-API-Key: <api-key>' \
  --data '
{
  "<tagKey>": "<string>"
}
'
{
  "tags": { "env": "staging", "team": "growth" },
  "tagsLastUpdatedAt": "2026-04-22T20:31:14Z"
}
Replace the full tag set for a sandbox. Partial updates are not supported — GET, modify, PUT. {} clears all tags.
Preview: Usage and tag APIs are new. Endpoints, response fields, and SDK method names may change before GA; temporary inaccuracies or rough edges are possible while the surface settles.
​
id
string
required
Sandbox ID.
​
<tagKey>
string
Each top-level key in the body is a tag name; the value is a string. Flat map only — nested objects are rejected.

​
Validation

  • At most 50 tag keys per sandbox.
  • Keys: 1–128 characters, A–Z a–z 0–9 _ . - :. : is allowed as a user namespace separator.
  • Values: 0–256 UTF-8 characters.
  • The oc: key prefix is reserved for future system-set tags.
{
  "tags": { "env": "staging", "team": "growth" },
  "tagsLastUpdatedAt": "2026-04-22T20:31:14Z"
}
Retagging rewrites attribution going forward: a sandbox re-tagged from team=payments to team=growth will appear under growth in every subsequent /usage query, including for time before the retag. Surface tagsLastUpdatedAt alongside usage in dashboards so readers can see when tags changed.