Sendgrid Twilio SendGrid Suppressions API
Browse all Sendgrid APIs★ Only Publicly Available OpenAPI DocumentCommunicationsEmail Deliverybearer33 EndpointsREST
For Agents
Programmatically create a new suppression group, retrieve all suppression groups associated with the user.. Covers 33 operations with bearer authentication.
Use for: I need to a new suppression group, I want to all suppression groups associated with the user., Search for information on a single suppression group., Find all a suppression group.
Not supported: Does not handle payments, crm, or developer tools — use for communications only.
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.
Install Jentic One Beta
Connect the Twilio SendGrid Suppressions API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Twilio SendGrid Suppressions 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 Suppressions API.
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
Patterns agents use Twilio SendGrid Suppressions API for, with concrete tasks.
★ 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..
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.
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.
Search Jentic for 'create a new suppression group', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
33 endpoints — the twilio sendgrid suppressions api allows you to manage your suppressions or unsubscribes and suppression or unsubscribe groups.
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
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
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Twilio SendGrid Suppressions API bearer credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'create a new suppression group') and Jentic returns the matching Twilio SendGrid Suppressions API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Twilio SendGrid Suppressions API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Twilio SendGrid Suppressions API through Jentic.
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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.
GET STARTED