Redact API

Name: Redact API API
Brand: Redact API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentSecurityCompliancebasic1 EndpointsREST

For Agents

Redact the personally identifiable content of a specific Vonage transactional record (SMS, voice call, verification, message) from Vonage's logs.

Quickstart

Get started with Redact API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"redact a vonage sms transaction"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Redact API API.

Redact a specific SMS transaction from Vonage's retained message logs

Redact a specific voice call record from Vonage's retained call logs

Redact a specific verification request from Vonage's retained Verify logs

Redact a specific Messages API record across SMS, MMS, WhatsApp, and Viber

GET STARTED

Start building with Redact API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Redact API, keeping it validated and agent-ready.

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.

Use Cases

Patterns agents use Redact API API for, with concrete tasks.

★ GDPR right-to-erasure on transactional logs

When a customer submits a right-to-erasure request, the compliance team identifies the affected SMS, voice, or verification transactions in their own systems, then calls POST /transaction with each id and product to scrub PII from Vonage's retained logs. Closing the loop on Vonage's side means the organisation can attest that no copy of the message body or number remains in any system under its control.

POST /transaction with id=MESSAGE_ID and product=sms for each message tied to the data subject

Voice call PII scrubbing

Customer support and trust teams that record voice calls or store recipient numbers in Vonage's retained logs can call the Redact API after a complaint or breach to remove the PII associated with a specific call. This is critical when a recording has been flagged as containing sensitive information that should not have been captured.

POST /transaction with id=CALL_UUID and product=voice for the affected call

Verify and Messages API cleanup

Organisations using Vonage's Verify or Messages APIs can redact a specific verification or rich-message record by transaction id. Because the endpoint requires the original transaction id, redactions are scoped and auditable — you cannot accidentally erase records you do not specifically reference.

POST /transaction with id=REQUEST_ID, product=verify, and type=verify-request to scrub the verification record

AI agent compliance automation via Jentic

An AI agent that handles privacy ticket workflows can call the Redact API through Jentic each time a right-to-erasure request is approved. The agent reads transaction ids from its own ticket store, searches Jentic for the redact operation, and executes one POST /transaction per record, all with credentials supplied by the Jentic vault.

Search Jentic for 'redact a vonage transaction', load POST /transaction, and execute with id and product for each ticket-linked record

Key Endpoints

1 endpoints — 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.

METHOD

PATH

DESCRIPTION

POST

/transaction

Redact a specific SMS, voice, verify, or messages record by id

POST

/transaction

Redact a specific SMS, voice, verify, or messages record by id

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Nexmo apiKey and apiSecret are stored encrypted in the Jentic vault and encoded as HTTP Basic on the agent's behalf. Raw credentials never enter the agent's context.

Intent-based discovery

Agents search Jentic by intent (e.g. 'redact a vonage transaction') and Jentic returns the POST /transaction operation with its input schema.

Time to first call

Direct integration: half a day to wire up Basic auth, error handling, and audit logging. Through Jentic: under 15 minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Twilio Messaging

Twilio offers per-record deletion on its messaging resources as the closest equivalent compliance hook.

Choose Twilio's record deletion endpoints when the underlying traffic ran on Twilio rather than Vonage.

Complementary

Nexmo SMS API

SMS messages sent via the SMS API are the records the Redact API later scrubs.

Send via the SMS API; redact via the Redact API once a deletion request is approved.

Complementary

Nexmo Verify API

Verify transactions are one of the four product types the Redact API can scrub.

Trigger a Redact call against a Verify request_id when honouring an erasure request tied to 2FA.

FAQs

Specific to using Redact API API through Jentic.

What authentication does the Nexmo Redact API use?

The Redact API uses HTTP Basic authentication with your Nexmo apiKey as the username and apiSecret as the password — different from most other Vonage APIs that take credentials as query parameters. Through Jentic those credentials are encoded automatically and the agent only ever sees a scoped token.

Can I redact more than one record in a single request?

No — POST /transaction redacts exactly one record per call, identified by the id and product fields. For bulk erasure pipelines, loop through the transaction ids in your ticketing system and post one redaction per record. The request is intentionally narrow to keep the audit trail tight.

What are the rate limits for the Redact API?

The OpenAPI spec does not encode a numeric rate limit. The endpoint is intended for compliance workflows, not high-throughput automation, so a sensible client serialises requests and reconciles failures rather than running unbounded concurrency.

How do I redact a transaction through Jentic?

Run pip install jentic, search for 'redact a vonage transaction', and Jentic returns POST /transaction. Execute with id=TRANSACTION_ID and product (sms, voice, verify, or messages) and Jentic returns Vonage's confirmation.

What products can the Redact API target?

The product field accepts sms, voice, verify, and messages, covering every PII-bearing log Vonage retains for transactional traffic. The optional type field further narrows verify requests into verify-request, verify-check, and similar subtypes.

Is the Nexmo Redact API free to call?

Vonage does not charge per redaction request — the API exists to support compliance obligations. The cost of the original SMS, voice, or verification transaction is unaffected by a later redaction.