Restricted API keys are available as a public beta release. Twilio might add or change features before declaring Restricted API keys Generally Available. Beta products aren't covered by a Twilio SLA.
Learn more about beta product support.
Use Restricted API keys for fine-grained control over access to Twilio API resources. You can create and manage Restricted API keys using the REST API Key resource v1 or the Twilio Console.
Restricted API keys allow you to grant API access to many Twilio API endpoints, including:
For example, if your Programmable Voice application's testing suite makes test Voice calls, you can create a Restricted API key that permits only sending POST requests to create Call Resources.
Or you can create Restricted API keys that provide your engineering team with access to every Voice endpoint except the Call Recording Resource endpoints.
You can't create Access Tokens for Twilio's client-side SDKs with Restricted API keys.
Twilio uses the Restricted key's SID and secret as your credentials when sending API requests.
Read the Requests to Twilio page to learn more.
Restricted API keys have a limit of 100 permissions that can be associated with each key.
Restricted API keys allow you grant permissions for keys to access specific API endpoints.
Each permission maps to one or more endpoints/actions for each API Resource.
Click on one of the product areas below to download a PDF of the permissions/endpoint actions.
Twilio Restricted API keys Permissions - Messaging Permissions
Twilio Restricted API keys Permissions - Phone Numbers Permissions
Twilio Restricted API keys Permissions - Studio Permissions
Twilio Restricted API keys Permissions - TaskRouter Permissions
Twilio Restricted API keys Permissions - Voice Permissions
Twilio Restricted API keys Permissions - Lookup Permissions
Twilio Restricted API keys Permissions - API keys Permissions
Twilio Restricted API keys Permissions - Monitor Permissions