Pair a channel

​

Headers

​

Body parameters

​

Example request

curl -s -X POST 'https://api.qoder.com.cn/api/v1/forward/channel_pairings' \
  -H "Authorization: Bearer $QODER_ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: pairing-K7MP92" \
  -d '{
    "code": "K7MP92",
    "identity_id": "idn_019eabc123",
    "template_id": "tmpl_workspace_dev"
  }'

​

Example response

{
  "id": "pair_019eabc123",
  "type": "channel_pairing",
  "channel_id": "channel_019eabc123",
  "identity_id": "idn_019eabc123",
  "template_id": "tmpl_workspace_dev",
  "status": "active",
  "paired_at": "2026-07-16T10:00:00Z"
}

​

Response fields

​

Error codes

​

Notes

• The server uses the user_id resolved from the PAT and the normalized code to locate the pending pairing record — the request does not need channel_id.
• Pairing codes are unique within a single user scope; the response returns the channel_id resolved by the server.
• Submitting the same code with the same Identity and Template is idempotent and returns the existing Pairing; any different binding value returns a conflict.
• A Channel is a transport connection; a Pairing is the actual execution context binding for that direct/room scope.
• After successful pairing, Forward best-efforts a success notification to the original conversation; notification failure does not roll back the Pairing.

​

Related