Nexmo APIs
39 APIs212 Endpoints8 Categories
Categories
API Catalog(4 of 39)
Audit API
The Vonage Audit API (audit) exposes a read-only stream of changes made to a Vonage account. It records application configuration changes, user secret creations and deletions, and account-level setting updates with timestamps, actor identifiers, and before/after diffs. The 2 endpoints — paginated list and single-event retrieval — cover the surface needed to drive compliance dashboards, SIEM integration, and incident triage. Vonage flags this API as beta on the /beta/audit base path.
2 endpointsAudit API
The Vonage Audit API (audit-api) exposes a read-only stream of changes made to a Vonage account. It records application configuration changes, user secret creations and deletions, and account-level setting updates with timestamps, actor identifiers, and before/after diffs. The 2 endpoints — paginated list and single-event retrieval — cover the surface needed to drive compliance dashboards, SIEM integration, and incident triage. Vonage flags this API as beta on the /beta/audit base path.
2 endpointsRedact API
The Nexmo Redact API gives privacy and compliance teams a controlled way to scrub the personally identifiable content of a specific transactional record from Vonage's logs. A single POST endpoint accepts a transaction id and product type and removes the message body, recipient number, and other PII from Vonage's retained records, helping organisations meet GDPR right-to-erasure and similar privacy obligations on demand.
1 endpointsRedact API
The Nexmo Redact API gives privacy and compliance teams a controlled way to scrub the personally identifiable content of a specific transactional record from Vonage's logs. A single POST endpoint accepts a transaction id and product type and removes the message body, recipient number, and other PII from Vonage's retained records, helping organisations meet GDPR right-to-erasure and similar privacy obligations on demand.
1 endpointsConnect Your Agent
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.