How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

SignalWire Imported Phone Numbers API

Import phone numbers hosted elsewhere into your SignalWire Space.

SignalWire Imported Phone Numbers API is one of 80 APIs that SignalWire publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Imported Phone Numbers. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

This API exposes 2 operations across 2 paths, and defines 23 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 2 base URLs: https://{space_name}.signalwire.com/api/laml/2010-04-01, https://{space_name}.signalwire.com.

2 operations 2 paths 23 schemas 2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://{space_name}.signalwire.com
Authentication
HTTP Basic, HTTP Bearer
Resource Areas
1

Authentication & Security 2

SignalWire Imported Phone Numbers API declares 2 security schemes for authenticating requests. It accepts HTTP basic authentication (SignalWireBasicAuth). It accepts HTTP bearer tokens (SignalWireBearerAuth). By default, every request must be authenticated.

  • SignalWireBasicAuth — SignalWire Basic Authentication using Project ID and API Token. The client sends HTTP requests with the Authorization header containing the word Basic followed…
  • SignalWireBearerAuth — SignalWire Bearer Token Authentication for subscriber endpoints. The client sends HTTP requests with the Authorization header containing the word Bearer follow…

Paths & Operations 2

Across 2 paths, the API surfaces 2 operations — 2 POST. Each is listed below with its method, path, parameters, and response codes.

Imported Phone Numbers 2

Import phone numbers hosted elsewhere into your SignalWire Space.

POST
/Accounts/{AccountSid}/ImportedPhoneNumbers
Import a Phone Number
create_imported_phone_number 1 param body → 201400401422
POST
/api/relay/rest/imported_phone_numbers
Import phone number
create_imported_phone_number body → 201401422500

Schemas 23

The contract defines 23 schemas that model the data the API accepts and returns. The most detailed are PhoneNumberResponse (41 properties), IncomingPhoneNumber (33 properties), IncomingPhoneNumberCapabilities (4 properties), Types.StatusCodes.SpaceApiErrorItem (4 properties). Each schema is shown below with its type and property counts.

NumberType
string
The type of phone number being imported.
ImportPhoneNumberRequest
object
Request body for importing a phone number.
3 properties 2 required
IncomingPhoneNumberCapabilities
object
Phone number capabilities.
4 properties 4 required
uuid
string
Universal Unique Identifier.
AddressRequirements
string
Address requirements.
CompatibilityImportedPhoneNumberError
object
Error response model with string code for ImportedPhoneNumbers.
4 properties
CompatibilityErrorResponse
object
Error response model.
4 properties 4 required
PhoneNumberOrigin
string
Phone number origin.
IncomingPhoneNumber
object
Incoming phone number model.
33 properties 32 required
PhoneNumberCapability
string
Phone number capabilities.
PhoneNumberE911Status
string
E911 provisioning status of a phone number.
PhoneNumberCapability_2
string
Phone number capability.
PhoneNumberCallHandler
string
Call handler type for phone numbers.
ImportPhoneNumberRequest_2
object
Request body for importing a phone number.
3 properties 2 required
Types.StatusCodes.StatusCode401
object
Access is unauthorized.
1 property 1 required
PhoneNumberType
string
Phone number type.
PhoneNumberResponse
object
Response containing a single phone number.
41 properties 41 required
CallReceiveMode
string
Call receive mode.
Types.StatusCodes.ValidationError
object
The request failed validation. See errors for details.
1 property 1 required
Types.StatusCodes.SpaceApiErrorItem
object
Details about a specific validation error.
4 properties 4 required
Types.StatusCodes.StatusCode500
object
An internal server error occurred.
1 property 1 required
PhoneNumberMessageHandler
string
Message handler type for phone numbers.
HttpMethod
string
HTTP method type.

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

signalwire-imported-phone-numbers-api-openapi.yml Raw ↑

Other APIs SignalWire publishes across the network.

SignalWire Calling API (JSON-RPC)
SignalWire Accounts API
SignalWire Addresses API
SignalWire AI Agents: Custom API
SignalWire AI Agents: Dialogflow API
SignalWire AI Chat API
SignalWire AI Webhooks API
SignalWire Applications API
SignalWire Available Phone Numbers API
SignalWire Call Flows API
SignalWire Calling Webhooks API
SignalWire Calls API
Where this information came from

This is an independent, third-party profile of SignalWire Imported Phone Numbers API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.