Tags
Org-level tag management, and what tags can't do yet.
Tags
Tags are organization-level labels: a name, a color and an optional description, managed independently of any monitor.
curl -X POST https://api.up0.io/api/v1/me/tags \
-H "Authorization: Bearer <ACCESS_TOKEN>" \
-H "Content-Type: application/json" \
-d '{ "name": "production", "color": "#3B82F6", "description": "Prod-facing checks" }'GET /api/v1/me/tags lists every tag in the organization; PATCH and
DELETE by id round out the set. Creating, updating and deleting a tag needs
an Editor role or above; reading only needs membership.
Tags cannot be put on a monitor yet
Tag management exists as a standalone catalog today. There is no endpoint
that attaches a tag to a specific monitor, MonitorCreate and
MonitorUpdate carry no tags field, and monitor list responses carry no
tag information. Creating, listing, renaming and deleting tags all work; a
monitor cannot yet be given one.
If your organization needs to group monitors today, service_id (see
Binding to services) is the grouping mechanism that
is actually wired end to end.