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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
SignalWire

SignalWire Relay Application API

Endpoints related to creating & managing Relay Applications

Documentation Provider Profile APIs.io OpenAPI GitHub

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

Tagged areas include Relay Application. 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 19 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 19 schemas 1 DELETE3 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
SignalWire
License
MIT
Terms of Service
View terms
Resource Areas
1

Authentication & Security 2

SignalWire Relay Application 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 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Relay Application 6

Endpoints related to creating & managing Relay Applications

GET
/api/fabric/resources/relay_applications
List Relay applications
list_relay_applications → 200401404500
POST
/api/fabric/resources/relay_applications
Create Relay application
create_relay_application body → 200401404422500
GET
/api/fabric/resources/relay_applications/{id}
Get Relay application
get_relay_application 1 param → 200401404500
PUT
/api/fabric/resources/relay_applications/{id}
Update Relay application
update_relay_application 1 param body → 200401404422500
DELETE
/api/fabric/resources/relay_applications/{id}
Delete Relay application
delete_relay_application 1 param → 204401404500
GET
/api/fabric/resources/relay_applications/{id}/addresses
List Relay application Addresses
list_relay_application_addresses 1 param → 200401404500

Schemas 19

The contract defines 19 schemas that model the data the API accepts and returns. The most detailed are FabricAddressApp (9 properties), RelayApplicationResponse (7 properties), Types.StatusCodes.RestApiErrorItem (5 properties), RelayApplication (4 properties). Each schema is shown below with its type and property counts.

Types.StatusCodes.StatusCode401
object
Access is unauthorized.
1 property 1 required
RelayApplicationAddressListResponse
object
2 properties 2 required
AddressChannel
RelayApplicationCreateStatusCode422
object
The request contains invalid parameters. See errors for details.
1 property 1 required
VideoChannel
object
1 property 1 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
RelayApplicationCreateRequest
object
3 properties 2 required
RelayApplicationAddressPaginationResponse
object
4 properties 2 required
RelayApplication
object
4 properties 4 required
Types.StatusCodes.StatusCode500
object
An internal server error occurred.
1 property 1 required
RelayApplicationUpdateRequest
object
3 properties
MessagingChannel
object
1 property 1 required
RelayApplicationUpdateStatusCode422
object
The request contains invalid parameters. See errors for details.
1 property 1 required
Types.StatusCodes.RestApiErrorItem
object
Details about a specific error.
5 properties 4 required
FabricAddressApp
object
9 properties 9 required
RelayApplicationListResponse
object
2 properties 2 required
RelayApplicationResponse
object
7 properties 7 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

signalwire-relay-application-api-openapi.yml Raw ↑

Other APIs SignalWire publishes across the network.

SignalWire Calling API (JSON-RPC)
AE Profile APIs.io
SignalWire Accounts API
AE Profile APIs.io
SignalWire Addresses API
AE Profile APIs.io
SignalWire AI Agents: Custom API
AE Profile APIs.io
SignalWire AI Agents: Dialogflow API
AE Profile APIs.io
SignalWire AI Chat API
AE Profile APIs.io
SignalWire AI Webhooks API
AE Profile APIs.io
SignalWire Applications API
AE Profile APIs.io
SignalWire Available Phone Numbers API
AE Profile APIs.io
SignalWire Call Flows API
AE Profile APIs.io
SignalWire Calling Webhooks API
AE Profile APIs.io
SignalWire Calls API
AE Profile APIs.io
#Relay Application
← Back to S APIs
API Details
ID
signalwire:signalwire-relay-application-api
Base URL
https://{space_name}.signalwire.com
Docs
https://signalwire.com/docs/apis
Provider
SignalWire
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=signalwire-relay-application-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/signalwire-relay-application-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of SignalWire Relay Application 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.