Get a project's controls
The project’s ZDR / vendor / region override and the controls actually in force for it (the organization’s with the project’s units applied). Requires the manage_projects scope.
Authentication
A management key (prefixed mgmt_), created in the dashboard under Settings, API keys, Management keys. Distinct from a regular gateway API key, and never used to call models.
Path parameters
Response
Exactly what this scope stores, unit-wrapped: zero_data_retention, vendors {ignored_vendors, allowed_vendors, vendor_routing_preference}, regions {ignored_regions, allowed_regions}. Empty means it inherits everything.
The controls actually in force for the scope: the organization’s with this scope’s units applied. For a customer, a project is not folded in; at request time a customer override still wins over a project’s.
Per unit (zero_data_retention, vendors, regions), which scope supplied the effective value: org or this scope