Skip to main content
Tag Value Update API

Authentication

All requests require an API key in the request headers. Headers:

Request

Content-Type: application/json This endpoint updates the state of one or more values of an existing dropdown tag. Use the tag’s slug (from the Tag List API) as the tagId path parameter, and the value ids (from the Tag Detail API or Tag Value Creation API) in the body. Every id in the payload must belong to the tag identified by tagId — if any id does not, the entire request is rejected and no value is updated.

Path Parameters

Body Parameters

Tag Value State Values

When a value is disabled, Pazy checks whether it is still in use on any open transaction (invoices, reimbursements, expenses, purchase orders, and similar). If it is in use, the value is kept as DEPRECATED so existing records stay intact. If it is not in use anywhere, the value is fully retired to DISABLED and is also cleared from any vendor it was mapped to as a default. Either way the request succeeds — the state reported by the Tag Detail API afterwards reflects the outcome.

Code Examples

Success Response

HTTP Status: 200 OK Response Fields:

Response Example

Error Responses

Tag Is Not a Dropdown

Returned when the target tag is not a dropdown tag (only dropdown tag values can be updated). HTTP Status: 400 Bad Request

Tag Value Does Not Belong to the Tag

Returned when one or more ids in the payload do not exist under the tag given in the path. No value is updated in this case. The same error is returned when the tag slug itself does not exist. HTTP Status: 400 Bad Request

Validation Error

Returned when the required tags array is missing, empty, contains more than 100 items, or an item has an unsupported state. HTTP Status: 400 Bad Request

Access Denied

HTTP Status: 403 Forbidden

Authentication Errors

HTTP Status: 401 Unauthorized

Permission Errors

HTTP Status: 403 Forbidden

Tag Value Update Failed

In the rare case the values could not be persisted, the response is returned with an HTTP 200 OK status, ok: false, and updated: false. HTTP Status: 200 OK

Best Practices

  • Only DROPDOWN tag values can be updated — use the Tag List API to confirm the tag’s dataType before calling
  • Fetch the value ids with the Tag Detail API; passing an id that belongs to a different tag rejects the whole request
  • Batch related changes into a single call — up to 100 values can be updated at once
  • Always check the updated flag in addition to the HTTP status; a failure is returned with ok: false and updated: false under a 200 OK status
  • Disabling a value does not alter transactions that already carry it — it only stops the value from being selected going forward
  • Access is limited to users with tag update permission and an admin or bookkeeper role