Sign in
Relay Application

Update Relay application

Changes where a Relay Application sends events or call-status updates while preserving the same Fabric resource. Update a SWML Webhook or Call Flow through its own resource endpoint instead.

Permissions

The API token used to authenticate must have the following scope(s) enabled to make a successful request: Voice, Messaging, Fax, or Video.

Learn more about API scopes.

put/api/fabric/resources/relay_applications/{id}

Path parameters

idstring uuid required

Universal Unique Identifier.

Unique ID of a Relay Application.

Request body

namestring

Name of the Relay Application

topicstring

Topic of the Relay Application

call_status_callback_urlstring

Call status callback URL

Example request

{
  "name": "Booking Assistant",
  "topic": "booking",
  "call_status_callback_url": "https://booking.com/callbacks"
}

Response

The request has succeeded.

idstring uuid required

Universal Unique Identifier.

project_idstring uuid required

Universal Unique Identifier.

display_namestring required

Display name of the Relay Application Fabric Resource

type'relay_application' required

Type of the Fabric Resource

created_atstring date-time required

Date and time when the resource was created.

updated_atstring date-time required

Date and time when the resource was updated.

Example response

{
  "display_name": "Customer Service Bot",
  "type": "relay_application",
  "created_at": "2024-05-06T12:20:00Z",
  "updated_at": "2024-05-06T12:20:00Z",
  "relay_application": {
    "name": "Booking Assistant",
    "topic": "booking",
    "call_status_callback_url": "https://example.com/callbacks"
  }
}

Changes

No changes found, but 3 of the 137 revisions have a changelog that could not be searched — this endpoint may have changed in one of them.