Safeguard Docs
Compliance ConnectorsSetup by categoryCommunications Platforms

Plivo

Connect Plivo to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.

Record your Plivo connection as communications platforms evidence.

CategoryCommunications Platforms
Connect withAPI token
What a connection producesConnection record

Connect with an API token

  1. In Plivo:

    1. Sign in to the Plivo console (cx.plivo.com/home) and open API Keys (Console › API Keys).
    2. Copy the Auth Token; Plivo uses it as the password in HTTP Basic auth, with the Auth ID as the username.

    Where to find the other values:

    • Account / Org / Workspace (optional): Your Auth ID, shown with the Auth Token in the Plivo console (Console › API Keys).
    • Base URL (optional): Plivo's API base URL is https://api.plivo.com/v1/; account endpoints are under https://api.plivo.com/v1/Account/\{auth_id\}/.

    Plivo's public documentation does not cover every step.

    The fetched page says only 'Find your credentials on the Plivo console', with a troubleshooting reference to Console › API Keys; the exact page layout and labels were not quoted. Plivo documents no read-only credential; the Auth ID and Auth Token give full account API access. Subaccounts exist but their credential handling was not confirmed.

    Source: plivo.com, plivo.com, checked 2026-10-07.

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

    FieldWhat to enter
    API token / Personal access tokenRequired. Stored encrypted and never shown again.
    Base URL (optional)-
    Account / Org / Workspace (optional)-
  3. Click Connect with token.

Frameworks

Plivo publishes no API for what these tests check, so its evidence is an attestation: connect it to record the connection, then attest the result. An accepted attestation counts toward each control below.

FrameworkEvidenceControlsTests
SOC2AttestationCC6.2, CC6.31
ISO/IEC 27001AttestationA.5.181
HIPAA Security RuleAttestation164.308(a)(3)1
PCI DSSAttestation7.2.41
NIST CSF 2.0AttestationPR.AA-051

On this page