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 SIP Gateway API

Endpoints related to creating & managing SIP Gateways

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

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

This API exposes 6 operations across 3 paths, and defines 22 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.

6 operations 3 paths 22 schemas 1 DELETE3 GET1 PATCH1 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 SIP Gateway 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 6

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

SIP Gateway 6

Endpoints related to creating & managing SIP Gateways

GET
/api/fabric/resources/sip_gateways
List SIP gateways
list_sip_gateways → 200401404500
POST
/api/fabric/resources/sip_gateways
Create SIP gateway
create_sip_gateway body → 201401404422500
GET
/api/fabric/resources/sip_gateways/{id}
Get SIP gateway
get_sip_gateway 1 param → 200401404500
PATCH
/api/fabric/resources/sip_gateways/{id}
Update SIP gateway
update_sip_gateway 1 param body → 200401404422500
DELETE
/api/fabric/resources/sip_gateways/{id}
Delete SIP gateway
delete_sip_gateway 1 param → 204401404500
GET
/api/fabric/resources/sip_gateways/{id}/addresses
List SIP gateway Addresses
list_sip_gateway_addresses 1 param → 200401404500

Schemas 22

The contract defines 22 schemas that model the data the API accepts and returns. The most detailed are FabricAddressCall (9 properties), SipGatewayResponse (7 properties), SipGateway (6 properties), SipGatewayRequest (5 properties). Each schema is shown below with its type and property counts.

SipGatewayPaginationResponse
object
4 properties 2 required
Types.StatusCodes.StatusCode401
object
Access is unauthorized.
1 property 1 required
Encryption
string
SipGatewayCreateStatusCode422
object
The request contains invalid parameters. See errors for details.
1 property 1 required
SipGateway
object
6 properties 6 required
Codecs
string
AddressChannel
VideoChannel
object
1 property 1 required
Ciphers
string
SipGatewayResponse
object
7 properties 7 required
AudioChannel
object
1 property 1 required
uuid
string
Universal Unique Identifier.
Types.StatusCodes.StatusCode404
object
The server cannot find the requested resource.
1 property 1 required
SipGatewayAddressListResponse
object
2 properties 2 required
Types.StatusCodes.StatusCode500
object
An internal server error occurred.
1 property 1 required
SipGatewayListResponse
object
2 properties 2 required
MessagingChannel
object
1 property 1 required
Types.StatusCodes.RestApiErrorItem
object
Details about a specific error.
5 properties 4 required
SipGatewayRequestUpdate
object
5 properties
FabricAddressCall
object
9 properties 9 required
SipGatewayRequest
object
5 properties 5 required
SipGatewayAddressPaginationResponse
object
4 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

signalwire-sip-gateway-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 SIP Gateway 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.