Create a Standard API Key for Praxi

Praxi connects to your Twilio account using a Standard API Key — not your root Auth Token. Standard keys are scoped, named, individually revocable and auditable; they're the recommended path for any third-party integration.

The BYO connect form validates the format of what you paste: the Account SID must be AC followed by 32 hex characters, and the API Key SID SK followed by 32 hex characters. Praxi cannot tell a Standard key from a Main key — choosing Standard when you create the key in the Twilio Console is up to you.

Create the key

1. Sign in to the Twilio Console.
2. In the top-right account menu, choose Account → API Keys & Tokens, or open it directly: console.twilio.com/us1/account/keys-credentials/api-keys.
3. Click Create API Key in the API Keys table.
4. Friendly name: enter something memorable — for example Praxi production (Banksia Psychology). Twilio shows this name in the audit trail every time the key is used.
5. Region: pick Australia (au1). This must match the region you'll later select in Praxi's BYO form.
6. Key type: choose Standard. Do not pick Main — Main keys carry subaccount-management privileges Praxi does not need.
7. Click Create API Key.

Save the Secret before closing the dialog

Twilio shows the API Key Secret only once, in the dialog that appears immediately after creation. You cannot recover it later — if you lose it, you'll need to delete the key and create a new one.

Copy all three values somewhere safe:

Field	Where to find it	Format
Account SID	Console homepage / Account tab	AC + 32 hex chars
API Key SID	The new key's row in the table	SK + 32 hex chars
API Key Secret	The creation dialog (one-shot)	Random 32+ chars

A password manager entry is ideal. Avoid pasting them into chat tools or email.

What Praxi does with the key

When you submit the BYO connect form, Praxi:

1. Validates the SID/Secret pair against the Twilio API.
2. Encrypts the Secret with AES-256-GCM and stores it in your tenant database.
3. Uses the key on every outbound Twilio API call (numbers, recordings, softphone tokens). The key is never sent to the browser.

If the key is ever revoked (in Twilio Console) or rotated, the next Praxi operation will fail with an authentication error, and the banner on the Phone Agent settings page flags the connection as needing re-validation once it hasn't been validated for 24 hours. See Troubleshooting for recovery.

Rotating the key

Best practice is to rotate the API Key every 90 days:

1. Create a new Standard API Key (steps above).
2. Connect Praxi using the new SID/Secret. The BYO form replaces the stored credentials.
3. Verify a test call works.
4. Revoke the old key in the Twilio Console.

If you need to revoke the key immediately (e.g. a staff member leaves and you suspect they have access to the secret), revoke first then re-issue. Practice Phone will return errors until you connect a fresh key.