mcp

POST /v1/mcp/oauth/requests/{requestId}/approve

Approve an AI app — creates the connection and returns the app's redirect.

All mcp endpoints

All developer docs →

Authentication

Send an API key as a bearer token. The key must carry the mcp.manage permission; a key without it is refused with 403, not 404.

Where your organisation id goes

This endpoint takes org_id as a field in the JSON body.

Your organisation id is on the API keys screen in your dashboard, beside the key itself. It is the same id in every call you make.

Try it

Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.

curl -X POST https://api.zinndigital.com/v1/mcp/oauth/requests/{requestId}/approve \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "scopes": <string[]> }'

Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console

Details

Creates an MCP connection (kind: oauth) in the chosen organization with the chosen permissions and returns the URL to send the browser back to, carrying a one-time code. The person must manage MCP connections in that organization and may grant only permissions they hold there (403 otherwise); a request is approved once (404 after). Audited as mcp.connection.created. Requires mcp.manage.

Parameters

NameTypeRequiredWhat it is
requestId (path)stringYes—

Request body

NameTypeRequiredWhat it is
org_idUuidNoUUIDv7 identifier — sortable by creation time (docs/02 §8).
scopesstring[]Yes—

Response

NameTypeRequiredWhat it is
redirect_urlstringYesWhere to send the browser next.
connection_idUuidNoUUIDv7 identifier — sortable by creation time (docs/02 §8).

Errors this endpoint can return

401 · 403 · 404 · 422