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 ↗
More from Twilio
Follow Twilio to get its new changes in your feed and email digest.
Voice Integrity now supports all three major US networks
Voice Integrity, part of Twilio's Voice Trust offering, now supports all three major US carrier networks. Businesses can register their details and outbound phone numbers directly with carriers to help identify legitimate traffic and reduce spam blocking.
Unified Login for SendGrid Marketplace Customers
SendGrid marketplace customers can now create individual Twilio logins for each user, enabling granular permission management instead of shared admin access. This rollout applies to all marketplace integrations including Azure, Google Cloud, Heroku, and AWS.
Webhook Configuration API is now Generally Available
The Webhook Configuration API enables customers to configure authentication and delivery settings for outbound webhooks on a per-URL basis through Webhook Settings and Webhook Rules resources.