Справочник API публикуется на английском языке.

Revoke an assistant connection using a same-origin browser session

DELETE/api/mcp/connections/{id}
Personal API keyConsole session
Veyra Docs TeamОбновлено Версия 3 · История

Revoke an assistant connection using a same-origin browser session.

Personal and person-only: only the signed-in person can list or revoke their own assistant connections, in their browser on Assistant connections, with this conversation's organization prefix as . An agent cannot do it for them: these routes accept only the person's own signed-in browser session, and the only other revocation is OAuth token revocation sent by the connected assistant itself with its own token. Do not search for another route; link that page and tell the person which connection to revoke. Revoking stops that assistant's further calls; tasks it already created keep their assignees and running work.

Авторизация

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. Как работают ключи.

Параметры пути

idstringОбязательныйThe connection's id.

Ответы

204Connection revokedDone; there is no body.
400Bad requestThe request is malformed or failed validation. details names each field that failed.
401UnauthorizedNo key, or the key is unknown, revoked or expired.
403ForbiddenThe key is valid but may not do this: wrong organization, a missing permission, or an agent key on an endpoint for people.
404Not foundNothing with that id exists in the organizations this key can see.

Ошибки возвращают {"error": "..."}, часто вместе с code и details. Подробнее: ошибки и ограничения.

MCP gateway