Send Call

Your API key for authentication.

A special key for using a BYOT (Bring Your Own Twilio) account. Only required for sending calls from your own Twilio account.

The phone number to call. Must be a valid phone number in E.164 format.

Specify a phone number to call from that you own or have uploaded from your Twilio account. Country code is required, spaces or parentheses must be excluded.

By default, calls are initiated from a separate pool of numbers owned by Bland. If you are using your own twilio numbers, you must specify a matching encrypted_key in the create call request headers.

This is the pathway ID for the pathway you have created on our dev portal. You can access the ID of your pathways by clicking the ‘Copy ID’ button of your pathway here

Note: Certain parameters do not apply when using pathways.

Example Simple Request body:

{
  "phone_number": "+1975934749",
  "pathway_id": "a0f0d4ed-f5f5-4f16-b3f9-22166594d7a7"
}

Note: Do not specify if using a pathway.

Provide instructions, relevant information, and examples of the ideal conversation flow.

This is your prompt where you are telling the agent what to do.

Recommendations:

• Include context and a background/persona for the agent like "You are {name}, a customer service agent at {company} calling {name} about {reason}.
• Phrase instructions like you are speaking to the agent before the call.
• Any time you tell the agent not to do something, provide an example of what they should do instead.
• Keep the prompt under 2,000 characters where possible.

The voice of the AI agent to use. Accepts any form of voice ID, including custom voice clones and voice presets.

Default voices can be referenced directly by their name instead of an id.

Usage example: voice: “maya”

Bland Curated voices:

• Josh
• Florian
• Derek
• June
• Nat
• Paige

The ID of the persona to use for the call.

Personas act as pre-configured templates that automatically apply a configuration when you pass a persona_id to an outbound call. Think of them as “call presets” that you can reuse across multiple calls.

When using a persona_id, any parameters specified in your request body will override the corresponding parameters from the persona’s configuration.

You can access your persona IDs by clicking the “Personas” button at the bottom of the Send Call page, and then “Use and Manage”.

Select an audio track that you’d like to play in the background during the call. The audio will play continuously when the agent isn’t speaking, and is incorporated into it’s speech as well.

Use this to provide a more natural, seamless, engaging experience for the conversation. We’ve found this creates a significantly smoother call experience by minimizing the stark differences between total silence and the agent’s speech.

Options:

• null - Default, will play audible but quiet phone static.
• office - Office-style soundscape. Includes faint typing, chatter, clicks, and other office sounds.
• cafe - Cafe-like soundscape. Includes faint talking, clinking, and other cafe sounds.
• restaurant - Similar to cafe, but more subtle.
• none - Minimizes background noise

Makes your agent say a specific phrase or sentence for it’s first response.

(Optional) Custom instructions for how the call summary should be generated after the call completes. Use this to provide specific guidance or context for the AI when writing the post-call summary. Maximum length: 2000 characters.

Example:

{
  "summary_prompt": "Summarize the call in 2-3 sentences, focusing on the customer's main concern and any next steps discussed."
}

By default, the agent starts talking as soon as the call connects.

When wait_for_greeting is set to true, the agent will wait for the call recipient to speak first before responding.

When set to true, the AI will not respond or process interruptions from the user.

Adjusts how patient the AI is when waiting for the user to finish speaking.

Lower values mean the AI will respond more quickly, while higher values mean the AI will wait longer before responding.

Recommended range: 50-200 • 50: Extremely quick, back and forth conversation • 100: Balanced to respond at a natural pace • 200: Very patient, allows for long pauses and interruptions. Ideal for collecting detailed information.

Try to start with 100 and make small adjustments in increments of ~10 as needed for your use case.

Select a model to use for your call.

Options: base or turbo.

In nearly all cases, base is the best choice.

A value between 0 and 1 that controls the randomness of the LLM. 0 will cause more deterministic outputs while 1 will cause more random.

Example Values: “0.9”, “0.3”, “0.5”

Integrate data from external APIs into your agent’s knowledge.

Set to null or an empty string to clear dynamic data settings.

  "dynamic_data": [
    {
      "url": "endpoint",
      "method": "GET",
      "body": [],
      "headers": [
        {
          "key": "Content-Type",
          "value": "application/json"
        }
      ],
      "query": [],
      "cache": true,
      "response_data": [
        {
          "context": "",
          "data": "$",
          "name": ""
        }
      ]
    }
  ],

