Skip to main content
POST
/
api
/
adm
/
transactionTags
/
update
Update Transaction Tags
curl --request POST \
  --url https://localhost:44371/api/adm/transactionTags/update \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{}'
{
  "success": true,
  "code": 200,
  "errorMessage": null
}

​
Description

Modifies tags on transactions in batch. Operations include adding new tags to transactions, removing existing tags, or updating tag metadata. This endpoint supports bulk operations for efficiency when tagging multiple transactions with the same classification or removing tags from a set of transactions.

​
Input

  • Body: model (TransactionTagUpdateCommandRequest, required) — Update command including:
    • transactionIds (array of strings, required) — List of transaction IDs to update.
    • tagsToAdd (array of strings, optional) — List of tag names to add.
    • tagsToRemove (array of strings, optional) — List of tag names to remove.

​
Output

Returns a TransactionTagUpdateCommandResponse indicating the result and count of updated transactions.

​
Example Request

POST /api/admin/transactionTags/update
Content-Type: application/json
Authorization: Bearer {token}

{
  "transactionIds": ["TX123456", "TX123457", "TX123458"],
  "tagsToAdd": ["high-value", "fraud-review"],
  "tagsToRemove": []
}

​
Example Response

{
  "success": true,
  "code": 200,
  "errorMessage": null,
  "updatedCount": 3
}

​
Errors

  • 400 Bad Request — Missing required fields, validation errors, or duplicate tag.
  • 404 Not Found — One or more specified transaction IDs do not exist.
  • 401 Unauthorized — Missing or invalid authentication token.

​
Notes

  • Tag operations are atomic per transaction; partial failures are rolled back.
  • Tag changes are audited and include timestamp and user information.
  • Adding a tag that already exists on a transaction will fail validation.
  • Removing a non-existent tag is silently ignored (success).
  • Tag names are case-sensitive and should follow naming conventions.

Authorizations

​
Authorization
string
header
required

The access token received from the authorization server in the OAuth 2.0 flow.

Body

application/json

The update command containing transaction IDs and tag operations (add/remove) to perform.

Base structure for command requests that modify data. Represents the request used to update transaction tags for a project.

​
companyProjectId
string<guid>

The identifier of the project whose tags are being updated.

​
transactionTags
object[] | null

The collection of transaction tags to persist.

Response

Always returned. Check the success property in the response body to determine if the operation succeeded.

Standard response structure containing operation status and error information. Standard command response indicating the result of a data modification. Represents the response returned after updating transaction tags.

​
success
boolean

True if the operation completed successfully; false if an error occurred.

Example:

true

​
code
enum<string>

Result code indicating the outcome of the operation.

Available options:
Unknown,
Success,
BadRequest,
Unauthorized,
NotFound,
Error
Example:

200

​
errorMessage
string | null

Human-readable error message when an error occurs.

Example:

null