canonical: https://jentic.com/apis/sendgrid.com/twilio-sendgrid-ip-address-management-api

# Sendgrid Twilio SendGrid IP Address Management API

The Twilio SendGrid IP Address Management API combines functionality that was previously split between the Twilio SendGrid [IP Address API](https://docs.sendgrid.com/api-reference/ip-address) and [IP Pools API](https://docs.sendgrid.com/api-reference/ip-pools). This functionality includes adding IP addresses to your account, assigning IP addresses to IP Pools and Subusers, among other tasks. The API exposes 15 endpoints secured with bearer authentication.

## For AI agents

Programmatically add a twilio sendgrid ip address, get a list of all ip addresses on your account. Covers 15 operations with bearer authentication.

## Scope

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

## Capabilities

- Add a Twilio SendGrid IP Address
- Get a List of all IP Addresses on your Account
- Update Details for an IP Address
- Assign a Batch of Subusers to an IP
- Delete a Batch of Subusers from an IP

## Use cases

### Productivity Operations

Use the Twilio SendGrid IP Address Management API to perform productivity operations programmatically. The API provides 15 endpoints covering core functionality including add a twilio sendgrid ip address, get a list of all ip addresses on your account, get details for an ip address.

Example prompt: Call POST /v3/send_ips/ips to add a twilio sendgrid ip address

### Automated IP Address Management Management

Automate ip address management operations by combining multiple Twilio SendGrid IP Address Management API endpoints. Agents can get a list of all ip addresses on your account and then get details for an ip address in a single workflow.

Example prompt: Call GET /v3/send_ips/ips to get a list of all ip addresses on your account, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Twilio SendGrid IP Address Management 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 'add a twilio sendgrid ip address', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /v3/send_ips/ips | Add a Twilio SendGrid IP Address |
| GET | /v3/send_ips/ips | Get a List of all IP Addresses on your Account |
| GET | /v3/send_ips/ips/{ip} | Get Details for an IP Address |
| PATCH | /v3/send_ips/ips/{ip} | Update Details for an IP Address |
| GET | /v3/send_ips/ips/{ip}/subusers | Get a List of Subusers Assigned to an IP |
| POST | /v3/send_ips/ips/{ip}/subusers:batchAdd | Assign a Batch of Subusers to an IP |
| POST | /v3/send_ips/ips/{ip}/subusers:batchDelete | Delete a Batch of Subusers from an IP |
| POST | /v3/send_ips/pools | Create an IP Pool with a Name and IP Assignments |

## Key resources

- **IP Address Management** — Twilio SendGrid IP Address Management API

## Why Jentic

- **Setup:** Wiring the Twilio SendGrid IP Address Management 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 IPs and pools yourself. Through Jentic you install once, import the Twilio SendGrid IP Address Management API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** This API puts the IP address in the URL path (/v3/send_ips/ips/{ip}/...), so a rule can pin your agent to one IP: it can read that IP and its subusers. You choose the operations it may call, so batch subuser removal is not included unless you add it.
- **Credential handling:** Your Twilio SendGrid IP Address Management 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 'add a SendGrid IP address' or 'list IP pools', and Jentic returns the matching Twilio SendGrid IP Address Management API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Asana** — Alternative productivity API
- **Monday** — Alternative productivity API
- **Clickup** — Complementary productivity API

## FAQ

### What authentication does the Twilio SendGrid IP Address Management API use?

The Twilio SendGrid IP Address Management 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 add a twilio sendgrid ip address with the Twilio SendGrid IP Address Management API?

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

### What are the rate limits for the Twilio SendGrid IP Address Management 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 add a twilio sendgrid ip address through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'add a twilio sendgrid ip address'. Jentic returns the matching Twilio SendGrid IP Address Management API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Twilio SendGrid IP Address Management API have?

The Twilio SendGrid IP Address Management API exposes 15 endpoints covering ip address management operations.

### Can I limit what my agent is allowed to do with the Twilio SendGrid IP Address Management 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 puts the IP address in the URL path (for example /v3/send_ips/ips/{ip}/subusers), a rule can pin the agent to a single IP and let it only read that IP and its assigned subusers. You pick the exact operations it may call, so destructive actions like the batch subuser delete are excluded unless you explicitly add them.