canonical: https://jentic.com/apis/sendgrid.com/twilio-sendgrid-domain-authentication-api

# Sendgrid Twilio SendGrid Domain Authentication API

The Twilio SendGrid Domain Authentication API allows you to manage your authenticated domains and their settings. Domain Authentication is a required step when setting up your Twilio SendGrid account because it's essential to ensuring the deliverability of your email. Domain Authentication signals trustworthiness to email inbox providers and your recipients by approving SendGrid to send email on b. The API exposes 16 endpoints secured with bearer authentication.

## For AI agents

Programmatically email dns records to a co-worker, authenticate a domain. Covers 16 operations with bearer authentication.

## Scope

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

## Capabilities

- Email DNS records to a co-worker
- Authenticate a domain
- List all authenticated domains
- Retrieve an authenticated domain
- Update an authenticated domain
- Delete an authenticated domain.
- Associate an authenticated domain with a given user.

## Use cases

### Communications Operations

Use the Twilio SendGrid Domain Authentication API to perform communications operations programmatically. The API provides 16 endpoints covering core functionality including email dns records to a co-worker, authenticate a domain, list all authenticated domains.

Example prompt: Call POST /v3/whitelabel/dns/email to email dns records to a co-worker

### Automated Domain Authentication Management

Automate domain authentication operations by combining multiple Twilio SendGrid Domain Authentication API endpoints. Agents can authenticate a domain and then list all authenticated domains in a single workflow.

Example prompt: Call POST /v3/whitelabel/domains to authenticate a domain, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Twilio SendGrid Domain Authentication 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 'email dns records to a co-worker', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /v3/whitelabel/dns/email | Email DNS records to a co-worker |
| POST | /v3/whitelabel/domains | Authenticate a domain |
| GET | /v3/whitelabel/domains | List all authenticated domains |
| GET | /v3/whitelabel/domains/{domain_id} | Retrieve an authenticated domain |
| PATCH | /v3/whitelabel/domains/{domain_id} | Update an authenticated domain |
| DELETE | /v3/whitelabel/domains/{domain_id} | Delete an authenticated domain. |
| POST | /v3/whitelabel/domains/{domain_id}/subuser | Associate an authenticated domain with a given user. |
| DELETE | /v3/whitelabel/domains/{domain_id}/subuser | Disassociate an authenticated domain from a given user for users with up to five |

## Key resources

- **Domain Authentication** — Twilio SendGrid Domain Authentication API

## Why Jentic

- **Setup:** Wiring the Twilio SendGrid Domain Authentication API by hand means learning its bearer auth where the API key is the token, choosing the right US or EU host (api.sendgrid.com or api.eu.sendgrid.com), and managing DNS whitelabel records yourself. Through Jentic you install once, import the Twilio SendGrid Domain Authentication API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** This API puts the domain id in the URL path (/v3/whitelabel/domains/{domain_id}/...), so a rule can pin your agent to one domain: it can read, update, and attach a subuser to that domain. You choose the operations it may call, so domain deletion is not included unless you add it.
- **Credential handling:** Your Twilio SendGrid Domain Authentication 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 'authenticate a sending domain' or 'list whitelabel domains', and Jentic returns the matching Twilio SendGrid Domain Authentication 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 Domain Authentication API use?

The Twilio SendGrid Domain Authentication 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 email dns records to a co-worker with the Twilio SendGrid Domain Authentication API?

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

### What are the rate limits for the Twilio SendGrid Domain Authentication 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 email dns records to a co-worker through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'email dns records to a co-worker'. Jentic returns the matching Twilio SendGrid Domain Authentication API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Twilio SendGrid Domain Authentication API have?

The Twilio SendGrid Domain Authentication API exposes 16 endpoints covering domain authentication operations.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which operations and credentials the agent may use. Because this API carries the domain id in the URL path (/v3/whitelabel/domains/{domain_id}/...), you can pin the agent to a single authenticated domain and allow only the calls it needs, such as retrieving that domain, updating it, and associating a subuser. You choose the operations it may call, so the DELETE /v3/whitelabel/domains/{domain_id} endpoint stays off the list unless you explicitly add it.