---
title: "Bulk Update Change Alert State"
method: POST
path: "/api/v1/schema-drift/changes/bulk-response"
tags: ["schema-drift", "schema-drift"]
---

# Bulk Update Change Alert State

`POST /api/v1/schema-drift/changes/bulk-response`

## Request

- Base URL: `http://localhost:8000`
- URL: `http://localhost:8000/api/v1/schema-drift/changes/bulk-response`
- Auth: none declared

Bulk update user response for multiple schema change events.

TECH-622: Efficient bulk operation for review queue.
Updates all provided change events in a single transaction.

Returns partial success info. IDs that don't exist or user lacks access to
are reported in failed_ids (intentionally no distinction for IDOR protection).

## Headers

- `Authorization` string

## Request body

- BulkChangeResponseRequest: Request body for bulk updating user response to multiple schema change events. TECH-622: Provides efficient bulk operations for the review queue.
  - `change_ids` string[], required: List of change event public UUIDs to update
  - `state` 'DISMISSED' | 'ACKNOWLEDGED', required: User response to a schema change event. This represents the user's action/acknowledgement state for individual schema change events, NOT the alert inbox lifecycle state. For alert inbox states (NEW, ACKNOWLEDGED, DISMISSED, RESOLVED, SNOOZED), see: app.domains.feature.alerts.values.alert_state.AlertState

## Response `200`

Successful Response

- StandardResponse: Standard API response wrapper.
  - `success` boolean, required
  - `data` unknown
  - `message` string, nullable
  - `error` string, nullable
  - `meta` object, nullable

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/anomalyarmor/apis/anomalyarmor-api.md) · [All operations](https://skmtc.dev/anomalyarmor/apis/anomalyarmor-api/llms.txt) · [OpenAPI document](https://skmtc.dev/anomalyarmor/apis/anomalyarmor-api/revisions/51c755fb5d0b?raw)