Azure Communication Call Automation client library for Python

This package contains a Python SDK for Azure Communication Call Automation. Call Automation provides developers the ability to build server-based, intelligent call workflows, and call recording for voice and PSTN channels.

Overview of Call Automation | Product documentation

Disclaimer

Azure SDK Python packages support for Python 2.7 has ended 01 January 2022. For more information and questions, please refer to https://github.com/Azure/azure-sdk-for-python/issues/20691

Security notice: version 1.6.0 deprecated

Version 1.6.0 of azure-communication-callautomation is deprecated as of 2026-10-22 because of a recording URL validation security issue. This notice applies to version 1.6.0, not to the library as a whole.

In applications that pass attacker-influenced recording URLs to the synchronous download_recording or delete_recording methods using the default Requests transport, an ambiguous URL can bypass hostname validation and send an authenticated request to an unintended endpoint, potentially exposing a Bearer token.

Upgrade to 1.6.1 or a later fixed release to receive the security fix. Use only service-generated recording URLs received through trusted, integrity-protected events; do not pass untrusted recording URLs to these methods.

Refer to the release history and Azure SDK support policy for more information.

Getting started

Prerequisites

• Python 3.8 or later is required to use this package.
• You need an Azure subscription to use this package.
• A deployed Communication Services resource. You can use the Azure Portal or the Azure PowerShell to set it up.

Installing

Install the Azure Communication Service Call Automation SDK.

pip install azure-communication-callautomation

Key concepts

Recording URL security

download_recording and delete_recording accept only HTTPS URLs with ASCII DNS hostnames under *.asm.skype.com, *.asyncgw.teams.microsoft.com, or *.ams.gov.teams.microsoft.us. URLs containing user information, raw backslashes, whitespace, control characters, or malformed authorities are rejected with ValueError before authentication. Redirect destinations are subject to the same validation. Valid signed query parameters are preserved.

Use service-generated recording URLs from trusted, integrity-protected events.

Examples

Initialize CallAutomationClient

from azure.identity import DefaultAzureCredential
from azure.communication.callautomation import (CallAutomationClient)

# Your unique Azure Communication service endpoint
endpoint_url = '<ENDPOINT>'
credential = DefaultAzureCredential()
client = CallAutomationClient(endpoint_url, credential)

Create Call

from azure.communication.callautomation import (
    CallAutomationClient,
    CommunicationUserIdentifier
)

# target endpoint for ACS User
user = CommunicationUserIdentifier("8:acs:...")

# callback url to receive callback events
callback_url = "https://<MY-EVENT-HANDLER-URL>/events"

# send out the invitation, creating call
result = client.create_call(
    target_participant=user,
    callback_url=callback_url
)

# this id can be used to do further actions in the call
call_connection_id = result.call_connection_id

Play Media

# using call connection id, get call connection
call_connection = client.get_call_connection(call_connection_id)

# from callconnection of result above, play media to all participants
my_file = FileSource(url="https://<FILE-SOURCE>/<SOME-FILE>.wav")
call_connection.play_to_all(my_file)

Troubleshooting

Next steps

• Call Automation Overview
• Incoming Call Concept
• Build a customer interaction workflow using Call Automation
• Redirect inbound telephony calls with Call Automation
• Quickstart: Play action
• Quickstart: Recognize action
• Read more about Call Recording in Azure Communication Services
• Record and download calls with Event Grid

Provide Feedback

If you encounter any bugs or have suggestions, please file an issue in the Issues section of the project

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the [Microsoft Open Source Code of Conduct][code_of_conduct]. For more information, see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.