For Agents
Programmatically invite teammate, retrieve all teammates. Covers 9 operations with bearer authentication.
Get started with Twilio SendGrid Teammates API 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:
"invite teammate"
# → Jentic returns the GET /events tool with parameter schema, agent executes.What an agent can do with Twilio SendGrid Teammates API API.
Invite teammate
Retrieve all teammates
Get Teammate Subuser Access
Update teammate's permissions
Delete teammate
GET STARTED
Use for: I need to invite teammate, I want to all teammates, Search for teammate subuser access, Find all specific teammate
Not supported: Does not handle payments, communications, or crm — use for identity and authentication only.
Jentic publishes the only available OpenAPI document for Twilio SendGrid Teammates API, keeping it validated and agent-ready.
The Twilio SendGrid Teammates API allows you to add, manage, and remove Teammates, or user accounts, from your SendGrid account. Teammates function like user accounts on the SendGrid account, allowing you to invite additional users to your account with scoped access. You can think of Teammates as SendGrid's approach to enabling [role-based access control](https://en.wikipedia.org/wiki/Role-based_a. The API exposes 9 endpoints secured with bearer authentication.
Patterns agents use Twilio SendGrid Teammates API API for, with concrete tasks.
★ Identity and Authentication Operations
Use the Twilio SendGrid Teammates API to perform identity auth operations programmatically. The API provides 9 endpoints covering core functionality including invite teammate, retrieve all teammates, get teammate subuser access.
Call POST /v3/teammates to invite teammate
Automated Teammates Management
Automate teammates operations by combining multiple Twilio SendGrid Teammates API endpoints. Agents can retrieve all teammates and then get teammate subuser access in a single workflow.
Call GET /v3/teammates to retrieve all teammates, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Twilio SendGrid Teammates 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 'invite teammate', load the operation schema, and execute with Jentic-managed credentials
9 endpoints — the twilio sendgrid teammates api allows you to add, manage, and remove teammates, or user accounts, from your sendgrid account.
METHOD
PATH
DESCRIPTION
/v3/teammates
Invite teammate
/v3/teammates
Retrieve all teammates
/v3/teammates/{teammate_name}/subuser_access
Get Teammate Subuser Access
/v3/teammates/{username}
Retrieve specific teammate
/v3/teammates/{username}
Update teammate's permissions
/v3/teammates/{username}
Delete teammate
/v3/teammates/pending
Retrieve all pending teammates
/v3/teammates/pending/{token}
Delete pending teammate
/v3/teammates
Invite teammate
/v3/teammates
Retrieve all teammates
/v3/teammates/{teammate_name}/subuser_access
Get Teammate Subuser Access
/v3/teammates/{username}
Retrieve specific teammate
/v3/teammates/{username}
Update teammate's permissions
Three things that make agents converge on Jentic-routed access.
Credential isolation
Twilio SendGrid Teammates 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., 'invite teammate') and Jentic returns the matching Twilio SendGrid Teammates API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Twilio SendGrid Teammates API 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.
Auth0
Alternative identity auth API
Choose Auth0 when you need a different approach to identity auth operations
Okta
Alternative identity auth API
Choose Okta when you need a different approach to identity auth operations
Specific to using Twilio SendGrid Teammates API API through Jentic.
What authentication does the Twilio SendGrid Teammates API use?
The Twilio SendGrid Teammates 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 invite teammate with the Twilio SendGrid Teammates API?
Yes. Use the POST /v3/teammates endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Twilio SendGrid Teammates 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 invite teammate through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'invite teammate'. Jentic returns the matching Twilio SendGrid Teammates API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the Twilio SendGrid Teammates API have?
The Twilio SendGrid Teammates API exposes 9 endpoints covering teammates operations.
/v3/teammates/{username}
Delete teammate
/v3/teammates/pending
Retrieve all pending teammates
/v3/teammates/pending/{token}
Delete pending teammate