Skip to main content
PATCH
Add or remove task tags in batch

Authorizations

X-API-Key
string
header
required

API key authentication. Include your API key in the X-API-Key header as: X-API-Key YOUR_API_KEY

Example:

Authorization
string
header
required

JWT Bearer token authentication. Include your access token in the Authorization header as: Bearer YOUR_ACCESS_TOKEN

Example:

Body

application/json

Batch request to add or remove multiple task execution tags.

Supports mixed operations (add and remove) in a single atomic transaction. All operations succeed together or all fail. Efficient for bulk tagging.

tags
PatchFlowTaskTagsRequestItem · object[]
required

Array of tag operations to perform in a single atomic transaction. Each item specifies an 'add' or 'remove' operation for a specific task. Operations processed sequentially; all succeed or all fail together.

Batch benefits:

  • Single database transaction for consistency
  • Reduced network overhead (one request vs many)
  • Atomic operations (no partial failures)

Mixed operations supported:

  • Add tags to multiple tasks
  • Remove tags from multiple tasks
  • Add and remove different tags in same request

Practical limit: 1-100 operations per request for performance. For bulk tagging beyond 100 operations, split into multiple requests.

Required array length: 1 - 100 elements
Example:

Response

Task tags successfully updated

Response from batch tag operations.

Returns status for each operation in request array order. Array length matches request array length (1:1 correspondence).

tags
PatchFlowTaskTagsResponseItem · object[]
required

Array of operation results in request array order. Each element corresponds to the tag operation at the same index in the request.

Response structure:

  • Length: Always equals request.tags length
  • Order: Preserves request order (response[i] is result of request.tags[i])
  • Content: Each item contains 'status' field indicating operation outcome

Example mapping: Request: [add_tag1, remove_tag2, add_tag3] Response: [status1, status2, status3]

All operations complete (no partial failures). Check each status to determine individual operation outcomes. Use array index to match operations with results.

Example: