canonical: https://jentic.com/apis/sendgrid.com/twilio-sendgrid-reverse-dns-api

# Sendgrid Twilio SendGrid Reverse DNS API

The Twilio SendGrid Reverse DNS API (formerly IP Whitelabel) allows you to configure reverse DNS settings for your account. Mailbox providers verify the sender of your emails by performing a reverse DNS lookup. When setting up Reverse DNS, Twilio SendGrid will provide an A Record (address record) for you to add to the DNS records of your sending domain. The A record maps your sending domain to a d. The API exposes 5 endpoints secured with bearer authentication.

## For AI agents

Programmatically set up reverse dns, retrieve all reverse dns records. Covers 5 operations with bearer authentication.

## Scope

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

## Capabilities

- Set up reverse DNS
- Retrieve all reverse DNS records
- Delete a reverse DNS record
- Validate a reverse DNS record
- Monitor Twilio SendGrid Reverse DNS API operational status and events

## Use cases

### Communications Operations

Use the Twilio SendGrid Reverse DNS API to perform communications operations programmatically. The API provides 5 endpoints covering core functionality including set up reverse dns, retrieve all reverse dns records, retrieve a reverse dns record.

Example prompt: Call POST /v3/whitelabel/ips to set up reverse dns

### Automated Reverse DNS Management

Automate reverse dns operations by combining multiple Twilio SendGrid Reverse DNS API endpoints. Agents can retrieve all reverse dns records and then retrieve a reverse dns record in a single workflow.

Example prompt: Call GET /v3/whitelabel/ips to retrieve all reverse dns records, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Twilio SendGrid Reverse DNS 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 'set up reverse dns', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /v3/whitelabel/ips | Set up reverse DNS |
| GET | /v3/whitelabel/ips | Retrieve all reverse DNS records |
| GET | /v3/whitelabel/ips/{id} | Retrieve a reverse DNS record |
| DELETE | /v3/whitelabel/ips/{id} | Delete a reverse DNS record |
| POST | /v3/whitelabel/ips/{id}/validate | Validate a reverse DNS record |

## Key resources

- **Reverse DNS** — Twilio SendGrid Reverse DNS API

## Why Jentic

- **Setup:** Wiring the Twilio SendGrid Reverse DNS 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 paging and retries yourself. Through Jentic you install once, import the Reverse DNS API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** This API puts the reverse DNS id in the URL path (/v3/whitelabel/ips/{id}), so a rule can pin your agent to one reverse DNS record: it can read and validate that record and nothing else. You choose the operations it may call, so deleting a record with DELETE /v3/whitelabel/ips/{id} is not included unless you add it.
- **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 'set up reverse DNS' or 'validate a reverse DNS record', and Jentic returns the matching Twilio SendGrid Reverse DNS 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 Reverse DNS API use?

The Twilio SendGrid Reverse DNS 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 set up reverse dns with the Twilio SendGrid Reverse DNS API?

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

### What are the rate limits for the Twilio SendGrid Reverse DNS 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 set up reverse dns through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'set up reverse dns'. Jentic returns the matching Twilio SendGrid Reverse DNS API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Twilio SendGrid Reverse DNS API have?

The Twilio SendGrid Reverse DNS API exposes 5 endpoints covering reverse dns operations.

### Can I limit what my agent is allowed to do with the Twilio SendGrid Reverse DNS API?

Yes. Because you run Jentic One yourself, your own rules decide which Twilio SendGrid Reverse DNS API operations and credentials the agent may use. Since the record id sits in the URL path (/v3/whitelabel/ips/{id}), you can pin the agent to a single reverse DNS record and let it only read and validate that record, and nothing else. Destructive calls like DELETE /v3/whitelabel/ips/{id} stay off limits unless you explicitly grant them.