canonical: https://jentic.com/apis/twilio.com/twilio---supersim

# Twilio - Supersim

This is the public Twilio REST API. The API exposes 31 endpoints secured with basic authentication.

## For AI agents

Programmatically retrieve a list of billing periods for a super sim., order an esim profile.. Covers 31 operations with basic authentication.

## Scope

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

## Capabilities

- Retrieve a list of Billing Periods for a Super SIM.
- Order an eSIM Profile.
- Fetch an eSIM Profile.
- Create a Fleet
- Updates the given properties of a Super SIM Fleet instance from your account.

## Use cases

### Developer Tools Operations

Use the Twilio - Supersim to perform developer tools operations programmatically. The API provides 31 endpoints covering core functionality including retrieve a list of billing periods for a super sim., order an esim profile., retrieve a list of esim profiles..

Example prompt: Call GET /v1/Sims/{SimSid}/BillingPeriods to retrieve a list of billing periods for a super sim.

### Automated SupersimV1BillingPeriod Management

Automate supersimv1billingperiod operations by combining multiple Twilio - Supersim endpoints. Agents can order an esim profile. and then retrieve a list of esim profiles. in a single workflow.

Example prompt: Call POST /v1/ESimProfiles to order an esim profile., then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Twilio - Supersim 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 basic tokens manually.

Example prompt: Search Jentic for 'retrieve a list of billing periods for a super sim.', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /v1/Sims/{SimSid}/BillingPeriods | Retrieve a list of Billing Periods for a Super SIM. |
| POST | /v1/ESimProfiles | Order an eSIM Profile. |
| GET | /v1/ESimProfiles | Retrieve a list of eSIM Profiles. |
| GET | /v1/ESimProfiles/{Sid} | Fetch an eSIM Profile. |
| POST | /v1/Fleets | Create a Fleet |
| GET | /v1/Fleets | Retrieve a list of Fleets from your account. |
| POST | /v1/Fleets/{Sid} | Updates the given properties of a Super SIM Fleet instance from your account. |
| GET | /v1/Fleets/{Sid} | Fetch a Fleet instance from your account. |

## Key resources

- **SupersimV1BillingPeriod** — Operations related to SupersimV1BillingPeriod
- **SupersimV1EsimProfile** — Operations related to SupersimV1EsimProfile
- **SupersimV1Fleet** — Operations related to SupersimV1Fleet
- **SupersimV1IpCommand** — Operations related to SupersimV1IpCommand
- **SupersimV1Network** — Operations related to SupersimV1Network

## Why Jentic

- **Setup:** Wiring Twilio Super SIM by hand means setting up HTTP basic auth with your account SID and auth token against the supersim.twilio.com host and handling retries yourself. Through Jentic you install once, import Twilio Super SIM from the API Directory, store the account SID and auth token once, and your agent calls it.
- **Permission scoping:** Twilio Super SIM puts the SIM, fleet, and eSIM profile Sids in the URL path (/v1/Fleets/{Sid}), so a rule can pin your agent to one fleet or SIM. You choose the operations it may call, so writes like updating a fleet are not included unless you add them.
- **Credential handling:** Your Twilio account SID and auth token are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list billing periods for a SIM' or 'create a fleet', and Jentic returns the matching Twilio Super SIM operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the Twilio - Supersim use?

The Twilio - Supersim uses HTTP Basic authentication with username and password. 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 billing periods for a super sim. with the Twilio - Supersim?

Yes. Use the GET /v1/Sims/{SimSid}/BillingPeriods endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Twilio - Supersim?

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 billing periods for a super sim. 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 billing periods for a super sim.'. Jentic returns the matching Twilio - Supersim operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Twilio - Supersim have?

The Twilio - Supersim exposes 31 endpoints covering supersimv1billingperiod, supersimv1esimprofile, supersimv1fleet operations.

### Can I limit what my agent is allowed to do with the Twilio Super SIM API?

Yes. Jentic One is self-hosted by you, so your own rules decide which Super SIM operations and credentials the agent may use. Because the API puts the SIM, fleet, and eSIM profile Sids in the URL path, such as /v1/Fleets/{Sid}, you can pin the agent to a single fleet or SIM. You also choose which operations it may call, so write actions like updating a fleet via POST /v1/Fleets/{Sid} stay out of reach unless you explicitly allow them.