Addresses3

AI Agents: Custom6

AI Agents: Dialogflow5

AI Chat1

Alias Addresses5

Call Flows8

Caller ID Name3

Calls1

Campaign Registry: Brands4

Campaign Registry: Campaigns4

Campaign Registry: Phone Number Assignments5

Chat Tokens1

Chunks3

Conference Logs1

Conference Rooms6

Conference Tokens3

cXML Applications5

cXML Scripts6

cXML Webhook6

Documents6

Domain Applications1

E911 Addresses7

Fax Logs2

FreeSWITCH Connector6

Imported Phone Numbers1

Message Logs2

Messages2

Multi-Factor Authentication3

Number Group Membership4

Number Groups5

Phone Number Addresses5

Phone Number Lookup1

Phone Numbers6

Phone Routes1

Project Tokens3

Projects6

PubSub Tokens1

Queue Members3

Queues5

Recordings3

Relay Application6

Resources3

Room Recordings4

Room Sessions5

Room Tokens1

Rooms6

Short Codes3

SIP Addresses5

SIP Credentials7

SIP Endpoints (Legacy)5

SIP Gateway6

SIP Profile2

Space4

Space Balance4

Space Billing10

Space Domain Applications5

Space Members8

Streams7

Subscriber SIP Credentials5

Subscriber Tokens5

Subscribers6

SWML Scripts6

SWML Webhook6

Verified Caller ID7

Video Conferences5

Video Logs2

Voice Logs3

WhatsApp Businesses1

WhatsApp Numbers2

WhatsApp Routes1

WhatsApp Templates5

Webhooks

AI Webhooks8

Calling Webhooks3

Messaging Webhooks3

Call Flows

Deploy call flow version

Makes one saved Call Flow version active, selected by document version or version ID. Use it after updating a visual flow when that revision is ready to handle calls; updating the Call Flow saves a revision but does not replace this deployment step. Directly authored SWML Scripts do not use Call Flow versions.

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.

post/api/fabric/resources/call_flow/{id}/versions

Path parameters

idstring required

The unique identifier of the Call Flow.

Request body

Example request

{
  "document_version": 2
}

Response

The request has succeeded and a new resource has been created as a result.

idstring uuid required

Universal Unique Identifier.

created_atstring required

The creation timestamp.

updated_atstring required

The last update timestamp.

document_versioninteger required

The document version.

flow_dataobject

Call Flow Builder state, stored as an opaque JSON object.

relaymlobject

The calling SWML document deployed by this version. Uses calling SWML methods.

Example response

{
  "created_at": "2024-01-02T00:00:00Z",
  "updated_at": "2024-01-02T00:00:00Z",
  "document_version": 2,
  "flow_data": {},
  "relayml": {
    "version": "1.0.0",
    "sections": {
      "main": [
        {
          "play": {
            "url": "https://cdn.signalwire.com/swml/audio.mp3"
          }
        }
      ]
    }
  }
}

Changes

Changed in 33 of the 161 revisions of this API.139184448

Aug 20, 2026e79dcc8b215012See the full diff
- ▲
  the response's property type changed from no type to object for status
  response-property-type-changed
- ○
  removed from the response property allOf list for the response status
  response-property-all-of-removed
- ○
  added 'unevaluatedProperties' constraint to the response property for the status
  response-property-unevaluated-properties-added
This revision also has 11 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
Aug 18, 202651e63ae4cf5534See the full diff
- ▲
  the ///////// response's property type changed from no type to object for status
  response-property-type-changed
- ▲
  the ///////////////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the ///////////////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the ////////////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the ////////////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the ///////////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the ///////////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the ////////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the ////////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the ///////////////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the ///////////////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the ////////////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the ////////////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the ///////////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the ///////////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the ////////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the ////////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the ///////// response's property type changed from no type to object for status
  response-property-type-changed
- ▲
  the ///////////////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the ///////////////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the ////////////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the ////////////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the ///////////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the ///////////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the ////////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the ////////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the ///////////////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the ///////////////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the ////////////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the ////////////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the ///////////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the ///////////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the ////////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the ////////////////// response's property type changed from array to no type for status
  response-property-type-changed
This revision's changelog hit the recording limit, so it may not list every change to this endpoint.
This revision also has 26 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
Aug 13, 20261e361d3f91b34See the full diff
- ○
  added subschema #1 subschema #2 subschema #3 subschema #4 to the ///////////////// response property anyOf list for the response status
  response-property-any-of-added
- ○
  added subschema #1 subschema #2 subschema #3 subschema #4 to the ///////////////// response property anyOf list for the response status
  response-property-any-of-added
- ○
  removed subschema #1 subschema #2 subschema #3 subschema #4 from the ///////////////// response property anyOf list for the response status
  response-property-any-of-removed
- ○
  removed subschema #1 subschema #2 subschema #3 subschema #4 from the ///////////////// response property anyOf list for the response status
  response-property-any-of-removed
This revision also has 1 change that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
Aug 13, 20261e3d98618de04See the full diff
- ○
  added subschema #1 subschema #2 subschema #3 subschema #4 to the ///////////////// response property anyOf list for the response status
  response-property-any-of-added
