Decline an addressed connection request

POST/api/connection-intents/{interactionId}/decline
Personal API keyConsole session
Veyra Docs TeamUpdated Version 3 · History

Decline an addressed connection request.

Person-only: a connection request card is addressed to one person, its addresseeUserId. Only that person, signed in to their own browser, can open its setup, connect their account or decline it. The server refuses every other member, member and agent, so nobody can finish it for them. When someone else offers to finish it, tell them the addressee must connect their own account from the card on its task, linked as . Do not create another request for the addressee and do not search for another route.

Authorization

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. How keys work.

Path parameters

interactionIdstringRequiredThe interaction's id.

Request body

application/json · required

reasonstringOptionalat most 4000 characters

Responses

200SuccessThe request worked; the body holds the result.
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.

Errors return {"error": "..."}, often with a code and details. See errors and limits.

Connection requests