Install Jentic One Beta

Connect the Twilio SendGrid Subusers to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Twilio SendGrid Subusers, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fsendgrid.com%2Ftwilio-sendgrid-subusers" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fsendgrid.com%2Ftwilio-sendgrid-subusers" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Twilio SendGrid Subusers API.

Create Subuser

List all Subusers

Enable/disable a subuser

Delete a subuser

GET STARTED

Start building with Twilio SendGrid Subusers API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Twilio SendGrid Subusers API for, with concrete tasks.

★ Payments Operations

Use the Twilio SendGrid Subusers to perform payments operations programmatically. The API provides 14 endpoints covering core functionality including create subuser, list all subusers, enable/disable a subuser.

Call POST /v3/subusers to create subuser

Automated Subusers Management

Automate subusers operations by combining multiple Twilio SendGrid Subusers endpoints. Agents can list all subusers and then enable/disable a subuser in a single workflow.

Call GET /v3/subusers to list all subusers, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Twilio SendGrid Subusers 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.

Search Jentic for 'create subuser', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

14 endpoints — the twilio sendgrid subusers api allows you to create and manage your subuser accounts.

METHOD

PATH

DESCRIPTION

POST

/v3/subusers

Create Subuser

GET

/v3/subusers

List all Subusers

PATCH

/v3/subusers/{subuser_name}

Enable/disable a subuser

DELETE

/v3/subusers/{subuser_name}

Delete a subuser

PATCH

/v3/subusers/{subuser_name}/website_access

Enable/Disable website access for a Subuser

GET

/v3/subusers/{subuser_name}/credits

Get the Credits for a Subuser

PUT

/v3/subusers/{subuser_name}/credits

Update the Credits for a Subuser

PATCH

/v3/subusers/{subuser_name}/credits/remaining

Update the remaining credits for a Subuser

POST

/v3/subusers

Create Subuser

GET

/v3/subusers

List all Subusers

PATCH

/v3/subusers/{subuser_name}

Enable/disable a subuser

DELETE

/v3/subusers/{subuser_name}

Delete a subuser

PATCH

/v3/subusers/{subuser_name}/website_access

Enable/Disable website access for a Subuser

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Twilio SendGrid Subusers 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 Subusers API from the API Directory, store the token once, and your agent calls it.

Permission scoping

The Subusers API puts the subuser name in the URL path (/v3/subusers/{subuser_name}/...), so a rule can pin your agent to one subuser. You choose the operations it may call, so destructive ones like deleting a subuser are not included unless you add them.

Credential isolation

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.

Intent-based discovery

Agents search Jentic by intent such as 'create a subuser', and Jentic returns the matching Subusers operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Twilio SendGrid Subusers API through Jentic.

What authentication does the Twilio SendGrid Subusers use?

The Twilio SendGrid Subusers 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 subuser with the Twilio SendGrid Subusers?

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

What are the rate limits for the Twilio SendGrid Subusers?

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 subuser through Jentic?

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

How many endpoints does the Twilio SendGrid Subusers have?

The Twilio SendGrid Subusers exposes 14 endpoints covering subusers, subuser statistics operations.

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

Yes. Jentic One is self-hosted, so your own rules decide which operations and credentials the agent may use. Because the subuser name sits in the URL path, such as /v3/subusers/{subuser_name}/credits, you can pin the agent to a single subuser and grant only the calls it needs, like GET /v3/subusers to list or GET /v3/subusers/{subuser_name}/credits to read credits. Destructive operations such as DELETE /v3/subusers/{subuser_name} or PATCH website access stay off unless you explicitly allow them.

Sendgrid Twilio SendGrid Subusers

Name: Twilio SendGrid Subusers API
Brand: Twilio SendGrid Subusers
Availability: InStock

Browse all Sendgrid APIs

PaymentsBilling Subscriptionsbearer14 EndpointsREST

For Agents

Programmatically create subuser, list all subusers. Covers 14 operations with bearer authentication.

Use for: I need to subuser, I want to all subusers, Search for enable/disable a subuser, Find all a subuser

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

The Twilio SendGrid Subusers API allows you to create and manage your Subuser accounts. Subusers are available on [Pro and Premier plans](https://sendgrid.com/pricing), and you can think of them as sub-accounts. Each Subuser can have its own sending domains, IP addresses, and reporting. SendGrid recommends creating Subusers for each of the different types of emails you send-one Subuser for transac. The API exposes 14 endpoints secured with bearer authentication.

Jentic One on Github View OpenAPI Document

Connect the Twilio SendGrid Subusers to your agent

Capabilities

Start building with Twilio SendGrid Subusers API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Sendgrid Twilio SendGrid Subusers