---
title: "Batch Impact Analysis"
method: POST
path: "/api/v1/assets/{asset_id}/lineage/batch-impact"
tags: ["lineage-query"]
---

# Batch Impact Analysis

`POST /api/v1/assets/{asset_id}/lineage/batch-impact`

## Request

- Base URL: `http://localhost:8000`
- URL: `http://localhost:8000/api/v1/assets/{asset_id}/lineage/batch-impact`
- Auth: none declared

Analyze downstream impact for multiple nodes in a single request.

TECH-817: Returns downstream impact counts for each unique_id,
enabling the schema changes page to show impact badges without
N+1 API calls.

Args:
    asset_id: Asset UUID
    request: Batch request with unique_ids and max_hops

## Path parameters

- `asset_id` string, uuid, required

## Headers

- `Authorization` string

## Request body

- BatchImpactRequest: Request body for batch downstream impact analysis. TECH-817: Enables the schema changes page to show downstream impact counts for multiple tables in a single request.
  - `unique_ids` string[], required: List of lineage node unique identifiers (format: catalog.schema.table)
  - `max_hops` integer: Maximum hops to traverse for each node

## 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)