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: Campaigns API

Create and manage 10DLC campaigns for A2P messaging compliance.

SignalWire Campaign Registry: Campaigns 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: Campaigns. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

This API exposes 4 operations across 2 paths, and defines 13 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.

4 operations 2 paths 13 schemas 2 GET1 POST1 PUT

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: Campaigns 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 4

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

Campaign Registry: Campaigns 4

Create and manage 10DLC campaigns for A2P messaging compliance.

GET
/api/relay/rest/registry/beta/brands/{id}/campaigns
List campaigns
list_campaigns 3 params → 200401404500
POST
/api/relay/rest/registry/beta/brands/{id}/campaigns
Create campaign
create_campaign 1 param body → 201401404422500
GET
/api/relay/rest/registry/beta/campaigns/{id}
Get campaign
retrieve_campaign 1 param → 200401404500
PUT
/api/relay/rest/registry/beta/campaigns/{id}
Update campaign
update_campaign 1 param body → 200401404422500

Schemas 13

The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are Campaign (31 properties), CampaignResponse (31 properties), CreateManagedCampaignRequest (28 properties), PaginationLinks (4 properties). Each schema is shown below with its type and property counts.

UpdateCampaignRequest
object
Request body for updating a campaign.
1 property
PaginationLinks
object
Pagination links for list responses.
4 properties 2 required
Types.StatusCodes.StatusCode401
object
Access is unauthorized.
1 property 1 required
CampaignResponse
object
Response containing a single campaign.
31 properties 1 required
uuid
string
Universal Unique Identifier.
Types.StatusCodes.StatusCode404
object
The server cannot find the requested resource.
1 property 1 required
CampaignListResponse
object
Response containing a list of campaigns.
2 properties
Types.StatusCodes.ValidationError
object
The request failed validation. See errors for details.
1 property 1 required
CreatePartnerCampaignRequest
object
Request body for creating a partner/CSP campaign. Used when the brand is a CSP (self-registered) brand.
4 properties 3 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
CreateManagedCampaignRequest
object
Request body for creating a managed campaign. Used when the brand is a managed (non-CSP) brand.
28 properties 16 required
Campaign
object
Campaign model for 10DLC registration.
31 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

signalwire-campaign-registry-campaigns-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: Campaigns 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.