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

# Sendgrid Twilio SendGrid Scopes API

The Twilio SendGrid Scopes API allows you to retrieve the scopes or permissions available to a user, see the user's attempts to access your SendGrid account, and, if necessary, deny an access request. The API exposes 4 endpoints secured with bearer authentication.

## For AI agents

Programmatically retrieve a list of scopes for which this user has access., retrieve access requests. Covers 4 operations with bearer authentication.

## Scope

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

## Capabilities

- Retrieve a list of scopes for which this user has access.
- Deny access request
- Approve access request
- Query and filter Twilio SendGrid Scopes API records by parameters
- Monitor Twilio SendGrid Scopes API operational status and events

## Use cases

### Identity and Authentication Operations

Use the Twilio SendGrid Scopes API to perform identity auth operations programmatically. The API provides 4 endpoints covering core functionality including retrieve a list of scopes for which this user has access., retrieve access requests, deny access request.

Example prompt: Call GET /v3/scopes to retrieve a list of scopes for which this user has access.

### Automated Scopes Management

Automate scopes operations by combining multiple Twilio SendGrid Scopes API endpoints. Agents can retrieve access requests and then deny access request in a single workflow.

Example prompt: Call GET /v3/scopes/requests to retrieve access requests, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Twilio SendGrid Scopes 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 a list of scopes for which this user has access.', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /v3/scopes | Retrieve a list of scopes for which this user has access. |
| GET | /v3/scopes/requests | Retrieve access requests |
| DELETE | /v3/scopes/requests/{request_id} | Deny access request |
| PATCH | /v3/scopes/requests/{request_id}/approve | Approve access request |

## Key resources

- **Scopes** — Twilio SendGrid Scopes API

## Why Jentic

- **Setup:** Wiring the Twilio SendGrid Scopes 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 Scopes API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** The Scopes API puts the access request id in the URL path (/v3/scopes/requests/{request_id}), so a rule can pin your agent to one scope request. You choose the operations it may call, so ones like approving or denying a request 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 'list the scopes this user can access', and Jentic returns the matching Scopes 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 Scopes API use?

The Twilio SendGrid Scopes 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 a list of scopes for which this user has access. with the Twilio SendGrid Scopes API?

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

### What are the rate limits for the Twilio SendGrid Scopes 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 a list of scopes for which this user has access. through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'retrieve a list of scopes for which this user has access.'. Jentic returns the matching Twilio SendGrid Scopes API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Twilio SendGrid Scopes API have?

The Twilio SendGrid Scopes API exposes 4 endpoints covering scopes operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which SendGrid Scopes operations the agent may call and which stored token it may use. You can grant only read access, such as listing scopes with GET /v3/scopes or fetching access requests with GET /v3/scopes/requests, while withholding the operations that approve or deny a request. Since the access request id sits in the path at /v3/scopes/requests/{request_id}, you can also pin the agent to a single request rather than the whole set.