44 APIs across 10 product groups. All share one credential.
What agents get from Jentic-routed access to this vendor.
Setup
Once Jentic One is installed, you or your agent can find and add any Twilio SendGrid API from the Jentic directory to your workspace, so sending, marketing, deliverability, and reporting endpoints are all reachable through one consistent interface.
Permission scoping
Your own rules in your Jentic One instance decide which SendGrid operations an agent may call, so you can allow read-only stats or contact lookups while withholding destructive actions like erasing recipient data or deleting API keys.
Credential isolation
Your single SendGrid API key is stored encrypted in your own self-hosted Jentic One instance and injected as the bearer token at call time, so the agent triggers SendGrid operations without reading the raw key.
Specific to using Twilio SendGrid APIs through Jentic.
What can an agent do across the Twilio SendGrid APIs?
An agent can send transactional and marketing email over HTTP, build and target campaigns with contacts, lists, and segments, configure deliverability infrastructure such as domain authentication, link branding, and dedicated IP warmup, and pull delivery and engagement statistics. It can also administer the account by managing API keys, teammates, subusers, single sign-on, and suppressions.
Do all these APIs share one credential?
Yes. Every Twilio SendGrid API authenticates with a single SendGrid API key sent as a bearer token, so one credential works across sending, marketing, deliverability, analytics, and administration. What each key can actually do is bounded by the scopes assigned to it.
What is the difference between the Mail API and Marketing Campaigns Single Sends?
The Mail API sends individual transactional or marketing messages over HTTP, with support for templates, categories, and batch scheduling. Single Sends are one-time, non-automated campaign messages delivered to a list or segment of your marketing audience, and they carry their own campaign statistics.
Why are there both current and legacy Marketing Campaigns APIs?
BOOK A DEMO
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.
For Agents
An agent can send transactional and marketing email, manage contacts, lists, and segments, schedule and cancel batch sends, and configure deliverability settings such as domain authentication, link branding, and dedicated IP warmup. It can also pull delivery and engagement statistics, manage suppressions and tracking, and administer API keys, teammates, subusers, and single sign-on across the account.
Twilio SendGrid splits email into focused APIs for sending, marketing campaigns, deliverability infrastructure, and reporting, so an agent can pick exactly the surface it needs rather than one broad interface. Both current Marketing Campaigns and legacy Marketing Campaigns endpoints are catalogued, alongside deliverability controls like domain authentication, reverse DNS, and engagement quality scoring.
Use for: Sending transactional and marketing email at scale, managing contacts, lists, and segments, configuring deliverability infrastructure, and reporting on email engagement through Twilio SendGrid
Not supported: SMS messaging, voice calling, push notifications, inbound email hosting, payment processing
Credentials: All Twilio SendGrid APIs authenticate with a single SendGrid API key sent as a bearer token, so one credential covers the entire portfolio, subject to the scopes assigned to that key.
All 44 Twilio SendGrid OpenAPI specs are vendor-official and indexed by Jentic, kept validated and agent-ready.
Twilio SendGrid is an email delivery platform whose APIs cover transactional and marketing email sending, contact and list management, deliverability infrastructure, analytics, and account administration. The portfolio lets an agent send mail at scale over HTTP, build and target marketing campaigns, authenticate sending domains and IP addresses, track opens and clicks, manage suppressions, and administer users and API keys, all against a single SendGrid account.
| I want to... | Use | Why |
|---|---|---|
| Send a one-off transactional or marketing email over HTTP | Twilio SendGrid Mail API | Core send endpoint with templates, categories, batch scheduling, and open/click tracking |
| Create and send a one-time campaign to a list or segment | Twilio SendGrid Marketing Campaigns Single Sends API | Single Sends are non-automated one-time campaign messages to an audience |
| Send a test marketing email before a real campaign | Twilio SendGrid Marketing Campaigns Send Test Email API | Sends a marketing email to up to 10 addresses for layout and content checks |
| Manage marketing contacts in current Marketing Campaigns | Twilio SendGrid Marketing Campaigns Contacts API | Current Contacts API for importing, updating, and deleting marketing contacts |
| Manage marketing contacts on the older stack | Twilio SendGrid Legacy Marketing Campaigns Contacts API | Legacy Marketing Campaigns contacts and custom fields for accounts still on that version |
| Define dynamic audience segments | Twilio SendGrid Marketing Campaigns Segments 2.0 API | Segments V2 update dynamically as contact data changes; the older mc-segments is read-only after deprecation |
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Twilio SendGrid APIs, 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.
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" | shStep 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" | 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.
Once connected, ask your agent something like: “send email and manage marketing campaigns with Twilio SendGrid”.
Each workflow spans multiple Twilio SendGrid APIs. Jentic routes each operation to the right API automatically.
Send a tracked transactional email with a saved template
An agent creates a reusable transactional template, then sends mail referencing that template ID and reads back open and click statistics to measure engagement.
Create a transactional template, send an email that references its template ID, then retrieve open and click stats for the send.
Twilio SendGrid Templates API + Twilio SendGrid Mail API + Twilio SendGrid Statistics API
Warm a dedicated IP on an authenticated domain
An agent authenticates a sending domain, adds a dedicated IP address, and starts a gradual warmup schedule to build sender reputation before high-volume sending.
Authenticate a domain, add a dedicated IP, then start warming that IP on the recommended schedule.
Twilio SendGrid Domain Authentication API + Twilio SendGrid IP Address Management API + Twilio SendGrid IP Warmup API
Build and launch a targeted marketing campaign
An agent adds contacts, groups them into a dynamic segment, and creates a Single Send targeting that segment for a one-time campaign.
Add or update contacts, create a dynamic segment from their attributes, then create a Single Send addressed to that segment.
Twilio SendGrid Marketing Campaigns Contacts API + Twilio SendGrid Marketing Campaigns Segments 2.0 API + Twilio SendGrid Marketing Campaigns Single Sends API
Manage recipient consent and receive delivery events
An agent maintains suppression groups so unsubscribed recipients are filtered, and configures an event webhook to consume delivery and engagement events in near real time.
Create a suppression group for opt-outs, then configure an event webhook to receive delivery and engagement events.
Twilio SendGrid Suppressions API + Twilio SendGrid Webhook Configuration API
Intent-based discovery
An agent searches the Jentic API Directory for the SendGrid capability it needs, such as sending mail or building a segment, and loads the matching operation on demand instead of hardcoding endpoints across the portfolio.
SendGrid maintains a current Marketing Campaigns stack (Contacts, Lists, Segments V2, Single Sends, Designs, Senders) and an older legacy stack still used by some accounts. The legacy Contacts, Campaigns, and Sender Identities APIs remain operational, but new work should target the current versions where possible.
How do these APIs help with email deliverability?
Several APIs focus on reputation and inbox placement: domain authentication and reverse DNS establish sender trust, link branding serves tracked links from your own domain, dedicated IP management and IP warmup build a sending reputation gradually, and the engagement quality API reports a score correlated with deliverability.
Can an agent track and report on email performance?
Yes. The Statistics API returns account-wide metrics by category, browser, and mailbox provider, while the Marketing Campaigns Statistics API scopes results to Automations and Single Sends. The Email Activity API lets an agent query and download data about individual stored messages.
How does an agent manage recipient consent and privacy?
The Suppressions API manages unsubscribe and suppression groups so opted-out recipients are filtered from sends, and the Recipients' Data Erasure API deletes a recipient's personal data to support data privacy obligations. Tracking settings control which interactions are recorded.
All 4 are in the Jentic catalogue with the same one-credential, intent-search pattern.