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

# Sendgrid Twilio SendGrid Teammates API

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.

## For AI agents

Programmatically invite teammate, retrieve all teammates. Covers 9 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for identity and authentication only.

## Capabilities

- Invite teammate
- Retrieve all teammates
- Get Teammate Subuser Access
- Update teammate's permissions
- Delete teammate

## Use cases

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: Search Jentic for 'invite teammate', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /v3/teammates | Invite teammate |
| GET | /v3/teammates | Retrieve all teammates |
| GET | /v3/teammates/{teammate_name}/subuser_access | Get Teammate Subuser Access |
| GET | /v3/teammates/{username} | Retrieve specific teammate |
| PATCH | /v3/teammates/{username} | Update teammate's permissions |
| DELETE | /v3/teammates/{username} | Delete teammate |
| GET | /v3/teammates/pending | Retrieve all pending teammates |
| DELETE | /v3/teammates/pending/{token} | Delete pending teammate |

## Key resources

- **Teammates** — Twilio SendGrid Teammates API

## Why Jentic

- **Setup:** Wiring the Twilio SendGrid Teammates 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 Teammates API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** The Teammates API puts the username in the URL path (/v3/teammates/{username}), so a rule can pin your agent to one teammate. You choose the operations it may call, so destructive ones like deleting a teammate 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 'invite a teammate', and Jentic returns the matching Teammates operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Auth0** — Alternative identity auth API
- **Okta** — Alternative identity auth API

## FAQ

### 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 your Jentic One instance 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 through Jentic One, the self-hosted execution layer, 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.

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

Yes. Because Jentic One is self-hosted, your own rules decide which Teammates operations and credentials the agent may use. You can allow read-only calls like GET /v3/teammates and GET /v3/teammates/{username} while withholding destructive ones such as DELETE /v3/teammates/{username} or PATCH /v3/teammates/{username}. Since the username sits in the URL path, a rule can also pin the agent to a single teammate rather than the whole account.