Require approval for every AI agent change in an org, or not
Sets whether every change the org's members' AI agents ask for waits for the member to approve it in the dashboard. Off, the default, an ordinary change applies when it is asked, recorded as made by the agent for the member, unless the member asks to approve theirs. Some changes always ask, and take a sign-in from the last 5 minutes to approve: money and people (billing and plans, inviting or removing members, roles, API keys, deleting or moving a brand) and sign-in security (an app’s redirect and sign-out addresses and how it proves itself, custom sign-in, sending and verified domains, turning a sign-in protection off, such as the breached-password check or PKCE, turning a token gate off, deleting it or taking a place off it, and loosening account linking). So does a change that makes a secret only you should see (a web or machine app’s client secret, a webhook’s signing secret), which shows once, on its approval page. From the dashboard's app only, by a person: never an agent's to change. Turning it on asks every member at once; turning it off wants a sign-in from the last 5 minutes (403 `fresh_sign_in_required`: sign in again with `max_age=300`). Needs `org.sso.edit`. Recorded as `org.agent_approvals_updated`.
/v1/orgs/{org}/agent-approvalsSets whether every change the org's members' AI agents ask for waits for the member to approve it in the dashboard. Off, the default, an ordinary change applies when it is asked, recorded as made by the agent for the member, unless the member asks to approve theirs. Some changes always ask, and take a sign-in from the last 5 minutes to approve: money and people (billing and plans, inviting or removing members, roles, API keys, deleting or moving a brand) and sign-in security (an app’s redirect and sign-out addresses and how it proves itself, custom sign-in, sending and verified domains, turning a sign-in protection off, such as the breached-password check or PKCE, turning a token gate off, deleting it or taking a place off it, and loosening account linking). So does a change that makes a secret only you should see (a web or machine app’s client secret, a webhook’s signing secret), which shows once, on its approval page. From the dashboard's app only, by a person: never an agent's to change. Turning it on asks every member at once; turning it off wants a sign-in from the last 5 minutes (403 fresh_sign_in_required: sign in again with max_age=300). Needs org.sso.edit. Recorded as org.agent_approvals_updated.
Authorization
bearer An org API key (sk_live_…, sk_test_…), or an access token from the Synq issuer (the synq brand, on the accounts host) for this API.
In: header
Path Parameters
The org's id
^org_[0-9a-hjkmnp-tv-z]{26}$Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
curl -X PATCH "https://api.synq.build/v1/orgs/org_01h455vb4pex5vsknk084sn02q/agent-approvals" \ -H "Authorization: Bearer $SYNQ_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "require_approval": true }'{ "require_approval": false, "your_approvals": "apply_at_once"}List the orgs the caller can act in GET
An API key's own org; a person's orgs, those they are a member of. Needs no permission.
Change an org PATCH
Its name, its slug or its default brand: making another brand the default is how the old default can be deleted on its own. Needs `org.edit`. Recorded as `org.updated`. Its brands' issuer slugs never change.