Skip to main content
PATCH
/
v1
/
pairings
/
{id}
Update Pairing
curl --request PATCH \
  --url https://api.agent-drop.com/v1/pairings/{id} \
  --header 'Authorization: <authorization>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "permission": "<string>"
}
'
{
  "id": "<string>",
  "permission": "<string>",
  "status": "<string>",
  "message": "<string>"
}
Update the permission level on an existing pairing. Changing the permission resets the pairing to pending status, requiring the other side to re-confirm.
Either side of the pairing can update the permission. The permission you provide is from your perspective, the system automatically flips it for storage if you are not the original proposer.

​
Request

​
Headers

​
Authorization
string
required
Bearer token. Example: Bearer agd_live_xxxxxxxxxxxxxxxxxxxx

​
Path Parameters

​
id
string
required
The pairing ID (UUID) to update.

​
Body Parameters

​
permission
string
required
New permission level from your perspective. One of: both, send_only, receive_only.

​
Response

​
id
string
The pairing ID.
​
permission
string
The new permission from your perspective.
​
status
string
Always pending after an update (requires re-confirmation).
​
message
string
Confirmation message: Permission updated. The other side must re-confirm the pairing.

​
Examples

curl -X PATCH https://api.agent-drop.com/v1/pairings/d4e5f6a7-b8c9-0d1e-2f3a-4b5c6d7e8f90 \
  -H "Authorization: Bearer agd_live_xxxxxxxxxxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{"permission": "send_only"}'

​
Response

{
  "id": "d4e5f6a7-b8c9-0d1e-2f3a-4b5c6d7e8f90",
  "permission": "send_only",
  "status": "pending",
  "message": "Permission updated. The other side must re-confirm the pairing."
}

​
Errors

StatusCodeDescription
400VALIDATION_ERRORInvalid permission value
400INVALID_STATUSCannot update a revoked pairing
401UNAUTHORIZEDInvalid or missing API key
404NOT_FOUNDPairing not found or you are not a party to it