- ○
  added subschema #1 subschema #2 subschema #3 subschema #4 to the ///////////////// response property anyOf list for the response status
  response-property-any-of-added
- ○
  removed subschema #1 subschema #2 subschema #3 subschema #4 from the ///////////////// response property anyOf list for the response status
  response-property-any-of-removed
- ○
  removed subschema #1 subschema #2 subschema #3 subschema #4 from the ///////////////// response property anyOf list for the response status
  response-property-any-of-removed
This revision also has 2 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
Aug 13, 2026549e44d6120b6436See the full diff
- ▲
  the response property /////////////////// became optional for the status
  response-property-became-optional
- ▲
  the response property ///////////////// became optional for the status
  response-property-became-optional
- ▲
  the response property ///////////////////// became optional for the status
  response-property-became-optional
- ▲
  the response property /////////////////// became optional for the status
  response-property-became-optional
- ▲
  the response property /////////////////// became optional for the status
  response-property-became-optional
- ▲
  the response property ///////////////// became optional for the status
  response-property-became-optional
- ▲
  the response property ///////////////////// became optional for the status
  response-property-became-optional
- ▲
  the response property /////////////////// became optional for the status
  response-property-became-optional
- ▲
  the response property /////////////////// became optional for the status
  response-property-became-optional
- ▲
  the response property ///////////////// became optional for the status
  response-property-became-optional
- ▲
  the response property ///////////////////// became optional for the status
  response-property-became-optional
- ▲
  the response property /////////////////// became optional for the status
  response-property-became-optional
- ▲
  the response property /////////////////// became optional for the status
  response-property-became-optional
- ▲
  the response property ///////////////// became optional for the status
  response-property-became-optional
- ▲
  the response property ///////////////////// became optional for the status
  response-property-became-optional
- ▲
  the response property /////////////////// became optional for the status
  response-property-became-optional
- ▲
  the response property /////////////////// became optional for the status
  response-property-became-optional
- ▲
  the response property ///////////////// became optional for the status
  response-property-became-optional
- ▲
  the response property ///////////////////// became optional for the status
  response-property-became-optional
- ▲
  the response property /////////////////// became optional for the status
  response-property-became-optional
- ▲
  the response property /////////////////// became optional for the status
  response-property-became-optional
- ▲
  the response property ///////////////// became optional for the status
  response-property-became-optional
- ▲
  the response property ///////////////////// became optional for the status
  response-property-became-optional
- ▲
  the response property /////////////////// became optional for the status
  response-property-became-optional
- ▲
  the response property /////////////////// became optional for the status
  response-property-became-optional
- ▲
  the response property ///////////////// became optional for the status
  response-property-became-optional
- ▲
  the response property ///////////////////// became optional for the status
  response-property-became-optional
- ▲
  the response property /////////////////// became optional for the status
  response-property-became-optional
- ▲
  the response property /////////////////// became optional for the status
  response-property-became-optional
- ▲
  the response property ///////////////// became optional for the status
  response-property-became-optional
- ▲
  the response property ///////////////////// became optional for the status
  response-property-became-optional
- ▲
  the response property /////////////////// became optional for the status
  response-property-became-optional
- ▲
  the /////////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the ///////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the ///////////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the /////////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the /////////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the ///////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the ///////////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the /////////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the /////////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the ///////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the ///////////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the /////////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the /////////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the ///////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the ///////////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the /////////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the /////////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the ///////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the ///////////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the /////////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the /////////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the ///////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the ///////////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the /////////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the /////////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the ///////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the ///////////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the /////////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the /////////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the ///////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the ///////////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ▲
  the /////////////////// response's property type changed from array to no type for status
  response-property-type-changed
- ○
  added subschema #2 to the /////////////////// response property anyOf list for the response status
  response-property-any-of-added
- ○
  added subschema #2 to the ///////////////// response property anyOf list for the response status
  response-property-any-of-added
- ○
  added subschema #2 to the ///////////////////// response property anyOf list for the response status
  response-property-any-of-added
- ○
  added subschema #2 to the /////////////////// response property anyOf list for the response status
  response-property-any-of-added
- ○
  added subschema #2 to the /////////////////// response property anyOf list for the response status
  response-property-any-of-added
- ○
  added subschema #2 to the ///////////////// response property anyOf list for the response status
  response-property-any-of-added
- ○
  added subschema #2 to the ///////////////////// response property anyOf list for the response status
  response-property-any-of-added
- ○
  added subschema #2 to the /////////////////// response property anyOf list for the response status
  response-property-any-of-added
- ○
  added subschema #2 to the /////////////////// response property anyOf list for the response status
  response-property-any-of-added
- ○
  added subschema #2 to the ///////////////// response property anyOf list for the response status
  response-property-any-of-added
- ○
  added subschema #2 to the ///////////////////// response property anyOf list for the response status
  response-property-any-of-added
- ○
  added subschema #2 to the /////////////////// response property anyOf list for the response status
  response-property-any-of-added
- ○
  added subschema #2 to the /////////////////// response property anyOf list for the response status
  response-property-any-of-added
