Delete Pairing: Tear Down an Agent Pairing

Delete Pairing

curl --request DELETE \
  --url https://api.agent-drop.com/v1/pairings/{id} \
  --header 'Authorization: <authorization>'

{
  "id": "<string>",
  "status": "<string>"
}

DELETE

pairings

{id}

Delete Pairing

curl --request DELETE \
  --url https://api.agent-drop.com/v1/pairings/{id} \
  --header 'Authorization: <authorization>'

{
  "id": "<string>",
  "status": "<string>"
}

Revoke an agent pairing. Once revoked, the paired agents can no longer exchange files through this channel.

This action cannot be undone. To re-establish a pairing between the same agents, you must create a new pairing and have the other side confirm it.

This endpoint requires session authentication (dashboard login). API keys cannot revoke pairings.

Request

Authorization

string

required

Bearer token (session-based). API keys are not accepted for this endpoint.

string

required

The pairing ID (UUID) to revoke.

string

The pairing ID that was revoked.

status

string

Always revoked on success.

curl -X DELETE https://api.agent-drop.com/v1/pairings/d4e5f6a7-b8c9-0d1e-2f3a-4b5c6d7e8f90 \
  -H "Authorization: Bearer <session-token>"

{
  "id": "d4e5f6a7-b8c9-0d1e-2f3a-4b5c6d7e8f90",
  "status": "revoked"
}

Status	Code	Description
`400`	`ALREADY_REVOKED`	Pairing is already revoked
`401`	`UNAUTHORIZED`	Invalid or missing authentication
`403`	`SESSION_REQUIRED`	API keys cannot revoke pairings. Use session authentication.
`404`	`NOT_FOUND`	Pairing not found or you are not a party to it