Sign in
Integrations

Reject an agent's connect request

Changed on

End the session as rejected — the approve dialog's explicit Reject.

Only the target agent's owner (holding credentials:write and agents:write) or org:admin; there is no poll-token path and an agent can never reject. Everyone else gets the uniform 403. The agent's /status then reports failed with error_code: rejected, and its repeat :connect for the same target answers 429 recently_rejected for the rejection cooldown. Closing the dialog without rejecting makes no call; an unmount cancel stays cancelled.

post/connect-sessions/{session_id}:reject

Request

  • Base URL: / (relative, and the document was published on a file host, not at the API’s origin)
  • URL: /connect-sessions/{session_id}:reject
  • Auth: HTTP bearer

Path parameters

session_idstring required

Response

Successful Response

Changes