- ○
  added subschema #2 to the ///////////////// response property anyOf list for the response status
  response-property-any-of-added
- ○
  added subschema #2 to the ///////////////////// response property anyOf list for the response status
  response-property-any-of-added
- ○
  added subschema #2 to the /////////////////// response property anyOf list for the response status
  response-property-any-of-added
- ○
  added subschema #2 to the /////////////////// response property anyOf list for the response status
  response-property-any-of-added
- ○
  added subschema #2 to the ///////////////// response property anyOf list for the response status
  response-property-any-of-added
- ○
  added subschema #2 to the ///////////////////// response property anyOf list for the response status
  response-property-any-of-added
- ○
  added subschema #2 to the /////////////////// response property anyOf list for the response status
  response-property-any-of-added
- ○
  added subschema #2 to the /////////////////// response property anyOf list for the response status
  response-property-any-of-added
- ○
  added subschema #2 to the ///////////////// response property anyOf list for the response status
  response-property-any-of-added
- ○
  added subschema #2 to the ///////////////////// response property anyOf list for the response status
  response-property-any-of-added
- ○
  added subschema #2 to the /////////////////// response property anyOf list for the response status
  response-property-any-of-added
- ○
  added subschema #2 to the /////////////////// response property anyOf list for the response status
  response-property-any-of-added
- ○
  added subschema #2 to the ///////////////// response property anyOf list for the response status
  response-property-any-of-added
- ○
  added subschema #2 to the ///////////////////// response property anyOf list for the response status
  response-property-any-of-added
- ○
  added subschema #2 to the /////////////////// response property anyOf list for the response status
  response-property-any-of-added
- ○
  added subschema #2 to the /////////////////// response property anyOf list for the response status
  response-property-any-of-added
- ○
  added subschema #2 to the ///////////////// response property anyOf list for the response status
  response-property-any-of-added
- ○
  added subschema #2 to the ///////////////////// response property anyOf list for the response status
  response-property-any-of-added
- ○
  added subschema #2 to the /////////////////// response property anyOf list for the response status
  response-property-any-of-added
- ○
  added subschema #1 subschema #2 subschema #3 subschema #4 to the ///////////////// response property anyOf list for the response status
  response-property-any-of-added
- ○
  added subschema #1 subschema #2 subschema #3 subschema #4 to the ///////////////// response property anyOf list for the response status
  response-property-any-of-added
- ○
  removed subschema #1 subschema #2 subschema #3 subschema #4 from the ///////////////// response property anyOf list for the response status
  response-property-any-of-removed
- ○
  removed subschema #1 subschema #2 subschema #3 subschema #4 from the ///////////////// response property anyOf list for the response status
  response-property-any-of-removed
This revision also has 1 change that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
Aug 7, 2026ad46a79d07e44See the full diff
- ●
  removed the optional property //////////////// from the response with the status
  response-optional-property-removed
- ●
  removed the optional property //////////////// from the response with the status
  response-optional-property-removed
- ●
  removed the optional property //////////////// from the response with the status
  response-optional-property-removed
- ●
  removed the optional property //////////////// from the response with the status
  response-optional-property-removed
This revision also has 2 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
Jul 23, 2026e8d17946d2de6See the full diff
- ○
  added the optional property ////////// to the response with the status
  response-optional-property-added
- ○
  added the optional property ////////// to the response with the status
  response-optional-property-added
- ○
  added the optional property ////////// to the response with the status
  response-optional-property-added
- ○
  added the optional property ////////// to the response with the status
  response-optional-property-added
- ○
  added the optional property ////////// to the response with the status
  response-optional-property-added
- ○
  added the optional property ////////// to the response with the status
  response-optional-property-added
Jul 21, 2026bbd9474198176See the full diff
- ●
  removed the optional property ////////// from the response with the status
  response-optional-property-removed
- ●
  removed the optional property ////////// from the response with the status
  response-optional-property-removed
- ●
  removed the optional property ////////// from the response with the status
  response-optional-property-removed
- ●
  removed the optional property ////////// from the response with the status
  response-optional-property-removed
- ●
  removed the optional property ////////// from the response with the status
  response-optional-property-removed
- ●
  removed the optional property ////////// from the response with the status
  response-optional-property-removed
Jul 21, 2026f1aae4e315dd6See the full diff
- ○
  added the optional property ////////// to the response with the status
  response-optional-property-added
- ○
  added the optional property ////////// to the response with the status
  response-optional-property-added
- ○
  added the optional property ////////// to the response with the status
  response-optional-property-added
- ○
  added the optional property ////////// to the response with the status
  response-optional-property-added
- ○
  added the optional property ////////// to the response with the status
  response-optional-property-added
- ○
  added the optional property ////////// to the response with the status
  response-optional-property-added
Jul 20, 20266e5c9df703692See the full diff
- ○
  the response's property default value changed from gcloud_speech_v2_async to deepgram:nova-3 for the status
  response-property-default-value-changed
- ○
  the response's property default value changed from gcloud_speech_v2_async to deepgram:nova-3 for the status
  response-property-default-value-changed
This revision also has 42 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

Of the 161 revisions, 3 have a changelog that could not be searched.

Full history (33 revisions)