Sendgrid Twilio SendGrid Tracking Settings API
Browse all Sendgrid APIs64
AI ReadinessAI-Aware (B)64/100
CommunicationsEmail Deliverybearer9 EndpointsREST
For Agents
Programmatically retrieve tracking settings, retrieve click track settings. Covers 9 operations with bearer authentication.
Use for: I need to tracking settings, I want to click track settings, Search for click tracking settings, Find all google analytics settings
Not supported: Does not handle payments, crm, or developer tools - use for communications only.
The Twilio SendGrid Tracking Settings API allows you to configure which tracking settings are enabled for your messages. You can track many of your recipients' interactions with your emails, including which emails they open, which links they click, and when they subscribe to or unsubscribe from your emails. See [**Tracking Settings**](https://docs.sendgrid.com/ui/account-and-settings/tracking) for. The API exposes 9 endpoints secured with bearer authentication.
Install Jentic One Beta
Connect the Twilio SendGrid Tracking Settings API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Twilio SendGrid Tracking 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-tracking-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-tracking-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 Tracking Settings API.
Retrieve Tracking Settings
Update Click Tracking Settings
Get Open Tracking Settings
Query and filter Twilio SendGrid Tracking Settings API records by parameters
Monitor Twilio SendGrid Tracking Settings API operational status and events
Use Cases
Patterns agents use Twilio SendGrid Tracking Settings API for, with concrete tasks.
★ Communications Operations
Use the Twilio SendGrid Tracking Settings API to perform communications operations programmatically. The API provides 9 endpoints covering core functionality including retrieve tracking settings, retrieve click track settings, update click tracking settings.
Call GET /v3/tracking_settings to retrieve tracking settings
Automated Tracking Management
Automate tracking operations by combining multiple Twilio SendGrid Tracking Settings API endpoints. Agents can retrieve click track settings and then update click tracking settings in a single workflow.
Call GET /v3/tracking_settings/click to retrieve click track settings, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Twilio SendGrid Tracking 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 tracking settings', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
9 endpoints — the twilio sendgrid tracking settings api allows you to configure which tracking settings are enabled for your messages.
METHOD
PATH
DESCRIPTION
GET
/v3/tracking_settings
Retrieve Tracking Settings
GET
/v3/tracking_settings/click
Retrieve Click Track Settings
PATCH
/v3/tracking_settings/click
Update Click Tracking Settings
GET
/v3/tracking_settings/google_analytics
Retrieve Google Analytics Settings
PATCH
/v3/tracking_settings/google_analytics
Update Google Analytics Settings
GET
/v3/tracking_settings/open
Get Open Tracking Settings
PATCH
/v3/tracking_settings/open
Update Open Tracking Settings
GET
/v3/tracking_settings/subscription
Retrieve Subscription Tracking Settings
GET
/v3/tracking_settings
Retrieve Tracking Settings
GET
/v3/tracking_settings/click
Retrieve Click Track Settings
PATCH
/v3/tracking_settings/click
Update Click Tracking Settings
GET
/v3/tracking_settings/google_analytics
Retrieve Google Analytics Settings
PATCH
/v3/tracking_settings/google_analytics
Update Google Analytics Settings
GET
/v3/tracking_settings/open
Get Open Tracking Settings
PATCH
/v3/tracking_settings/open
Update Open Tracking Settings
GET
/v3/tracking_settings/subscription
Retrieve Subscription Tracking Settings
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
T
Twilio SendGrid Tracking Settings API
- AI-Aware (B)64/100
100
Foundational Compliance62
Developer Experience & Jentic Compatibility43
AI-Readiness & Agent Experience94
Agent Usability60
Security75
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
100
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
99%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
62
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
24%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
25%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
43
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: DSignals: 4
42%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
30%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
60
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
60%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
75
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A-Signals: 1
75%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Twilio SendGrid Tracking Settings API by hand means setting up its bearer token auth, choosing the right US or EU host (api.sendgrid.com or api.eu.sendgrid.com), and handling status codes yourself. Through Jentic you install once, import the Tracking Settings API from the API Directory, store the token once, and your agent calls it.
Permission scoping
The Tracking Settings API addresses named account settings such as click, open, and Google Analytics tracking rather than resource ids in the path, so scope your agent to the operations it needs, such as reading or updating a specific setting. You choose the operations it may call, so an update like changing click tracking is not included unless you add it.
Credential isolation
Your Twilio SendGrid token 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 tracking settings', and Jentic returns the matching Tracking Settings 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 Tracking Settings API through Jentic.
What authentication does the Twilio SendGrid Tracking Settings API use?
The Twilio SendGrid Tracking 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 tracking settings with the Twilio SendGrid Tracking Settings API?
Yes. Use the GET /v3/tracking_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 Tracking 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 tracking settings through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'retrieve tracking settings'. Jentic returns the matching Twilio SendGrid Tracking 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 Tracking Settings API have?
The Twilio SendGrid Tracking Settings API exposes 9 endpoints covering tracking operations.
Can I limit what my agent is allowed to do with the Twilio SendGrid Tracking Settings API?
Yes. Because Jentic One is self-hosted, your own rules decide which operations and credentials the agent may use, and you scope it to only the tracking settings it needs. This API addresses named account settings such as click, open, and Google Analytics tracking rather than resource ids in the path, so you can grant read-only access to GET /v3/tracking_settings/click while withholding the PATCH operations. An update like changing click tracking is never available to the agent unless you explicitly add that operation.
GET STARTED