SUPPORT.TWILIO.COM END OF LIFE NOTICE: This site, support.twilio.com, is scheduled to go End of Life on February 27, 2024. All Twilio Support content has been migrated to help.twilio.com, where you can continue to find helpful Support articles, API docs, and Twilio blog content, and escalate your issues to our Support team. We encourage you to update your bookmarks and begin using the new site today for all your Twilio Support needs.

Why do Multiple Studio API Keys Appear on Your Account?

Question

Why are there two Studio API keys automatically generated, and recreated in my Twilio account?

 

Product

Twilio Studio

 

Answer

Twilio Studio automatically generates an API key named Studio API Key to authenticate and execute REST API requests on behalf of your account during Flow Executions.

If you observe two active Studio API Key records on your account, this is expected behavior related to the new Studio engine. The updated engine architecture requires its own dedicated API key to execute workflows and widgets independently from the original workflow engine.

Key details regarding these API keys:

  • Automatic Provisioning: When a flow executes under the new Studio engine, Studio automatically creates a second API key if one does not already exist.

  • Deletion and Regeneration: If either (or both) Studio API key is removed, Studio will automatically recreate it during the next flow execution to prevent service disruption and ensure your flows run uninterrupted only if the processing engine does not have one available.

  • Credential Management: Studio-generated keys are managed automatically by Twilio Studio, meaning you do not need to manually configure them.

Leaving both Studio API Key entries active on your account is expected and required for your Studio flows to execute properly.

 

Additional Information

Studio Generated API Keys: https://www.twilio.com/docs/studio/studio-generated-api-keys

New Studio Engine: https://www.twilio.com/docs/studio/new-studio-engine

Have more questions? Submit a request
We can’t wait to see what you build.
Powered by Zendesk