Nextiva
Connect Nextiva to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Record your Nextiva connection as communications platforms evidence. Automated collection is not available for this provider yet.
| Category | Communications Platforms |
| Connect with | API token |
| What a connection produces | Connection record |
Connect with an API token
-
In Nextiva:
- Nextiva's developer documentation describes no screen for creating a long-lived API key or personal access token. Its SDKs get a session token by signing in a Nextiva user: sdk.login(username, password) sends the credentials to Nextiva's Provider Service, which returns a token used on all later requests.
- Use a dedicated Nextiva user for this, and ask your Nextiva account team whether a non-interactive API credential is available for your plan.
Where to find the other values:
- API token / Personal access token: The token field in the login response from the Nextiva SDK (sdk.login). Nextiva says this token is needed on all subsequent requests and the SDK adds it to the HTTP header automatically.
- Base URL (optional): Nextiva says requests are routed through the nextiva.io domain (currently thrio.io), with regional domains being set up for the US, Canada, Europe and India. The login response tells the client where to send later requests.
- Account / Org / Workspace (optional): Not documented publicly; leave blank.
Nextiva issues this credential through its API or its support team, not through its admin screens.
Applies to Nextiva's contact-center developer platform (developer.nextiva.com, the NEXT/Thrio stack). The SDK docs only describe username-and-password login that returns a session token. They describe no admin page for API keys, no scopes and no read-only role. Site-filtered searches of nextiva.com, help.nextiva.com and developer.nextiva.com found no customer-facing API-key article; the Nextiva Contact Center 'Private Key' article covers SFTP file-server keys, not API access. Nextiva's other products (NextivaONE, legacy voice) were not covered.
Source: developer.nextiva.com, developer.nextiva.com, checked 2026-10-07.
-
On Compliance › Connectors, open Nextiva, click Connect, choose API token and fill in:
Field What to enter API token / Personal access token Required. Stored encrypted and never shown again. Base URL (optional) — Account / Org / Workspace (optional) — -
Click Connect with token.
Frameworks
Nextiva 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.
| Framework | Evidence | Controls | Tests |
|---|---|---|---|
| SOC2 | Attestation | CC6.2, CC6.3 | 1 |
| ISO/IEC 27001 | Attestation | A.5.18 | 1 |
| HIPAA Security Rule | Attestation | 164.308(a)(3) | 1 |
| PCI DSS | Attestation | 7.2.4 | 1 |
| NIST CSF 2.0 | Attestation | PR.AA-05 | 1 |
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