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

# Sendgrid Twilio SendGrid Suppressions API

The Twilio SendGrid Suppressions API allows you to manage your Suppressions or Unsubscribes and Suppression or Unsubscribe groups. With SendGrid, an unsubscribe is the action an email recipient takes when they opt-out of receiving your messages. A suppression is the action you take as a sender to filter or suppress an unsubscribed address from your email send. From the perspective of the recipient. The API exposes 33 endpoints secured with bearer authentication.

## For AI agents

Programmatically create a new suppression group, retrieve all suppression groups associated with the user.. Covers 33 operations with bearer authentication.

## Scope

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

## Capabilities

- Create a new suppression group
- Retrieve all suppression groups associated with the user.
- Get information on a single suppression group.
- Update a suppression group.
- Delete a Suppression Group
- Add suppressions to a suppression group

## Use cases

### Communications Operations

Use the Twilio SendGrid Suppressions API to perform communications operations programmatically. The API provides 33 endpoints covering core functionality including create a new suppression group, retrieve all suppression groups associated with the user., get information on a single suppression group..

Example prompt: Call POST /v3/asm/groups to create a new suppression group

### Automated Suppressions Management

Automate suppressions operations by combining multiple Twilio SendGrid Suppressions API endpoints. Agents can retrieve all suppression groups associated with the user. and then get information on a single suppression group. in a single workflow.

Example prompt: Call GET /v3/asm/groups to retrieve all suppression groups associated with the user., then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Twilio SendGrid Suppressions 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 'create a new suppression group', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /v3/asm/groups | Create a new suppression group |
| GET | /v3/asm/groups | Retrieve all suppression groups associated with the user. |
| GET | /v3/asm/groups/{group_id} | Get information on a single suppression group. |
| PATCH | /v3/asm/groups/{group_id} | Update a suppression group. |
| DELETE | /v3/asm/groups/{group_id} | Delete a Suppression Group |
| POST | /v3/asm/groups/{group_id}/suppressions | Add suppressions to a suppression group |
| GET | /v3/asm/groups/{group_id}/suppressions | Retrieve all suppressions for a suppression group |
| DELETE | /v3/asm/groups/{group_id}/suppressions/{email} | Delete a suppression from a suppression group |

## Key resources

- **Suppressions** — Twilio SendGrid Suppressions API
- **Global Suppressions** — Twilio SendGrid Suppressions API: Global Suppressions operations
- **Unsubscribe Groups** — Twilio SendGrid Suppressions API: Unsubscribe Group operations
- **Blocks** — Twilio SendGrid Suppressions API: Blocks operations
- **Bounces** — Twilio SendGrid Suppressions API: Bounces operations

## Why Jentic

- **Setup:** Wiring the Twilio SendGrid Suppressions 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 Suppressions API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** The Suppressions API puts the group id in the URL path (/v3/asm/groups/{group_id}/...), so a rule can pin your agent to one suppression group. You choose the operations it may call, so destructive ones like deleting a group or removing a suppression are not included unless you add them.
- **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 'create a new suppression group', and Jentic returns the matching Suppressions 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 Suppressions API use?

The Twilio SendGrid Suppressions 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 create a new suppression group with the Twilio SendGrid Suppressions API?

Yes. Use the POST /v3/asm/groups endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Twilio SendGrid Suppressions 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 create a new suppression group through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create a new suppression group'. Jentic returns the matching Twilio SendGrid Suppressions API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Twilio SendGrid Suppressions API have?

The Twilio SendGrid Suppressions API exposes 33 endpoints covering suppressions, global suppressions, unsubscribe groups operations.

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

Yes. Because you run Jentic One yourself, you decide which suppression operations your agent may call, so you can grant read-only access like GET /v3/asm/groups while leaving out destructive ones such as DELETE /v3/asm/groups/{group_id} or removing a suppression. Since the group id sits in the URL path, your own rules can pin the agent to a single suppression group rather than every group on the account. Your SendGrid bearer token is held by your instance and injected at call time, so the agent can only act within the operations and credentials you allow.