Track usage, costs, and application health for Twilio Programmable Voice

You can track the usage and costs for your Twilio Programmable Voice applications in the Twilio Console, with the Twilio API's UsageRecord resource, or with the Twilio Datadog integration. Check Resolving call log and call usage discrepancies for common issues and solutions.

To track the usage and costs for your Programmable Voice application in the Twilio Console, view the Usage and Spend section:

You can also set alert triggers to notify you by email or webhook when your application reaches a certain usage threshold:

To pull usage and cost data for your voice applications programmatically, you can use the UsageRecords resource:

1. Find your Account SID and Auth Token:

   Twilio ConsoleLegacy Console

   1. On the Twilio Console landing page, under Let's get building, click API keys and Auth tokens.
   2. Click the Auth Tokens tab to find your Account SID and Auth Token. Copy these values for the next step.

2. Set the environment variables for your Account SID and Auth Token.

   (warning)

   Improve security with API keys

   To better control access, use API keys instead of the Account SID and Auth Token when you deploy to production. To learn more, see Why you should use API keys.

   On Mac or Linux:

   1. Run the following commands to add your credentials as environment variables in a twilio.env file and source them. Replace ACXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX with your Account SID and replace your_auth_token with your Auth Token.

      Copy code block

      1
      echo "export TWILIO_ACCOUNT_SID='ACXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX'" > twilio.env
      2
      echo "export TWILIO_AUTH_TOKEN='your_auth_token'" >> twilio.env
      3
       source ./twilio.env

   2. If you're committing code with Git, run the following command to add the twilio.env file to .gitignore to avoid uploading your credentials in plain text:

      Copy code block

      echo "twilio.env" >> .gitignore

   On Windows command line (cmd.exe), run the following commands. Replace ACXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX with your Account SID and replace your_auth_token with your Auth Token.

   Copy code block

   1
   set TWILIO_ACCOUNT_SID=ACXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
   2
   set TWILIO_AUTH_TOKEN=your_auth_token

   To learn more, see Store your Twilio credentials safely.

3. Make a GET request to the API endpoint for the desired time period and filters to retrieve usage and cost data for your voice applications. For example, to retrieve voice usage and cost data for the current month using cURL, you can make the following request:

   Copy code block

   1
   curl -X GET "https://api.twilio.com/2010-04-01/Accounts/$TWILIO_ACCOUNT_SID/Usage/Records/LastMonth.json?Category=calls&PageSize=20" \
   2
   -u $TWILIO_ACCOUNT_SID:$TWILIO_AUTH_TOKEN

   For more info and examples, see Read multiple UsageRecord resources.

To view Twilio usage and cost data alongside your other business metrics, you can use the Twilio Datadog integration to pull usage and cost data into your Datadog dashboard:

1. Generate an API key and find your Account SID:

   Twilio ConsoleLegacy Console

   1. On the Twilio Console landing page, under Let's get building, click API keys and Auth tokens.
   2. Click the API Keys tab.
   3. Click the Create API Key button and follow the prompts to generate a new API key. Copy the generated API key and secret and paste them in a temporary local file for use when you connect to Datadog.
   4. Copy your Account SID in the Twilio Console landing page under Let's get building. Paste it in the temporary local file.

2. Follow the steps in the Twilio Datadog integration documentation to connect your Twilio account to Datadog using your Account SID, API key, and secret from the temporary local file.

After you connect your Twilio account to Datadog, you can view your Twilio usage and cost data in your Datadog Cloud Cost Management dashboard alongside your other business metrics.

To track the health of your Twilio Programmable Voice applications, you can set alert triggers to notify you by email or webhook when application errors occur.

This guide applies to the following use cases:

You can use this guide to track the delivery costs and performance metrics of your voice notifications. For example, you can monitor billing thresholds to ensure your alert systems remain cost-effective.

To learn more advanced features that you can use with voice notifications, see Voice notifications.

You can use this guide to analyze and break down phone call usage and operational expenses across your campaigns. This helps you identify which numbers or tracking resources generate the highest ROI or call volume.

To learn more advanced features that you can use with call tracking, see Voice call tracking.

After following this guide, you can monitor your Twilio Programmable Voice metrics programmatically and through external dashboards. You might also have created alert triggers to immediately notify your team by email or webhook when unexpected usage spikes or application errors occur.

Explore the following guides to build on what you've learned in this guide:

• Retrieve call logs: Review complete records of your call data and activities.

Find reference documentation for the topics on this page.

• UsageRecords resource