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

# Sendgrid Twilio SendGrid IP Access Management API

IP Twilio SendGrid IP Access Management API allows you to control which IP addresses can be used to access your account, either through the SendGrid application user interface or the API. There is no limit to the number of IP addresses that you can allow. It is possible to remove your own IP address from your list of allowed addresses, thus blocking your own access to your account. While we are ab. The API exposes 6 endpoints secured with bearer authentication.

## For AI agents

Programmatically retrieve all recent access attempts, add one or more ips to the allow list. Covers 6 operations with bearer authentication.

## Scope

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

## Capabilities

- Retrieve all recent access attempts
- Add one or more IPs to the allow list
- Remove one or more IPs from the allow list
- Query and filter Twilio SendGrid IP Access Management API records by parameters
- Monitor Twilio SendGrid IP Access Management API operational status and events

## Use cases

### E-Commerce Operations

Use the Twilio SendGrid IP Access Management API to perform e commerce operations programmatically. The API provides 6 endpoints covering core functionality including retrieve all recent access attempts, add one or more ips to the allow list, retrieve a list of currently allowed ips.

Example prompt: Call GET /v3/access_settings/activity to retrieve all recent access attempts

### Automated IP Access Management Management

Automate ip access management operations by combining multiple Twilio SendGrid IP Access Management API endpoints. Agents can add one or more ips to the allow list and then retrieve a list of currently allowed ips in a single workflow.

Example prompt: Call POST /v3/access_settings/whitelist to add one or more ips to the allow list, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Twilio SendGrid IP Access 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 'retrieve all recent access attempts', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /v3/access_settings/activity | Retrieve all recent access attempts |
| POST | /v3/access_settings/whitelist | Add one or more IPs to the allow list |
| GET | /v3/access_settings/whitelist | Retrieve a list of currently allowed IPs |
| DELETE | /v3/access_settings/whitelist | Remove one or more IPs from the allow list |
| GET | /v3/access_settings/whitelist/{rule_id} | Retrieve a specific allowed IP |
| DELETE | /v3/access_settings/whitelist/{rule_id} | Remove a specific IP from the allowed list |

## Key resources

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

## Why Jentic

- **Setup:** Wiring the Twilio SendGrid IP Access 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 IP allowlist rules yourself. Through Jentic you install once, import the Twilio SendGrid IP Access Management API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** This API puts the allowlist rule id in the URL path (/v3/access_settings/whitelist/{rule_id}), so a rule can pin your agent to reading one allowlist entry and recent access activity. You choose the operations it may call, so removing an allowlist entry is not included unless you add it.
- **Credential handling:** Your Twilio SendGrid IP Access 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 'retrieve all recent access attempts' or 'add an IP to the allowlist', and Jentic returns the matching Twilio SendGrid IP Access Management API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Shopify** — Alternative e commerce API
- **Stripe** — Alternative e commerce API

## FAQ

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

The Twilio SendGrid IP Access 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 retrieve all recent access attempts with the Twilio SendGrid IP Access Management API?

Yes. Use the GET /v3/access_settings/activity 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 Access 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 retrieve all recent access attempts through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'retrieve all recent access attempts'. Jentic returns the matching Twilio SendGrid IP Access 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 Access Management API have?

The Twilio SendGrid IP Access Management API exposes 6 endpoints covering ip access management operations.

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

Yes. Because Jentic One is self-hosted, your own rules decide which of this API's operations your agent may call and which stored credential it may use. You can allow only read operations such as GET /v3/access_settings/activity to review recent access attempts and GET /v3/access_settings/whitelist/{rule_id} to inspect a single allowlist entry, while withholding destructive calls like DELETE /v3/access_settings/whitelist. Adding or removing allowlist IPs stays off limits unless you explicitly grant those operations.