canonical: https://jentic.com/apis/sendgrid.com/twilio-sendgrid-recipients-data-erasure-api

# Sendgrid Twilio SendGrid Recipients' Data Erasure API

The Recipients' Data Erasure API allows Twilio SendGrid customers to delete their own customers' personal data from the Twilio SendGrid Platform. The use of this API facilitates the self-service removal of email personal data from the Twilio SendGrid platform and will enable customers to comply with various obligatory data privacy regulations. The API exposes 1 endpoints secured with bearer authentication.

## For AI agents

Programmatically erase recipients' email data. Covers 1 operations with bearer authentication.

## Scope

Does not handle payments, crm, or developer tools - use for communications only.

## Capabilities

- Erase recipients' email data
- Manage communications data programmatically
- Integrate Twilio SendGrid Recipients' Data Erasure API into automated workflows
- Query and filter Twilio SendGrid Recipients' Data Erasure API records by parameters
- Monitor Twilio SendGrid Recipients' Data Erasure API operational status and events

## Use cases

### Communications Operations

Use the Twilio SendGrid Recipients' Data Erasure API to perform communications operations programmatically. The API provides 1 endpoints covering core functionality including erase recipients' email data.

Example prompt: Call POST /v3/recipients/erasejob to erase recipients' email data

### Data Retrieval and Monitoring

Query Twilio SendGrid Recipients' Data Erasure API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary Twilio SendGrid Recipients' Data Erasure API endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call Twilio SendGrid Recipients' Data Erasure API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.

Example prompt: Search Jentic for 'erase recipients' email data', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /v3/recipients/erasejob | Erase recipients' email data |

## Key resources

- **Point Delete System** — Twilio SendGrid Recipients' Data Erasure API

## Why Jentic

- **Setup:** Wiring the Twilio SendGrid Recipients' Data Erasure API by hand means learning its bearer API key auth, picking the right global api.sendgrid.com or EU api.eu.sendgrid.com host, and handling retries yourself. Through Jentic you install once, import the Recipients' Data Erasure API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** This API exposes a single erase-job operation, so limit the agent to the operation it needs, creating an erase job with POST /v3/recipients/erasejob. You choose whether the agent has that operation at all, so it cannot act beyond submitting erasure requests.
- **Credential handling:** Your Twilio SendGrid API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'erase recipient email data', and Jentic returns the matching Twilio SendGrid Recipients' Data Erasure API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Twilio** — Alternative communications API
- **Pusher** — Alternative communications API

## FAQ

### What authentication does the Twilio SendGrid Recipients' Data Erasure API use?

The Twilio SendGrid Recipients' Data Erasure API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I erase recipients' email data with the Twilio SendGrid Recipients' Data Erasure API?

Yes. Use the POST /v3/recipients/erasejob endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Twilio SendGrid Recipients' Data Erasure API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I erase recipients' email data through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'erase recipients' email data'. Jentic returns the matching Twilio SendGrid Recipients' Data Erasure API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Twilio SendGrid Recipients' Data Erasure API have?

The Twilio SendGrid Recipients' Data Erasure API exposes 1 endpoints covering point delete system operations.

### Can I limit what my agent is allowed to do with the Twilio SendGrid Recipients' Data Erasure API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use. This API exposes a single operation, POST /v3/recipients/erasejob, which creates an erasure job, so you can grant the agent just that call and nothing else. With no other operation available, the agent cannot act beyond submitting recipient data erasure requests.