Catalog Policy

Get Component Usage Flows

Return the flows that would be affected by blocking one component key.

A flow matches when the queried key and any of the flow's stored keys resolve to a shared canonical identity — the same matching rule flow writes and runs enforce. Flows are sorted by name, then id, and truncated to limit; total always reports the full match count. Results may lag flow writes by up to USAGE_SCAN_CACHE_TTL_SECONDS.

get/api/v1/catalog-policy/usage/flows

Query parameters

componentstring required

Component key to look up; aliases resolve like catalog enforcement.

Component key to look up; aliases resolve like catalog enforcement.

limitinteger

Response

Successful Response

componentstring required
totalinteger required

Total number of matching flows, before the limit is applied.

Changes

Changed in 1 of the 22 revisions of this API.1