Dialpad

Connect Dialpad to collect communications platforms evidence with automated compliance tests, switched on per workspace.

Connect with an API token

1. In Dialpad:

   1. Sign in to Dialpad as a company admin and create an API key for your company. Dialpad's public developer pages fetched for this check do not give the menu path or button labels for creating the key.
   2. Paste the key into Safeguard; Dialpad expects it as Authorization: Bearer <api_key>.

   Where to find the other values:

   • Environment (optional): Production is https://dialpad.com; the sandbox is https://sandbox.dialpad.com. Choose the one where you created the key.

   Dialpad's public documentation does not cover every step.

   Source: developers.dialpad.com, developers.dialpad.com, checked 2026-10-07.

   The permissions Safeguard needs: company admin. Dialpad shows the full user list only to administrators, so this credential must belong to one. Safeguard only reads with it.

2. On Compliance › Connectors, open Dialpad, click Connect, choose API token and fill in:

   Field	What to enter
   API key	Required. Stored encrypted and never shown again.
   Environment (optional)	—

3. Click Connect with token.

Frameworks

Safeguard's automated tests read Dialpad and map to the controls below. When a test passes, the result is evidence toward each control it maps to, in every framework listed. It is evidence toward a control, not proof that the control is met on its own.

These tests are switched on per workspace by the Safeguard team.

Related

• Communications Platforms connectors
• Compliance connectors: how connecting works, card statuses and multiple accounts
• Connector setup reference: every connector in one table
• Frameworks and connectors: how connectors provide evidence for frameworks