Skip to main content
POST
Add Tag To Subject

Authentication and permissions

Token requirements: User-based token (OAuth) or Organization-scoped API key or Team-scoped API key. Send a bearer access token for one of these identities. The permissions and resource restrictions below also apply.
Permissions joined by + are all required; or separates alternatives. Full-access keys still cannot call endpoints marked unsupported. Team keys must allow every team checked by the request. OAuth access depends on the user’s roles and resource access. Authorization follows the tagged subject. Granting permission to edit tag definitions alone does not authorize editing every tagged resource.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json

---- Polymorphic tag attach ----

subjectType
enum<string>
required

TagSubjectType is the kind of entity a tag is attached to. Mirrors the DB tag_subject_type enum and keys the polymorphic tag-subject RPCs that replace the per-subject tag-attach RPCs.

Deliberately distinct from AccessRelationshipSubjectType: the two overlap but diverge (tags add workflow/guidance; owners add team) and back separate DB enums. Unifying them would trade enum type-safety for runtime subset validation.

Available options:
TAG_SUBJECT_TYPE_UNSPECIFIED,
TAG_SUBJECT_TYPE_WORKFLOW,
TAG_SUBJECT_TYPE_GUIDANCE,
TAG_SUBJECT_TYPE_APP_INSTANCE,
TAG_SUBJECT_TYPE_RESOURCE,
TAG_SUBJECT_TYPE_ENTITLEMENT,
TAG_SUBJECT_TYPE_FORM,
TAG_SUBJECT_TYPE_FORM_BLOCK
subjectId
string
required
tagId
string
required

Response

200 - application/json

Success

data
Tag · object[]

The subject's resulting tag set.