Sendgrid Twilio SendGrid Domain Authentication API
Browse all Sendgrid APIs★ Only Publicly Available OpenAPI DocumentCommunicationsEmail Deliverybearer16 EndpointsREST
For Agents
Programmatically email dns records to a co-worker, authenticate a domain. Covers 16 operations with bearer authentication.
Use for: I need to email dns records to a co-worker, I want to authenticate a domain, Search for all authenticated domains, Find all an authenticated domain
Not supported: Does not handle payments, crm, or developer tools — use for communications only.
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.
Install Jentic One Beta
Connect the Twilio SendGrid Domain Authentication API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Twilio SendGrid Domain Authentication API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
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.
Capabilities
What an agent can do with Twilio SendGrid Domain Authentication API.
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
Patterns agents use Twilio SendGrid Domain Authentication API for, with concrete tasks.
★ 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.
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.
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.
Search Jentic for 'email dns records to a co-worker', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
16 endpoints — the twilio sendgrid domain authentication api allows you to manage your authenticated domains and their settings.
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
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
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Twilio SendGrid Domain Authentication API bearer credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'email dns records to a co-worker') and Jentic returns the matching Twilio SendGrid Domain Authentication API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Twilio SendGrid Domain Authentication API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Twilio SendGrid Domain Authentication API through Jentic.
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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.
GET STARTED