An icon of a right arrow Back

Twilio Changelog | Jun. 05, 2024

TaskRouter APIs now supported on Restricted API Keys

You can now select permissions for TaskRouter APIs while creating a Restricted API Key on Console. The product already supports permissions for Studio, Voice, SIP, Messages, Regulatory Compliance and Long Codes APIs.

Restricted API Keys allow you to decide which Twilio API Resources an API Key can access, and which action(s) the API Key is allowed to take on those API Resources.

Restricted API Keys is now available to all customers as a Public Beta offering. Customers can create and manage Restricted API Keys on Console.

  • Customers will see a new type ‘Restricted’ when creating a new API Key and can choose permissions for TaskRouter, Studio, Voice, SIP, Messages, Regulatory Compliance and Long Codes API endpoints.
  • API calls made with a Restricted API Key will only allow access to selected permissions. Calls made to resources that are not part of the selected permissions will be unauthorized.
  • Customers can manage Restricted API Keys solely through the Twilio Console only for the US region. Programmatic management of Restricted API Keys will be released shortly.

To learn more about Restricted API Keys, please check our docs.

TaskRouter Twilio Platform Flex