Rename a tagMenu

Rename a tag

PATCH/v1/tags/{id}

Requires an API key with the tags:write scope. About keys and scopes

Works with integration, agent and partner keys.

Safe to retry: a repeat sets the same values again. About idempotency

Renames the tag on every item that carries it. A name another tag holds, ignoring case, is refused with 409 ALREADY_EXISTS: merge the two instead.

Path parameters

idstringrequired

The tag's id.

uuid

Header parameters

Kirora-Workspacestringoptional

Partner keys only: the child workspace to act in, by the external id the partner gave it. Without it, a partner key acts in its own workspace. Any other key that sends it is refused with 403, and an unknown workspace is 404.

pattern ^[A-Za-z0-9._:-]{1,128}$

Request body

namestringrequired

The new name; unique within the workspace, ignoring case.

1–64 characters

Returns

Returns 200 OK with a Tag in data. It can also return 409 Conflict, 413 Payload Too Large or 415 Unsupported Media Type; see the statuses below. Otherwise returns an error; Errors lists every code and which to retry.

  • 200 OKThe renamed tag.
  • 409 ConflictThe request conflicts with current state — a duplicate unique value, or a resource whose status does not allow this operation.
  • 413 Payload Too LargeThe body is larger than this operation accepts (PAYLOAD_TOO_LARGE).
  • 415 Unsupported Media TypeThe body is not JSON, or not the upload the operation takes (UNSUPPORTED_MEDIA_TYPE).
idstringrequired

uuid

namestringrequired
usageobjectrequired

How many items of each kind carry the tag.

4 child attributes
campaignsintegerrequired

min 0

journeysintegerrequired

min 0

segmentsintegerrequired

min 0

templatesintegerrequired

min 0

createdAtstringrequired

date-time

updatedAtstringrequired

date-time