These words will be boosted in the transcription engine - recommended for proper nouns or words that are frequently mis-transcribed.

For example, if the word Blandy is frequently transcribed as a homonym like “Reese” you could do this:

  {
    "keywords": ["Blandy"]
  }

For stronger keyword boosts, you can place a colon then a boost factor after the word. The default boost factor is 2.

  {
    "keywords": ["Blandy:3"]
  }

The pronunciation guide is an array of objects that guides the agent on how to say specific words. Use this to improve clarity for acronyms, names, brand terms, or jargon.

  [
    {
      "word": "example",
      "pronunciation": "ex-am-ple",
      "case_sensitive": "false",
      "spaced": "false"
  },
  {
    "word": "API",
    "pronunciation": "A P I",
    "case_sensitive": "true",
    "spaced": "true"
  }
]

A phone number that the agent can transfer to under specific conditions - such as being asked to speak to a human or supervisor. This option will be ignored for pathways.

Give your agent the ability to transfer calls to a set of phone numbers. This option will be ignored for pathways.

Overrides transfer_phone_number if a transfer_list.default is specified.

Will default to transfer_list.default, or the chosen phone number.

Example usage to route calls to different departments:

{
  "transfer_list": {
      "default": "+12223334444",
      "sales": "+12223334444",
      "support": "+12223334444",
      "billing": "+12223334444"
  }
}

Select a supported language of your choice. Optimizes every part of our API for that language - transcription, speech, and other inner workings.

The version number of the pathway to use for the call. Defaults to the production version.

When true, automatically selects a “from” number that matches the callee’s area code for US-based calls. Must have purchased a local dialing add-on in the add-ons section.

Configure SMS settings for voicemail notifications. If a voicemail is left, an SMS message is sent to the “to” number. Requires SMS configuration.

Properties:

• from (string): The phone number to send the SMS from
• message (string): The message template to send when a voicemail is left

Example:

{
  "to": "+18001234567",
  "message": "You have a new voicemail!"
}

Restricts calls to certain hours in your timezone. Specify the timezone and time windows using 24-hour format.

Supported time formats: • 24-hour: “13:00”, “09:30” • 12-hour: “1:00pm”, “9:30am” • Military: “1300”, “0930”

Example:

{
  "start": "09:00",
  "end": "17:00"
}

The times will be automatically converted to UTC for processing. If the end time is before the start time (e.g. “22:00” to “06:00”), it will be interpreted as spanning overnight.

When true, uses LLM-based analysis to detect frequent voicemails.

