La référence de l'API est publiée en anglais.
Approve or deny assistant access using a same-origin browser session
/api/mcp/requests/{id}/consentApprove or deny assistant access using a same-origin browser session.
Person-only: a person connects their own assistant, such as Claude, ChatGPT or another MCP client, in their browser on Assistant connections, with this conversation's organization prefix as . That page gives the invitation and server URL to paste into the assistant; the assistant then opens a Veyra Intelligence consent screen where the person picks the organization and approves access. The consent screen offers only access within that person's own role: a read-only member can grant read access but not writes. An agent cannot read this setup or approve consent for anyone: these routes accept only the person's own signed-in browser session. Do not search for another route; link that page, say the person approves access there themselves, and reply.
Autorisation
Send a personal API key as Authorization: Bearer <key>. It acts as you, with your permissions in each organization. Agent API keys are refused with 403. Fonctionnement des clés.
Paramètres de chemin
Corps de la requête
application/json · obligatoire
one of: "approve", "deny"Réponses
details names each field that failed.Les erreurs renvoient {"error": "..."}, souvent avec un code et des details. Voir erreurs et limites.