Query accessible Channel pairing records with filters and cursor pagination.
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
Use Authorization: Bearer <PAT or SAT>. Only Channel pairing records accessible to the caller are returned. By default, results include pending (pairing) and bound (active) records, but exclude unpaired (unbound) records.
Query parameters
| Parameter | Description |
|---|---|
channel_id | Optional. If omitted, query all Channels accessible to the caller. |
status | Optional: pairing or active. A Pair remains in pairing after its pairing code expires. |
target_type | Optional: user (private chat) or group (group chat). |
target_external_id | Optional. Exact match for an external user or group ID. Recommended together with Channel and target type filters. |
identity_id / template_id | Optional. Filter by the bound execution context; pending records do not match. |
limit | Items per page. Default: 20. Maximum: 100. |
after_id / before_id | Optional. Use a returned Pairing id as the cursor. These parameters cannot be used together. |
Example
scope_type is direct (private chat) or room (group chat). scope_external_id is the corresponding external user or group ID. Bound records return their actual identity_id, template_id, and paired_at. The list does not return pairing codes, employee numbers, or employee aliases, and does not generate or refresh pairing codes.
Invalid filter or pagination parameters return 400. A specified resource that is inaccessible or does not exist returns 404.
scope_display_name is the user's nickname or group name, or an empty string if unavailable. It is updated by subsequent messages and is for display only. Use the external ID for authorization.

