Turn approving what your AI agents change on or off
Sets the calling person's own "Ask me to approve what my agents change". On, each change their AI agents ask for waits for them to approve it in the dashboard, in every org of theirs. Off, the default, an ordinary change applies when it is asked, recorded in its org's audit log as made by that agent for them, except in an org that requires approval for every change. 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: never an agent's to change. Turning it off wants a sign-in from the last 5 minutes (403 `fresh_sign_in_required`). Recorded as `member.agent_approvals_updated` in each org of theirs that doesn't require approval, where it changes anything.
/v1/agent-approvalsSets the calling person's own "Ask me to approve what my agents change". On, each change their AI agents ask for waits for them to approve it in the dashboard, in every org of theirs. Off, the default, an ordinary change applies when it is asked, recorded in its org's audit log as made by that agent for them, except in an org that requires approval for every change. 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: never an agent's to change. Turning it off wants a sign-in from the last 5 minutes (403 fresh_sign_in_required). Recorded as member.agent_approvals_updated in each org of theirs that doesn't require approval, where it changes anything.
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
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
curl -X PATCH "https://api.synq.build/v1/agent-approvals" \ -H "Authorization: Bearer $SYNQ_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "ask_to_approve": true }'{ "ask_to_approve": false}Read whether you approve what your AI agents change GET
The calling person's own setting, "Ask me to approve what my agents change" (`ask_to_approve`, off unless they turned it on). Each org's own `GET …/agent-approvals` says how their agents' changes are made there. A person's credential only.
Revoke an API key DELETE
At once: it gets 401 `api_key_revoked` from then on. Needs `org.apiKeys.edit`. Recorded as `api_key.revoked`.