Get Bridge by Slug
Telephony & Bridges
Get Bridge by Slug
Retrieve details of a specific telephony bridge using its slug
GET
Get Bridge by Slug
Documentation Index
Fetch the complete documentation index at: https://docs.unpod.dev/llms.txt
Use this file to discover all available pages before exploring further.
Get Bridge by Slug
Retrieve full details of a specific telephony bridge using its unique slug identifier, including its assigned phone numbers and current configuration.Prerequisites: Make sure you have your API Token and Org-Handle ready. See Authentication for details.
Path Parameters
| Name | Type | Required | Description |
|---|---|---|---|
| slug | string | Yes | Unique bridge slug |
You can get the bridge
slug by hitting the Get All Bridges API. The slug field in the response is your Bridge Slug.Headers
| Name | Type | Required | Description |
|---|---|---|---|
| Authorization | string | Yes | API Key format: Token <token> |
| Org-Handle | string | Yes | Organization domain handle |
You can get the
Org-Handle by hitting the Get All Organizations API. The domain_handle field in the response is your Org-Handle.Response Fields
| Field | Type | Description |
|---|---|---|
| status_code | integer | HTTP status code |
| message | string | Response message |
| data | object | Bridge details |
Bridge Object Fields
| Field | Type | Description |
|---|---|---|
| id | integer | Bridge unique identifier |
| name | string | Bridge display name |
| slug | string | Unique bridge slug identifier |
| numbers | array | List of assigned phone numbers |
Number Object Fields
| Field | Type | Description |
|---|---|---|
| id | integer | Number assignment ID |
| number_id | integer | Phone number ID |
| number | string | Phone number (E.164 format) |
| state | string | Number state: ASSIGNED, UNASSIGNED |
| active | boolean | Whether number is active |
| channels_count | integer | Number of active channels |
| status | string | Number status: active, inactive |
Common Error Codes
| Status Code | Description |
|---|---|
| 200 | Success - Bridge fetched successfully |
| 401 | Unauthorized - Invalid or missing API token |
| 403 | Forbidden - Invalid organization handle |
| 404 | Not Found - Bridge not found |
| 500 | Internal Server Error - Server-side error |
Code Examples
Best Practices
- Slug Validation: Handle 404 errors when a bridge slug may have been deleted or renamed
- Number Inspection: Check the
numbersarray to verify active phone numbers before routing calls - Active Status: Only numbers with
active: trueandstatus: activeare ready to handle calls - Error Handling: Always handle potential errors and edge cases
- Security: Keep API tokens secure and rotate them regularly