Bulk Operations
Bulk endpoints allow you to perform actions on multiple records in a single API call. This is useful for high-volume alert processing, batch assignment, and workflow automation.
Available bulk operations
Bulk resolve
Resolve multiple alerts with the same action and notes:
Bulk acknowledge
Claim multiple alerts for review:
Bulk assign
Assign multiple alerts to a specific analyst:
Bulk escalate
Escalate multiple alerts to a manager:
Partial success handling
Bulk operations use partial success semantics. The API processes each record independently and returns per-record results. The HTTP status code indicates the overall outcome:
Error codes
Request limits
Exceeding the per-request limit returns a 400 Bad Request with the message: “Maximum 100 alert tokens per bulk request.” Split larger batches into multiple requests.
Best practices
Idempotency: Bulk resolve and acknowledge are idempotent for already-processed records. Re-submitting a token that was already resolved returns a success result (not an error). This makes retries safe.
-
Keep batches under 100 records. Larger batches increase the chance of partial failures and make retries more complex.
-
Handle partial success. Always check the
summary.failed count and inspect individual results for errors. Do not assume all records succeeded.
-
Use consistent actions. Bulk resolve applies the same action and notes to all alerts. If different alerts need different actions, split them into separate requests.
-
Retry only failed records. On partial failure, extract the failed tokens and retry only those:
Audit trail
Every record in a bulk operation generates its own audit trail entry. Bulk operations also create a single BULK_OPERATION summary event that references the total count and action performed.
Next steps