Restricted API Keys now support granular Conversations permissions
Restricted API Keys now support resource-level permissions for Conversations (classic), enabling fine-grained control over operations like listing conversations, sending messages, and managing participants. This reduces security risk by limiting key scope to only necessary operations.
Restricted API Keys now support granular, resource-level permissions for Conversations (classic), covering actions like listing conversations, sending messages, managing participants, and configuring webhooks. This lets you scope a key to only the operations your integration needs — for example, granting read access to conversations while blocking any ability to delete users or roles — reducing the blast radius if a key is ever compromised. Configure these permissions when creating a Restricted API Key in the Twilio Console.
Source: original entry ↗