canonical: https://jentic.com/apis/twilio.com/twilio---accounts # Twilio - Accounts This is the public Twilio REST API. The API exposes 18 endpoints secured with basic authentication. ## For AI agents Programmatically promote the secondary auth token to primary. after promoting the new token, all , create a new aws credential. Covers 18 operations with basic authentication. ## Scope Does not handle payments, communications, or crm - use for developer tools only. ## Capabilities - Promote the secondary Auth Token to primary. After promoting the new token, all - Create a new AWS Credential - Retrieves a collection of AWS Credentials belonging to the account used to make - Modify the properties of a given Account - Fetch the AWS credentials specified by the provided Credential Sid - Delete a Credential from your account ## Use cases ### Developer Tools Operations Use the Twilio - Accounts to perform developer tools operations programmatically. The API provides 18 endpoints covering core functionality including promote the secondary auth token to primary. after promoting the new token, all , create a new aws credential, retrieves a collection of aws credentials belonging to the account used to make . Example prompt: Call POST /v1/AuthTokens/Promote to promote the secondary auth token to primary. after promoting the new token, all ### Automated AccountsV1AuthTokenPromotion Management Automate accountsv1authtokenpromotion operations by combining multiple Twilio - Accounts endpoints. Agents can create a new aws credential and then retrieves a collection of aws credentials belonging to the account used to make in a single workflow. Example prompt: Call POST /v1/Credentials/AWS to create a new aws credential, then verify the result ### AI Agent Integration via Jentic AI agents discover and call Twilio - Accounts 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 'promote the secondary auth token to primary. after promoting the new token, all ', load the operation schema, and execute with Jentic-managed credentials ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | /v1/AuthTokens/Promote | Promote the secondary Auth Token to primary. After promoting the new token, all | | POST | /v1/Credentials/AWS | Create a new AWS Credential | | GET | /v1/Credentials/AWS | Retrieves a collection of AWS Credentials belonging to the account used to make | | POST | /v1/Credentials/AWS/{Sid} | Modify the properties of a given Account | | GET | /v1/Credentials/AWS/{Sid} | Fetch the AWS credentials specified by the provided Credential Sid | | DELETE | /v1/Credentials/AWS/{Sid} | Delete a Credential from your account | | POST | /v1/Credentials/PublicKeys | Create a new Public Key Credential | | GET | /v1/Credentials/PublicKeys | Retrieves a collection of Public Key Credentials belonging to the account used t | ## Key resources - **AccountsV1AuthTokenPromotion** — Operations related to AccountsV1AuthTokenPromotion - **AccountsV1Aws** — Operations related to AccountsV1Aws - **AccountsV1BulkConsents** — Operations related to AccountsV1BulkConsents - **AccountsV1BulkContacts** — Operations related to AccountsV1BulkContacts - **AccountsV1PublicKey** — Operations related to AccountsV1PublicKey ## Why Jentic - **Setup:** Wiring Twilio - Accounts by hand means learning its basic auth with Account SID and Auth Token, pointing at the accounts.twilio.com host, and handling errors and retries yourself. Through Jentic you install once, import Twilio - Accounts from the API Directory, store the credentials once, and your agent calls it. - **Permission scoping:** Twilio - Accounts puts the credential SID in the URL path (/v1/Credentials/AWS/{Sid}), so a rule can pin your agent to one credential: it can read or update that credential and nothing else. You choose the operations it may call, so deleting a credential or promoting an auth token 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 AWS credentials' or 'promote the secondary auth token', and Jentic returns the matching Twilio - Accounts 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 - Accounts use? The Twilio - Accounts 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 promote the secondary auth token to primary. after promoting the new token, all with the Twilio - Accounts? Yes. Use the POST /v1/AuthTokens/Promote endpoint. The API returns structured JSON responses that agents can parse and act on directly. ### What are the rate limits for the Twilio - Accounts? 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 promote the secondary auth token to primary. after promoting the new token, all through Jentic? Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'promote the secondary auth token to primary. after promoting the new token, all '. Jentic returns the matching Twilio - Accounts operation with its input schema. Load the schema and execute the call - credentials are injected automatically. ### How many endpoints does the Twilio - Accounts have? The Twilio - Accounts exposes 18 endpoints covering accountsv1authtokenpromotion, accountsv1aws, accountsv1bulkconsents operations. ### Can I limit what my agent is allowed to do with the Twilio Accounts API? Yes. Because you run Jentic One yourself, self-hosted, your own rules decide which Twilio Accounts operations and credentials your agent may use. Since the credential SID sits in the URL path (/v1/Credentials/AWS/{Sid}), you can pin the agent to a single credential so it only reads or updates that one and nothing else. You also pick the exact operations it can call, so promoting an auth token or deleting a credential stay off-limits unless you explicitly allow them.