Update Project Controls
Replace the project’s override with exactly the fields you send; omit a
unit to inherit it. A management key can only tighten the organization’s
controls (narrow an allowlist, add to a denylist, turn zero data
retention on); anything that loosens them is refused with 403
scoped_controls_loosening_forbidden. Loosening is available in the
dashboard.
Authentication
A management key (mgmt_...), sent as Authorization: Bearer <key>. Reading /v1/routing-policies also accepts the organization’s gateway API keys; writing there needs a management key.
Path parameters
The project’s id.
Request
When non-empty, the only regions the project may route to. Vendors with no known region are excluded. Each token is a vendor’s country_code or geo_region, as listed by GET /v1/organization/vendors, like US, CA or NA. Case-sensitive; an unknown token is a 422.
When non-empty, the only vendors the project may route to.
Regions the project may never route to. Each token is a vendor’s country_code or geo_region, as listed by GET /v1/organization/vendors, like US, CA or NA. Case-sensitive; an unknown token is a 422.
Response
Always project here.