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 Campaign Registry: Phone Number Assignments API

Assign and manage phone numbers within 10DLC campaigns.

SignalWire Campaign Registry: Phone Number Assignments API is one of 80 APIs that SignalWire publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Campaign Registry: Phone Number Assignments. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

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

Requests are made against a single base URL, https://{space_name}.signalwire.com.

5 operations 4 paths 14 schemas 1 DELETE3 GET1 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
Contact
License
Terms of Service
Resource Areas
1

Authentication & Security 2

SignalWire Campaign Registry: Phone Number Assignments 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 5

Across 4 paths, the API surfaces 5 operations — 1 DELETE, 3 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Campaign Registry: Phone Number Assignments 5

Assign and manage phone numbers within 10DLC campaigns.

GET
/api/relay/rest/registry/beta/campaigns/{id}/numbers
List phone number assignments
list_number_assignments 2 params → 200401404500
GET
/api/relay/rest/registry/beta/campaigns/{id}/orders
List phone number assignment orders
list_orders 2 params → 200401404500
POST
/api/relay/rest/registry/beta/campaigns/{id}/orders
Create phone number assignment order
create_order 1 param body → 200401404422500
DELETE
/api/relay/rest/registry/beta/numbers/{id}
Delete phone number assignment
delete_number_assignment 1 param → 204401404500
GET
/api/relay/rest/registry/beta/orders/{id}
Get phone number assignment order
retrieve_order 1 param → 200401404500

Schemas 14

The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are AssignedNumber (6 properties), Order (6 properties), OrderResponse (6 properties), Types.StatusCodes.SpaceApiErrorItem (4 properties). Each schema is shown below with its type and property counts.

Types.StatusCodes.StatusCode401
object
Access is unauthorized.
1 property 1 required
AssignedNumberListResponse
object
Response containing a list of assigned numbers.
2 properties
OrderListResponse
object
Response containing a list of orders.
2 properties
CreateOrderRequest
object
Request body for creating an order.
2 properties
uuid
string
Universal Unique Identifier.
Types.StatusCodes.StatusCode404
object
The server cannot find the requested resource.
1 property 1 required
Types.StatusCodes.ValidationError
object
The request failed validation. See errors for details.
1 property 1 required
AssignedNumber
object
Assigned number model for campaign registration.
6 properties 1 required
Order
object
Order model for campaign registry operations.
6 properties 1 required
AssignedPhoneNumber
object
Phone number details in an assignment.
4 properties
Types.StatusCodes.SpaceApiErrorItem
object
Details about a specific validation error.
4 properties 4 required
OrderResponse
object
Response containing a single order.
6 properties 1 required
Types.StatusCodes.StatusCode500
object
An internal server error occurred.
1 property 1 required
PaginationLinks
object
Pagination links for list responses.
4 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

signalwire-campaign-registry-phone-number-assignments-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 Campaign Registry: Phone Number Assignments 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.