canonical: https://jentic.com/apis/sendgrid.com/twilio-sendgrid-tracking-settings-api

# Sendgrid Twilio SendGrid Tracking Settings API

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.

## For AI agents

Programmatically retrieve tracking settings, retrieve click track settings. Covers 9 operations with bearer authentication.

## Scope

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

## Capabilities

- 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

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: Search Jentic for 'retrieve tracking settings', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| 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 |

## Key resources

- **Tracking** — Twilio SendGrid Tracking Settings API

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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

- **Twilio** — Alternative communications API
- **Pusher** — Alternative communications API

## FAQ

### 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.