canonical: https://jentic.com/apis/sendgrid.com/twilio-sendgrid-engagement-quality-api

# Sendgrid Twilio SendGrid Engagement Quality API

The SendGrid Engagement Quality (SEQ) API allows you to retrieve metrics that define the quality of your email program. An SEQ score is correlated with: - The quality of the data in a sender’s program. - How “wanted” the sender's email is by their recipients. Because “wanted” email and deliverability are closely related, a higher SEQ metric is correlated with greater deliverability. This means the. The API exposes 2 endpoints secured with bearer authentication.

## For AI agents

Programmatically get engagement quality scores, get subusers' engagement quality scores. Covers 2 operations with bearer authentication.

## Scope

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

## Capabilities

- Get Engagement Quality Scores
- Manage communications data programmatically
- Integrate Twilio SendGrid Engagement Quality API into automated workflows
- Query and filter Twilio SendGrid Engagement Quality API records by parameters
- Monitor Twilio SendGrid Engagement Quality API operational status and events

## Use cases

### Communications Operations

Use the Twilio SendGrid Engagement Quality API to perform communications operations programmatically. The API provides 2 endpoints covering core functionality including get engagement quality scores, get subusers' engagement quality scores.

Example prompt: Call GET /v3/engagementquality/scores to get engagement quality scores

### Data Retrieval and Monitoring

Query Twilio SendGrid Engagement Quality 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 Engagement Quality API endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call Twilio SendGrid Engagement Quality 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 'get engagement quality scores', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /v3/engagementquality/scores | Get Engagement Quality Scores |
| GET | /v3/engagementquality/subusers/scores | Get Subusers' Engagement Quality Scores |

## Key resources

- **Engagement Quality** — Twilio SendGrid Engagement Quality API

## Why Jentic

- **Setup:** Wiring the Twilio SendGrid Engagement Quality 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 Engagement Quality API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** The Engagement Quality API scores travel as query parameters, not resource ids in the path, so scope your agent to the operations it needs, such as reading account scores or subuser scores, rather than to a single record. You choose the operations it may call, so nothing beyond that set runs 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 'get engagement quality scores', and Jentic returns the matching Engagement Quality 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 Engagement Quality API use?

The Twilio SendGrid Engagement Quality 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 get engagement quality scores with the Twilio SendGrid Engagement Quality API?

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

### What are the rate limits for the Twilio SendGrid Engagement Quality 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 get engagement quality scores through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get engagement quality scores'. Jentic returns the matching Twilio SendGrid Engagement Quality API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Twilio SendGrid Engagement Quality API have?

The Twilio SendGrid Engagement Quality API exposes 2 endpoints covering engagement quality operations.

### Can I limit what my agent is allowed to do with the Twilio SendGrid Engagement Quality API?

Yes. Because you run Jentic One yourself and set its rules, you decide which of this API's operations your agent may call and which credentials it may use. This API has just two read operations, GET /v3/engagementquality/scores for account scores and GET /v3/engagementquality/subusers/scores for subuser scores, so you can allow only account-level reads and leave subuser reads out, or the reverse. Since scores are selected through query parameters rather than resource ids in the path, you scope the agent to the operations it needs, and nothing outside that set runs unless you add it.