canonical: https://jentic.com/apis/sendgrid.com/twilio-sendgrid-enforced-tls-api

# Sendgrid Twilio SendGrid Enforced TLS API

The Twilio SendGrid Enforced TLS API allows you to specify whether or not the recipient of your mail send is required to support TLS or have a valid certificate. Twilio SendGrid sends all emails with [Opportunistic TLS](https://sendgrid.com/blog/myth-opportunistic-tls-email-privacy/) by default, meaning email is sent with TLS, and if the recipient's inbox provider does not accept the TLS encryptio. The API exposes 2 endpoints secured with bearer authentication.

## For AI agents

Programmatically retrieve current enforced tls settings., update enforced tls settings. Covers 2 operations with bearer authentication.

## Scope

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

## Capabilities

- Retrieve current Enforced TLS settings.
- Update Enforced TLS settings
- Integrate Twilio SendGrid Enforced TLS API into automated workflows
- Query and filter Twilio SendGrid Enforced TLS API records by parameters
- Monitor Twilio SendGrid Enforced TLS API operational status and events

## Use cases

### Communications Operations

Use the Twilio SendGrid Enforced TLS API to perform communications operations programmatically. The API provides 2 endpoints covering core functionality including retrieve current enforced tls settings., update enforced tls settings.

Example prompt: Call GET /v3/user/settings/enforced_tls to retrieve current enforced tls settings.

### Data Retrieval and Monitoring

Query Twilio SendGrid Enforced TLS API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary Twilio SendGrid Enforced TLS API endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call Twilio SendGrid Enforced TLS 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 current enforced tls settings.', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /v3/user/settings/enforced_tls | Retrieve current Enforced TLS settings. |
| PATCH | /v3/user/settings/enforced_tls | Update Enforced TLS settings |

## Key resources

- **Enforced TLS** — The Twilio SendGrid Enforced TLS API

## Why Jentic

- **Setup:** Wiring the Twilio SendGrid Enforced TLS API by hand means learning its bearer auth where the API key is the token, choosing the right US or EU host (api.sendgrid.com or api.eu.sendgrid.com), and reading and patching account settings yourself. Through Jentic you install once, import the Twilio SendGrid Enforced TLS API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** This API updates account-level TLS settings by request body, so scoping stays operations-only: limit the agent to the operations it needs, such as reading the enforced TLS settings. You choose the operations it may call, so updating those settings is not included unless you add it.
- **Credential handling:** Your Twilio SendGrid Enforced TLS 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.
- **Discovery method:** Agents search Jentic by intent such as 'retrieve current enforced TLS settings' or 'update TLS enforcement', and Jentic returns the matching Twilio SendGrid Enforced TLS API 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 Enforced TLS API use?

The Twilio SendGrid Enforced TLS 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 current enforced tls settings. with the Twilio SendGrid Enforced TLS API?

Yes. Use the GET /v3/user/settings/enforced_tls endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Twilio SendGrid Enforced TLS 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 current enforced tls settings. through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'retrieve current enforced tls settings.'. Jentic returns the matching Twilio SendGrid Enforced TLS API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Twilio SendGrid Enforced TLS API have?

The Twilio SendGrid Enforced TLS API exposes 2 endpoints covering enforced tls operations.

### Can I limit what my agent is allowed to do with the SendGrid Enforced TLS API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use. The SendGrid Enforced TLS API has just two operations: read the current enforced TLS settings (GET /v3/user/settings/enforced_tls) and update them (PATCH /v3/user/settings/enforced_tls). You can grant your agent only the read operation so it can check the settings, and withhold the update operation so it cannot change your account's TLS enforcement unless you explicitly allow it.