Skip to main content
Channels

Get a channel pairing

Retrieve a pending or bound Channel pairing record.

Channel pairing is currently in Beta. API definitions, response structures, and behavior may change. Check the documentation for updates.
GET /api/v1/forward/channel_pairings/{pairing_id} Retrieve a pending or bound pairing record.

Request parameters

Use Authorization: Bearer <PAT or SAT>. The required path parameter pairing_id is the id returned by List channel pairings.

Example request

curl -s 'https://api.qoder.com.cn/api/v1/forward/channel_pairings/pair_019eabc123' \
  -H "Authorization: Bearer $QODER_ACCESS_TOKEN"

Example response

HTTP 200 OK
{
  "id": "pair_019eabc123",
  "type": "channel_pairing",
  "channel_id": "channel_019eabc123",
  "scope_type": "direct",
  "scope_external_id": "external_user_id",
  "scope_display_name": "Test user",
  "status": "active",
  "identity_id": "idn_019eabc123",
  "template_id": "tmpl_workspace_dev",
  "paired_at": "2026-09-09T08:00:00Z",
  "created_at": "2026-09-09T07:50:00Z",
  "updated_at": "2026-09-09T08:00:00Z"
}
scope_type is direct (private chat) or room (group chat), and scope_external_id is the corresponding external user or group ID. For a pending record, status=pairing and identity_id, template_id, and paired_at are empty strings. Pairing code expiration does not change this status. The API does not return pairing codes. scope_display_name is the user's nickname or group name. It may be empty and is for display only.

HTTP error codes

HTTPTypeTrigger
400invalid_request_errorpairing_id is blank or contains control characters, or the Channel is not in pairing mode.
401authentication_errorPAT or SAT is invalid or expired.
403permission_errorThe caller does not have permission to invoke the API.
404not_found_errorThe pairing does not exist or has been unpaired, or its Channel does not exist, is archived, or is inaccessible.