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 Subscriber SIP Credentials API

Endpoints related to creating & managing [Subscriber](/docs/platform/subscribers) SIP Endpoints.

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

Tagged areas include Subscriber SIP Credentials. 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 2 paths, and defines 15 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 2 paths 15 schemas 1 DELETE2 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 Subscriber SIP Credentials 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 2 paths, the API surfaces 5 operations — 1 DELETE, 2 GET, 1 PATCH, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Subscriber SIP Credentials 5

Endpoints related to creating & managing [Subscriber](/docs/platform/subscribers) SIP Endpoints.

GET
/api/fabric/resources/subscribers/{fabric_subscriber_id}/sip_endpoints
List Subscriber SIP credentials
list_subscriber_sip_credentials 1 param → 200401404500
POST
/api/fabric/resources/subscribers/{fabric_subscriber_id}/sip_endpoints
Create Subscriber SIP credential
create_subscriber_sip_credential 1 param body → 201401404422500
GET
/api/fabric/resources/subscribers/{fabric_subscriber_id}/sip_endpoints/{id}
Get Subscriber SIP credential
get_subscriber_sip_credential 2 params → 200401404500
PATCH
/api/fabric/resources/subscribers/{fabric_subscriber_id}/sip_endpoints/{id}
Update Subscriber SIP credential
update_subscriber_sip_credential 2 params body → 200401404422500
DELETE
/api/fabric/resources/subscribers/{fabric_subscriber_id}/sip_endpoints/{id}
Delete Subscriber SIP credential
delete_subscriber_sip_credential 2 params → 204401404500

Schemas 15

The contract defines 15 schemas that model the data the API accepts and returns. The most detailed are SubscriberSIPEndpoint (7 properties), SubscriberSipEndpointRequestUpdate (7 properties), SubscriberSipEndpointRequest (7 properties), Types.StatusCodes.RestApiErrorItem (5 properties). Each schema is shown below with its type and property counts.

SubscriberSipEndpointPaginationResponse
object
4 properties 2 required
SubscriberSIPEndpoint
object
7 properties 7 required
SipEndpointCreateStatusCode422
object
The request contains invalid parameters. See errors for details.
1 property 1 required
SubscriberSipEndpointRequestUpdate
object
7 properties
Types.StatusCodes.StatusCode401
object
Access is unauthorized.
1 property 1 required
Encryption
string
uuid
string
Universal Unique Identifier.
SipEndpointUpdateStatusCode422
object
The request contains invalid parameters. See errors for details.
1 property 1 required
Types.StatusCodes.StatusCode404
object
The server cannot find the requested resource.
1 property 1 required
SubscriberSipEndpointRequest
object
7 properties 2 required
Codecs
string
SubscriberSipEndpointListResponse
object
2 properties 2 required
Types.StatusCodes.StatusCode500
object
An internal server error occurred.
1 property 1 required
Ciphers
string
Types.StatusCodes.RestApiErrorItem
object
Details about a specific error.
5 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

signalwire-subscriber-sip-credentials-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 Subscriber SIP Credentials 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.