Skip to main content
DSALTA connects to Twilio using read-only API access to collect compliance evidence automatically. Data feeds into your Data Library modules.
Read-only access. DSALTA never modifies, creates, or deletes resources in your Twilio account.
What you’ll see. Twilio’s API does not expose a per-user member list from an Account SID and Auth Token, so DSALTA’s Access page lists your Twilio account and any subaccounts (identified by name / Account SID) rather than individual people. Twilio accounts also have no email address, so User access to Critical System should be valid matches these rows on the account name. DSALTA joins Access rows to People by email; with no email it compares the account’s friendly name, case-insensitively, against each person’s Username on the People page and against the part before the @ in their email address. A row clears when either of those matches, and is reported as invalid otherwise. Username is entered in the Add Person form, so for people already on the People page the email match is the practical route. Treat the Access list as an inventory of Twilio accounts and confirm each owner manually.
DSALTA collects this integration’s data when you connect it — you can refresh it at any time with Sync from integrations on the Integrations page. The compliance checks below re-run once a day at 02:00 America/New_York.

​
What DSALTA reads

DSALTA reads your Twilio accounts — the connected account plus any subaccounts, with their friendly names, status and creation dates, which appears on your Access page. An Account SID and Auth Token cannot list console users, so these rows are accounts rather than people: they carry no email address, and each one is labelled Owner or Subaccount rather than a real role.It calls these Twilio endpoints:
  • /2010-04-01/Accounts.json
Every request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your Twilio environment.

​
Troubleshooting

There is no Reconnect button. Open Integrations → Connected, click Manage on the Twilio card, and check the Status tab — it shows either Connected and working properly or Connection issues detected. To restore a broken connection you must Disconnect and connect again, which permanently deletes the data and tests collected from Twilio. This can happen if the Auth Token was reset or rotated in the Twilio Console.
Confirm the Account SID and Auth Token are current (the token may have been reset in the Twilio Console), then click Sync from integrations on the Integrations page (Connected tab) — it refreshes every connected integration at once.