For Agents
Programmatically create subuser, list all subusers. Covers 14 operations with bearer authentication.
Get started with Twilio SendGrid Subusers in minutes using your preferred integration method.
# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
"jentic": {
"url": "https://api.jentic.com/mcp",
"auth": "oauth"
}
}
# Then ask your agent:
"create subuser"
# → Jentic returns the GET /events tool with parameter schema, agent executes.What an agent can do with Twilio SendGrid Subusers API.
Create Subuser
List all Subusers
Enable/disable a subuser
Delete a subuser
Get the Credits for a Subuser
GET STARTED
Use for: I need to subuser, I want to all subusers, Search for enable/disable a subuser, Find all a subuser
Not supported: Does not handle communications, crm, or developer tools — use for payments only.
Jentic publishes the only available OpenAPI document for Twilio SendGrid Subusers, keeping it validated and agent-ready.
The Twilio SendGrid Subusers API allows you to create and manage your Subuser accounts. Subusers are available on [Pro and Premier plans](https://sendgrid.com/pricing), and you can think of them as sub-accounts. Each Subuser can have its own sending domains, IP addresses, and reporting. SendGrid recommends creating Subusers for each of the different types of emails you send—one Subuser for transac. The API exposes 14 endpoints secured with bearer authentication.
Update the Credits for a Subuser
Patterns agents use Twilio SendGrid Subusers API for, with concrete tasks.
★ Payments Operations
Use the Twilio SendGrid Subusers to perform payments operations programmatically. The API provides 14 endpoints covering core functionality including create subuser, list all subusers, enable/disable a subuser.
Call POST /v3/subusers to create subuser
Automated Subusers Management
Automate subusers operations by combining multiple Twilio SendGrid Subusers endpoints. Agents can list all subusers and then enable/disable a subuser in a single workflow.
Call GET /v3/subusers to list all subusers, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Twilio SendGrid Subusers 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 subuser', load the operation schema, and execute with Jentic-managed credentials
14 endpoints — the twilio sendgrid subusers api allows you to create and manage your subuser accounts.
METHOD
PATH
DESCRIPTION
/v3/subusers
Create Subuser
/v3/subusers
List all Subusers
/v3/subusers/{subuser_name}
Enable/disable a subuser
/v3/subusers/{subuser_name}
Delete a subuser
/v3/subusers/{subuser_name}/website_access
Enable/Disable website access for a Subuser
/v3/subusers/{subuser_name}/credits
Get the Credits for a Subuser
/v3/subusers/{subuser_name}/credits
Update the Credits for a Subuser
/v3/subusers/{subuser_name}/credits/remaining
Update the remaining credits for a Subuser
/v3/subusers
Create Subuser
/v3/subusers
List all Subusers
/v3/subusers/{subuser_name}
Enable/disable a subuser
/v3/subusers/{subuser_name}
Delete a subuser
/v3/subusers/{subuser_name}/website_access
Enable/Disable website access for a Subuser
Three things that make agents converge on Jentic-routed access.
Credential isolation
Twilio SendGrid Subusers 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 subuser') and Jentic returns the matching Twilio SendGrid Subusers operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Twilio SendGrid Subusers integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Alternatives and complements available in the Jentic catalogue.
Stripe
Alternative payments API
Choose Stripe when you need a different approach to payments operations
Adyen
Alternative payments API
Choose Adyen when you need a different approach to payments operations
Square
Complementary payments API
Choose Square when you need a complementary approach to payments operations
Paypal
Complementary payments API
Choose Paypal when you need a complementary approach to payments operations
Specific to using Twilio SendGrid Subusers API through Jentic.
What authentication does the Twilio SendGrid Subusers use?
The Twilio SendGrid Subusers 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 subuser with the Twilio SendGrid Subusers?
Yes. Use the POST /v3/subusers endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Twilio SendGrid Subusers?
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 subuser through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'create subuser'. Jentic returns the matching Twilio SendGrid Subusers operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the Twilio SendGrid Subusers have?
The Twilio SendGrid Subusers exposes 14 endpoints covering subusers, subuser statistics operations.
/v3/subusers/{subuser_name}/credits
Get the Credits for a Subuser
/v3/subusers/{subuser_name}/credits
Update the Credits for a Subuser
/v3/subusers/{subuser_name}/credits/remaining
Update the remaining credits for a Subuser