Twilio
Collect account configuration, verified sender numbers, and usage-record evidence as read-only compliance signal for orgs using Twilio as an SMS/voice alerting channel -- analogous to the Discord/Opsgenie templates. Not intended for general consumer messaging content or customer-communication data.
What this connector audits
Checks this connector runs once it's connected. This is the full list; we don't claim coverage beyond what's implemented.
- Read-only API inventory endpoint checks
- Evidence assets generated through the generic HTTP connector
Endpoints this template queries
The exact Twilio API endpoints called once connected. All read-only GET requests unless noted.
- GET/Accounts/<account-sid>.json
- GET/Accounts/<account-sid>/IncomingPhoneNumbers.json
- GET/Accounts/<account-sid>/Usage/Records.json
What we need
Field labels only. We never show secret values here. Credentials are encrypted at rest and used only to run the checks above.
- Base URL(prefilled: https://api.twilio.com/2010-04-01)
- Endpoints (JSON)(prefilled: [ { "id": "account", "name": "Account info", "path": "/Accounts/<account-sid>.json" }, { "id": "phone-numbers", "name": "Verified/incoming phone numbers", "path": "/Accounts/<account-sid>/IncomingPhoneNumbers.json" }, { "id": "usage-records", "name": "Usage records", "path": "/Accounts/<account-sid>/Usage/Records.json" } ])
- Auth header name(prefilled: Authorization)
- Auth header value(secret credential)
Required
Optional
Which frameworks this evidence supports
Twilio evidence feeds into controls for any framework you run that requires this check type; the same synced evidence can satisfy more than one framework's requirements instead of being collected per audit.
Don't see your system?
Tell us what you use and what it needs to prove. We'll follow up about adding a connector.
Wire in Twilio evidence
Get a guided demo, or start by scanning any domain for free.