---
title: "Import a Twilio number as a warm-transfer bridge number"
method: POST
path: "/v1/identity/org/bridge-numbers"
tags: ["identity"]
---

# Import a Twilio number as a warm-transfer bridge number

`POST /v1/identity/org/bridge-numbers`

## Request body

- ImportBridgeNumberRequest — Request body for importing a Twilio number as a bridge number. Accepts either the Twilio Phone Number SID (PN…) or the E.164 phone number (+1…) — we resolve the canonical SID from Twilio either way. We resolve the Twilio account credentials from the org's Nango-connected Twilio integration (the same credentials SMS/voice already use). Bridge numbers are BYO-only: the org must have a connected Twilio integration or the import is rejected.
  - `twilio_number_sid` string, required
  - `integration_connection_id` string, uuid, nullable — BYOT only. Pin the import to a specific connected Twilio integration. Required when the org has more than one connected Twilio integration; when omitted, the service auto-discovers the org's single connected integration and 422s on ambiguity.

## Response `200`

Successful Response

- BridgeNumberView — Public view of a bridge number — never exposes credentials.
  - `id` string, uuid, required
  - `phone_e164` string, required
  - `twilio_sid` string, required
  - `integration_connection_id` string, uuid, nullable
  - `status` string, required
  - `created_at` string, date-time, required

## Other responses

- `422` — Validation Error

---

[API](https://skmtc.net/oneloop-hq/apis/feather-api.md) · [All operations](https://skmtc.net/oneloop-hq/apis/feather-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/oneloop-hq/feather-api/revisions/9cd7291d4228/schema)