v19.1.0

Changelog

2026-05-27

Added

Add color field to UpdateTagRequest

Products: Tags

Scope: API + SDKs

• What's new
  UpdateTagRequest now exposes the optional color field (hex string, e.g. #FF5733), matching what the upstream tagging-service already accepts. Previously the field was missing from the OpenAPI spec.

• Impact
  Clients can update a tag's color via PATCH /v1/tags/{tagId}. No change to server behavior — the field was already honored upstream.

Affected endpoints:

1. Update a tag

Expose type field on tags and add type filter to list tags

Products: Tags

Scope: API + SDKs

• What's new
  The Tag response now includes an optional type field (currently WALLET_POOL) indicating the domain that owns the tag. CreateTagRequest accepts an optional type to create typed tags, and GET /v1/tags accepts an optional type query parameter (array of TagType, multi-select) to filter the paged list by one or more tag types. The type field is intentionally omitted from UpdateTagRequest because tag type is immutable after creation.

• Impact
  Clients can read the new type field on tag responses (including Tag embedded in vault-account responses), create typed tags via POST /v1/tags, and filter the list endpoint by tag type. Existing tags with no type continue to return without the field.

Affected endpoints:

1. Create a new tag
2. Get list of tags
3. Get a tag
4. Update a tag

---