Read how AI agents’ changes are approved in an org
Whether the org requires approval for every change its members' AI agents ask for (`require_approval`, off by default), and how the calling person's are made there (`your_approvals`). 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. Needs `org.read`.
/v1/orgs/{org}/agent-approvalsWhether the org requires approval for every change its members' AI agents ask for (require_approval, off by default), and how the calling person's are made there (your_approvals). 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. Needs org.read.
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}$Response Body
application/json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
curl -X GET "https://api.synq.build/v1/orgs/org_01h455vb4pex5vsknk084sn02q/agent-approvals" \ -H "Authorization: Bearer $SYNQ_API_KEY"{ "require_approval": false, "your_approvals": "apply_at_once"}Delete an org DELETE
At once, nothing serves it: not its routes, its API keys or its brands' issuers. A paid plan ends with it: its Stripe subscription is canceled at once, with nothing prorated and no final invoice, so the rest of the period isn't refunded and nothing more is charged. It is purged 30 days later, and its issuer slugs are never used again. Needs `org.delete`, which only the owner has. Recorded as `org.deleted`.
Download the org's audit log GET
Every entry between `since` and `until` (at most 366 days), oldest first: the org's own and every brand's, each with the brand it happened in (`brand`, its id and name, or null for the org's own), to keep a copy or for a security tool such as a SIEM. CSV, JSON or NDJSON, streamed. On every plan, as far back as the org's plan keeps entries (its `audit_retention_days` in `GET /v1/plans`: 7, 30 or 365 days, or for ever, then 366 days at a time). Needs `org.auditLog.export` across the org. Ten an hour for an org. Each export is recorded as `org.audit_log_exported`, with the window it covered.