---
title: 'POST /Accounts/{AccountSid}/Calls.json'
description: 'Make a phone call'
---

# POST /Accounts/{AccountSid}/Calls.json

Make a phone call

| Detail | Value |
|---|---|
| Operation ID | `messaging.makeCall` |
| Method | `POST` |
| Path | `/Accounts/{AccountSid}/Calls.json` |
| Connector | [Twilio](./) |

## Parameters

| Name | Location | Type | Required |
|---|---|---|---|
| `AccountSid` | path | string | **Yes** |

## Request Body

| Field | Type |
|---|---|
| `To` | string |
| `From` | string |
| `Url` | string |


## Using this endpoint in a workflow

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

**Required fields are marked — fill them or the call will fail at runtime.**

## 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 <code v-pre>{{nodeId.data.path}}</code>. The exact response shape is documented on the upstream Twilio API reference.