When true, the system will ignore DTMF input (Dual-Tone Multi-Frequency) — the tones generated when a user presses keys on their phone keypad (e.g., 0-9, *, #).
This disables any in-call actions triggered by keypad input, such as menu navigation or transfers.
Useful when your agent should handle the entire call conversationally, without responding to button presses.

Set the timezone for the call. Handled automatically for calls in the US.

This helps significantly with use cases that rely on appointment setting, scheduling, or behaving differently based on the time of day.

Timezone options are here in the TZ identifier column.

Custom key-value data you send with the call. This information is available as variables inside your prompt, pathway, or tools — but only if the call is answered.

  {
    "task": "Say hello to the user, who's name is {{name}}",
    "request_data": {
      "name": "John Doe"
    }
  }

In this case, the AI would say: “Hello, John”.

Interact with the real world through API calls.

Detailed tutorial here: Custom Tools

The time you want the call to start. If you don’t specify a time (or the time is in the past), the call will send immediately.

Set your time in the format YYYY-MM-DD HH:MM:SS -HH:MM (ex. 2021-01-01 12:00:00 -05:00).

The timezone is optional, and defaults to UTC if not specified.

Note: Scheduled calls can be cancelled with the POST /v1/calls/:call_id/stop endpoint.

When the AI encounters a voicemail, it will leave this message after the beep and then immediately end the call.

Warning: If ivr_mode is set to true or voicemail_action is set to ignore, then this will still work for voicemails, but it will not hang up for IVR systems.

This is processed separately from the AI’s decision making, and overrides it.

Options:

• hangup
• leave_message
• ignore

Examples:

• Call is answered by a voicemail (specifically with a beep or tone):
• If voicemail_message is set, that message will be left and then the call will end.
• Otherwise, the call immediately ends (regardless of ivr_mode)
• Call is answered by an IVR system or phone tree:
• If ivr_mode is set to true, the AI will navigate the system and continue as normal.
• If voicemail_action is set to ignore, the AI will ignore the IVR and continue as normal.
• Otherwise, if voicemail_message is set then it’ll leave that message and end the call.
• Finally, if none of those conditions are met, the call will end immediately.

Note: If voicemail_message is set, then the AI will leave the message regardless of the voicemail_action.

If the call goes to voicemail, you can set up the call to retry, after a configurable delay. You can also update the voicemail_action, and voicemail_message in the retry object, for the re-tried call.

Takes in the following parameters:

• wait (integer): The delay in seconds before the call is retried.
• voicemail_action (enum): The action to take when the call goes to voicemail. Options: hangup, leave_message, ignore.
• voicemail_message (string): The message to leave when the call goes to voicemail.

Example:

{
    "retry": {
        "wait": 10,
        "voicemail_action": "leave_message",
        "voicemail_message": "Hello, this is a test message."
    }
}

When the call starts, a timer is set for the max_duration minutes. At the end of that timer, if the call is still active it will be automatically ended.

Example Values: 20, 2

To record your phone call, set record to true. When your call completes, you can access through the recording_url field in the call details or your webhook.

When the call ends, call information is sent to this webhook URL.

Specify which events you want to stream to the webhook, during the call.

Options:

• queue
• call
• latency
• webhook
• tool
• dynamic_data
• citations (Sent separately, Enterprise only)

Example payloads:

// ex 1
{
  "message": "Call enqueued",
  "call_id": "12345678-1234-1234-1234-123456789abc",
  "category": "queue",
  "log_level": "info"
}

Add any additional information you want to associate with the call. This data is accessible for all calls, regardless of if they are picked up or not. This can be used to track calls or add custom data to the call.

Anything that you put here will be returned in the post call webhook under metadata.

Example:

{
  "metadata": {
    "campaign_id": "1234",
    "source": "web"
  }
}

The citation schema is an incredibly powerful tool for running post call analysis, including specific variable extractions, conditional logic, and more.

You can build a citation schema here.

After building the citation schema (or schemas), you can copy their UUIDs and reference them in your API request for outgoing calls (and you can also attach them to your inbound phone numbers).

Here’s an example:

{
  "citation_schema_ids": ["dcad76eb-57b6-4be6-922f-8a5a95e2ffrt"]
}

Note: Citation schemas are very powerful and accurate, but also are more resource intensive to run. As such, for the time being, they are an enterprise-only feature.

The analysis preset UUID used to analyze the call, must be created on the analysis presets page.

All fields in the preset configuration are filled at the end of the call by analyzing the transcript.

Example:

  {
    "analysis_preset": "a0f0d4ed-f5f5-4f16-b3f9-22166594d7a7"
  }

An array of disposition tags. Uopon call completion, the AI will evaluate the transcripts of the call and assign one of the tags to the “disposition_tag” field. Tags are assigned exclusively by looking at the transcript and no other information.

Example:

  {
    "available_tags": ["got_full_name_and_number", "no_information_provided", "transferred_to_agent"]
  }

The geospatial dialing pool UUID. This is an enterprise only feature, to use this feature contact your Bland representative or reach out to sales.

Example:

  {
    "geospatial_dialing": "bd039087-decb-435a-a6e3-ca1ffbf89974"
  }

A sequence of DTMF digits that will be played before the call starts. Acceptable characters are 0-9, *, #, and w, where w is a pause of 0.5 seconds. Example:

  {
    "precall_dtmf_sequence": "1234567890*#w"
  }

Can be success or error.

A unique identifier for the call (present only if status is success).

The batch ID of the call (present only if status is success).

A message explaining the status of the call.

For validation errors, a detailed list of each field with an error and it’s error message.

Example:

{
    "status": "error",
    "message": "Invalid parameters",
    "errors": [
        "Missing required parameter: phone_number.",
        "Missing required parameter: task.",
        "Phone number must be a string or number.",
        "Task must be a string."
    ]
}