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

# Sendgrid Twilio SendGrid IP Address API

The Twilio SendGrid IP Address API allows you to add and manage dedicated IP addresses and IP Pools for your SendGrid account and Subusers. If you are sending any significant amount of email, SendGrid typically suggests sending from dedicated IPs. It's also best to send marketing and transactional emails from separate IP addresses. In order to do this, you'll need to set up IP Pools, which are gro. The API exposes 12 endpoints secured with bearer authentication.

## For AI agents

Programmatically add ips, retrieve all ip addresses. Covers 12 operations with bearer authentication.

## Scope

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

## Capabilities

- Add IPs
- Retrieve all IP addresses
- Create an IP pool
- Query and filter Twilio SendGrid IP Address API records by parameters
- Monitor Twilio SendGrid IP Address API operational status and events

## Use cases

### Communications Operations

Use the Twilio SendGrid IP Address API to perform communications operations programmatically. The API provides 12 endpoints covering core functionality including add ips, retrieve all ip addresses, retrieve all ip pools an ip address belongs to.

Example prompt: Call POST /v3/ips to add ips

### Automated IP Addresses Management

Automate ip addresses operations by combining multiple Twilio SendGrid IP Address API endpoints. Agents can retrieve all ip addresses and then retrieve all ip pools an ip address belongs to in a single workflow.

Example prompt: Call GET /v3/ips to retrieve all ip addresses, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Twilio SendGrid IP Address 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 ips', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /v3/ips | Add IPs |
| GET | /v3/ips | Retrieve all IP addresses |
| GET | /v3/ips/{ip_address} | Retrieve all IP pools an IP address belongs to |
| GET | /v3/ips/assigned | Retrieve all assigned IPs |
| POST | /v3/ips/pools | Create an IP pool |
| GET | /v3/ips/pools | Retrieve all IP pools |
| GET | /v3/ips/pools/{pool_name} | Retrieve all the IPs in a specified pool |
| PUT | /v3/ips/pools/{pool_name} | Rename an IP pool |

## Key resources

- **IP Addresses** — Twilio SendGrid IP Address API Operations
- **IP Pools** — Twilio SendGrid IP Address Pool API Operations

## Why Jentic

- **Setup:** Wiring the Twilio SendGrid IP Address API by hand means learning its bearer API key auth, picking the right global api.sendgrid.com or EU api.eu.sendgrid.com host, and handling paging and retries yourself. Through Jentic you install once, import the IP Address API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** This API puts the IP or pool name in the URL path (/v3/ips/{ip_address}, /v3/ips/pools/{pool_name}), so a rule can pin your agent to one IP or one pool: it can read and update that resource and nothing else. You choose the operations it may call, so adding a new IP with POST /v3/ips is not included unless you add it.
- **Credential handling:** Your Twilio SendGrid 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 'list assigned IPs' or 'create an IP pool', and Jentic returns the matching Twilio SendGrid IP Address API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Twilio** — Alternative communications API
- **Pusher** — Alternative communications API

## FAQ

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

The Twilio SendGrid IP Address 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 ips with the Twilio SendGrid IP Address API?

Yes. Use the POST /v3/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 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 ips through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'add ips'. Jentic returns the matching Twilio SendGrid IP Address 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 API have?

The Twilio SendGrid IP Address API exposes 12 endpoints covering ip addresses, ip pools operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use, so you can allow only read calls like GET /v3/ips or GET /v3/ips/pools while withholding writes such as POST /v3/ips or PUT /v3/ips/pools/{pool_name}. Since this API carries the IP or pool name in the URL path (/v3/ips/{ip_address}, /v3/ips/pools/{pool_name}), a rule can pin the agent to a single IP address or pool and let it touch nothing else. Any operation you do not grant, such as adding a new IP with POST /v3/ips, stays off limits.