Sendgrid Twilio SendGrid Mail Settings API
Browse all Sendgrid APIsCommunicationsEmail Deliverybearer13 EndpointsREST
For Agents
Programmatically retrieve all mail settings, retrieve address whitelist mail settings. Covers 13 operations with bearer authentication.
Use for: I need to all mail settings, I want to address whitelist mail settings, Search for address whitelist mail settings, Find all bounce purge mail settings
Not supported: Does not handle payments, crm, or developer tools - use for communications only.
The Twilio SendGrid Mail Settings API allows you to retrieve and configure the various Mail Settings available. Mail Settings instruct SendGrid to apply specific settings to every email that you send over [SendGrid’s Web API](https://docs.sendgrid.com/api-reference/mail-send/v3-mail-send) or [SMTP relay](https://sendgrid.com/docs/for-developers/sending-email/building-an-x-smtpapi-header/). These s. The API exposes 13 endpoints secured with bearer authentication.
Install Jentic One Beta
Connect the Twilio SendGrid Mail Settings API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Twilio SendGrid Mail Settings 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fsendgrid.com%2Ftwilio-sendgrid-mail-settings-api" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fsendgrid.com%2Ftwilio-sendgrid-mail-settings-api" | 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 Mail Settings API.
Retrieve all mail settings
Update address whitelist mail settings
Integrate Twilio SendGrid Mail Settings API into automated workflows
Query and filter Twilio SendGrid Mail Settings API records by parameters
Monitor Twilio SendGrid Mail Settings API operational status and events
Use Cases
Patterns agents use Twilio SendGrid Mail Settings API for, with concrete tasks.
★ Communications Operations
Use the Twilio SendGrid Mail Settings API to perform communications operations programmatically. The API provides 13 endpoints covering core functionality including retrieve all mail settings, retrieve address whitelist mail settings, update address whitelist mail settings.
Call GET /v3/mail_settings to retrieve all mail settings
Automated Mail Settings Management
Automate mail settings operations by combining multiple Twilio SendGrid Mail Settings API endpoints. Agents can retrieve address whitelist mail settings and then update address whitelist mail settings in a single workflow.
Call GET /v3/mail_settings/address_whitelist to retrieve address whitelist mail settings, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Twilio SendGrid Mail Settings 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 'retrieve all mail settings', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
13 endpoints — the twilio sendgrid mail settings api allows you to retrieve and configure the various mail settings available.
METHOD
PATH
DESCRIPTION
GET
/v3/mail_settings
Retrieve all mail settings
GET
/v3/mail_settings/address_whitelist
Retrieve address whitelist mail settings
PATCH
/v3/mail_settings/address_whitelist
Update address whitelist mail settings
GET
/v3/mail_settings/bounce_purge
Retrieve Bounce Purge Mail Settings
PATCH
/v3/mail_settings/bounce_purge
Update Bounce Purge Mail Settings
GET
/v3/mail_settings/footer
Retrieve footer mail settings
PATCH
/v3/mail_settings/footer
Update footer mail settings
GET
/v3/mail_settings/forward_bounce
Retrieve forward bounce mail settings
GET
/v3/mail_settings
Retrieve all mail settings
GET
/v3/mail_settings/address_whitelist
Retrieve address whitelist mail settings
PATCH
/v3/mail_settings/address_whitelist
Update address whitelist mail settings
GET
/v3/mail_settings/bounce_purge
Retrieve Bounce Purge Mail Settings
PATCH
/v3/mail_settings/bounce_purge
Update Bounce Purge Mail Settings
GET
/v3/mail_settings/footer
Retrieve footer mail settings
PATCH
/v3/mail_settings/footer
Update footer mail settings
GET
/v3/mail_settings/forward_bounce
Retrieve forward bounce mail settings
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Twilio SendGrid Mail Settings 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 Mail Settings API from the API Directory, store the API key once, and your agent calls it.
Permission scoping
This API exposes fixed settings such as address whitelist, bounce purge, and footer, so limit the agent to the operations it needs, such as reading mail settings with GET /v3/mail_settings. You choose the operations it may call, so an update like PATCH /v3/mail_settings/footer is not included unless you add it.
Credential isolation
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.
Intent-based discovery
Agents search Jentic by intent such as 'retrieve all mail settings' or 'update the email footer', and Jentic returns the matching Twilio SendGrid Mail Settings API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Twilio SendGrid Mail Settings API through Jentic.
What authentication does the Twilio SendGrid Mail Settings API use?
The Twilio SendGrid Mail Settings 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 retrieve all mail settings with the Twilio SendGrid Mail Settings API?
Yes. Use the GET /v3/mail_settings endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Twilio SendGrid Mail Settings 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 retrieve all mail settings through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'retrieve all mail settings'. Jentic returns the matching Twilio SendGrid Mail Settings API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Twilio SendGrid Mail Settings API have?
The Twilio SendGrid Mail Settings API exposes 13 endpoints covering mail settings operations.
Can I limit what my agent is allowed to do with the Twilio SendGrid Mail Settings API?
Yes. Jentic One runs self-hosted, so you decide which of the Mail Settings operations your agent may call and which credentials it may use. You can allow read-only access with GET /v3/mail_settings while excluding write operations such as PATCH /v3/mail_settings/footer or PATCH /v3/mail_settings/address_whitelist, so the agent only touches the settings you approve. An operation is available to the agent only when you have explicitly added it to its scope.
GET STARTED