SynqDocs
Management APIApproval window

Read whether you approve without signing in again

The calling person's approval window, in the dashboard session the token comes from: once an approval relies on a fresh sign-in (a change to money, people or sign-in security takes one, as an approval request's `fresh_sign_in` says), their approvals in that same session skip signing in again until 2 hours after that sign-in (`window_seconds`), like GitHub's sudo mode. Each change still has its own approval page and its own Approve. It closes early when they sign out, the session ends, or they sign in again, and another device or session has its own. What wants a fresh sign-in outside an approval, such as making an API key on its own page, still wants one from the last 5 minutes. Only the dashboard approves, so another app's token never has one open. A person's credential only.

GET/v1/approval-window

The calling person's approval window, in the dashboard session the token comes from: once an approval relies on a fresh sign-in (a change to money, people or sign-in security takes one, as an approval request's fresh_sign_in says), their approvals in that same session skip signing in again until 2 hours after that sign-in (window_seconds), like GitHub's sudo mode. Each change still has its own approval page and its own Approve. It closes early when they sign out, the session ends, or they sign in again, and another device or session has its own. What wants a fresh sign-in outside an approval, such as making an API key on its own page, still wants one from the last 5 minutes. Only the dashboard approves, so another app's token never has one open. A person's credential only.

Authorization

bearer
AuthorizationBearer <token>

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

Response Body

application/json

application/problem+json

application/problem+json

application/problem+json

curl -X GET "https://api.synq.build/v1/approval-window" \  -H "Authorization: Bearer $SYNQ_API_KEY"
{  "open": true,  "signed_in_at": "2026-11-13T09:12:00.000Z",  "ends_at": "2026-11-13T11:12:00.000Z",  "window_seconds": 7200}

Ask for a change, made at once or approved by the person in the dashboard POST

A change that widens who can get in or changes where sign-ins go, asked for from an MCP host: a new brand with a permanent issuer slug (`brand.create`), an app's redirect URIs (`app.redirect_uris`), a way to sign in an app takes or stops taking, or its test sign-ins (`app.sign_in_method`), a new app (`app.create`), an invitation (`org.invite`) an API key (`org.api_key`), or dashboard configuration (`configuration.update`: themes, brand email, APIs/scopes, token gates, sending domains and file finalization). Reads what is there as the caller and answers with `preview`, what it does in plain words, and its `hash`. A change the org's plan can't take is refused now, as approving would refuse it (403 `plan_feature_unavailable`, or `plan_quota_exceeded` for a new app or brand), naming the plan that allows it and how to move there, so nobody is asked to approve what can't be made. By default a change is made at once, answering `approved` with `applied_at_once` (recorded as `approval_request.applied`, and the change as its route records it, naming this request and the MCP host's app), and a refusal is the change's own route's, with nothing left waiting. It waits instead, and nothing changes until the same person approves it at `approve_url` in the dashboard within 15 minutes, where the org requires approval for every AI agent change or the person asks to approve theirs (`GET …/agent-approvals`), and whatever either says for money, people, sign-in security and a secret shown once (`asks_because`). 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. People only, never an API key. Needs `org.read`, and asking needs the permission the change does: `org.apps.edit` for apps and the ways they take, `org.members.edit` for an invitation, `org.apiKeys.edit` (and every permission the key would hold) for an API key. Recorded as `approval_request.created`.

Delete an app DELETE

At once: it signs no one in and gets no tokens. An app an API names as its own client can't be deleted until the API names another. Needs `org.apps.edit`. Recorded as `app.deleted`.