Bulk update incidents (async job)

POST 
/v2/incidents/bulk

Selects incidents by explicit incident_display_ids and/or filter fields (status, priority, module_name, created_after, created_before, assignee_email), then applies update_status, update_priority or update_assignee.

Asynchronous: returns 202 with a job_id. Poll GET /v2/jobs/{jobId} for per-record outcomes. Bulk requests have a lower per-token rate budget than single writes.

Request

Responses

202

Job accepted. data contains job_id, state, accepted and status_url.

400

Validation failure. See error.code (VALIDATION_ERROR, INVALID_STATUS_TRANSITION, COMMENT_REQUIRED, USER_NOT_FOUND, INVALID_DISPLAY_ID, BULK_ACTION_FIELD_MISMATCH, BULK_LIMIT_EXCEEDED).

401

UNAUTHORIZED: missing or invalid bearer token, or wrong token type for a write route.

403

Access denied. Possible codes are ACCESS_DENIED, TWO_WAY_DISABLED, MODULE_ACCESS_DENIED, INCIDENT_ARCHIVED, org/user inactive, or integration configuration inactive.

429

RATE_LIMIT_EXCEEDED: the per-token budget is exhausted. Back off per the Retry-After header.

Response Headers

Retry-After

Seconds to wait before retrying.

503

INTEGRATION_PLATFORM_UNAVAILABLE or INTEGRATION_AUTH_UNAVAILABLE: transient upstream failure, safe to retry.