Bandwidth

undefined

Detail	Value
Category	Communication
Base URL	https://messaging.bandwidth.com/api/v2
Authentication	API Key
Endpoints	6
Connector key	bandwidth

Using Bandwidth in a workflow

1. Go to Connections and click New Connection.
2. Pick Bandwidth from the marketplace.
3. Enter your credentials (see Authentication above for what's expected).
4. In a workflow, drop an API Call node and select this connection.
5. Pick the operation you need from the Operation dropdown — the full list is below.

Available endpoints

Endpoint	Summary
GET	Send Message
GET	List Messages
GET	Create Call
GET	Get Call
GET	List Recordings
GET	List Applications

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET

Send Message

Detail	Value
Operation ID	send_message_0
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Bandwidth connection from the Connection dropdown.
3. In the Operation dropdown, select send_message_0.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Bandwidth API reference.

GET

List Messages

Detail	Value
Operation ID	list_messages_1
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Bandwidth connection from the Connection dropdown.
3. In the Operation dropdown, select list_messages_1.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Bandwidth API reference.

GET

Create Call

Detail	Value
Operation ID	create_call_2
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Bandwidth connection from the Connection dropdown.
3. In the Operation dropdown, select create_call_2.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Bandwidth API reference.

GET

Get Call

Detail	Value
Operation ID	get_call_3
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Bandwidth connection from the Connection dropdown.
3. In the Operation dropdown, select get_call_3.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Bandwidth API reference.

GET

List Recordings

Detail	Value
Operation ID	list_recordings_4
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Bandwidth connection from the Connection dropdown.
3. In the Operation dropdown, select list_recordings_4.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Bandwidth API reference.

GET

List Applications

Detail	Value
Operation ID	list_applications_5
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Bandwidth connection from the Connection dropdown.
3. In the Operation dropdown, select list_applications_5.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Bandwidth API reference.