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

# Sendgrid Twilio SendGrid Account Provisioning API

The Twilio SendGrid Account Provisioning API provides a platform for Twilio SendGrid resellers to manage their customer accounts. This API is for companies that have a formal reseller partnership with Twilio SendGrid. You can access Twilio SendGrid sub-account functionality without becoming a reseller. If you require sub-account functionality, see the Twilio [SendGrid Subusers](https://docs.sendgr. The API exposes 9 endpoints secured with bearer authentication.

## For AI agents

Programmatically create an account, get all accounts. Covers 9 operations with bearer authentication.

## Scope

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

## Capabilities

- Create an account
- Get all accounts
- Delete an account
- Update account offerings
- Authenticate an account with single sign on

## Use cases

### Developer Tools Operations

Use the Twilio SendGrid Account Provisioning API to perform developer tools operations programmatically. The API provides 9 endpoints covering core functionality including create an account, get all accounts, delete an account.

Example prompt: Call POST /v3/partners/accounts to create an account

### Automated Account Management

Automate account operations by combining multiple Twilio SendGrid Account Provisioning API endpoints. Agents can get all accounts and then delete an account in a single workflow.

Example prompt: Call GET /v3/partners/accounts to get all accounts, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Twilio SendGrid Account Provisioning 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 an account', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /v3/partners/accounts | Create an account |
| GET | /v3/partners/accounts | Get all accounts |
| DELETE | /v3/partners/accounts/{accountID} | Delete an account |
| GET | /v3/partners/accounts/{accountID}/offerings | Get account offerings |
| PUT | /v3/partners/accounts/{accountID}/offerings | Update account offerings |
| POST | /v3/partners/accounts/{accountID}/sso | Authenticate an account with single sign on |
| GET | /v3/partners/accounts/{accountID}/state | Get an account's state |
| PUT | /v3/partners/accounts/{accountID}/state | Update an account's state |

## Key resources

- **Account** — Twilio SendGrid Account Provisioning API account operations.
- **Account State** — Twilio SendGrid Account Provisioning API account state operations.
- **Offering** — Twilio SendGrid Account Provisioning API offerings operations.

## Why Jentic

- **Setup:** Wiring the Twilio SendGrid Account Provisioning API by hand means learning its bearer auth where the API key is the token, choosing the right US or EU host (api.sendgrid.com or api.eu.sendgrid.com), and managing partner account state yourself. Through Jentic you install once, import the Twilio SendGrid Account Provisioning API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** This API puts the account id in the URL path (/v3/partners/accounts/{accountID}/...), so a rule can pin your agent to one account: it can read that account's offerings and state. You choose the operations it may call, so destructive ones like account deletion are not included unless you add them.
- **Credential handling:** Your Twilio SendGrid Account Provisioning API key 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 partner account' or 'read account state', and Jentic returns the matching Twilio SendGrid Account Provisioning API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the Twilio SendGrid Account Provisioning API use?

The Twilio SendGrid Account Provisioning 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 an account with the Twilio SendGrid Account Provisioning API?

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

### What are the rate limits for the Twilio SendGrid Account Provisioning 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 an account through Jentic?

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

### How many endpoints does the Twilio SendGrid Account Provisioning API have?

The Twilio SendGrid Account Provisioning API exposes 9 endpoints covering account, account state, offering operations.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which operations and credentials the agent may use. Because this API carries the account id in the URL path (/v3/partners/accounts/{accountID}/...), you can pin the agent to a single account and allow only read calls such as getting that account's offerings and state. Destructive operations like deleting an account are not available to the agent unless you explicitly add them.