Getting your Twilio credentials

REDA Connect authenticates to Twilio with exactly three values: your Account SID, an API key SID, and that key's Secret. This article shows where each one lives in the Twilio console, how to create the API key (its Secret is shown once, so this is the step people get wrong), and which REDA Connect field each value will go into. Collect all three now — the next article uses them.

The three values and where they land in REDA Connect

You'll do the actual entering in Creating the SMS Connect Account — this article is only about collecting the values safely.

Step 1 — Copy your Account SID

The Account SID is your Twilio account's public identifier. It is not a secret, but REDA Connect needs it in two places, so copy it exactly.

1. Log in at console.twilio.com.
2. On the console home page, find the Account Info panel — it shows Account SID, Auth Token, and your Twilio phone number.
3. Click the copy icon next to Account SID and save the value. It always starts with AC.

Expected result: you have a 34-character value starting with AC saved in your notes.

Your Account SID (always starting AC) in Admin → Account management → General settings. Copy it exactly — it goes into the endpoint address on your Connect Account.

Step 2 — Create a Standard API key

An API key is a separate credential that acts on behalf of your account. You create one specifically for REDA Connect:

1. In the Twilio console, go to Twilio Console → Settings → API keys & tokens.
2. Click Create API key.
3. Fill in the form:
   • Friendly name: something you'll recognise later, e.g. REDA Connect SMS.
   • Key type: Standard. (A Standard key can send and receive messages but cannot manage your account or other keys — exactly the level of access REDA Connect needs. Do not pick Restricted or Main.)
4. Click Create / Next.

Expected result: Twilio shows the new key's SID (starts with SK) and its Secret — this is the only time the Secret is ever displayed.

1. Copy both values into your secure notes now. Twilio makes you tick a Got it! checkbox confirming you saved the Secret before you can click Finish.

Keys & Credentials → API keys & tokens — click Create API key, keep type Standard. The key's SID stays visible afterwards, but the Secret is shown only once at creation: copy it immediately.

Why an API key instead of the Auth Token?

Technically, Twilio accepts either your Account SID + Auth Token or an API key SID + Secret for sending messages, and REDA Connect's credential fields would hold either pair. Use the API key:

• Independent rotation. A dedicated API key can be replaced without changing the account Auth Token. Create, update and test the replacement before revoking the old key where appropriate; deleting a key still in use causes failed calls.
• Scoped. A Standard key cannot change account settings or create other keys; the Auth Token can do everything.
• Auditable. A key named REDA Connect SMS tells you what it's for. Auth Token usage is anonymous.

Keep-safe rules

• Store all three values in a password manager, not in email, chat, or a shared spreadsheet.
• The Secret is the sensitive one — treat it like a password.
• Once entered into REDA Connect, the key and secret are stored encrypted and can only be changed through the Update SMS API Tokens action — you will never read them back out of Salesforce, so your password manager copy is the reference copy.
• Never paste any of these values into a support ticket or screenshot. When REDA support needs to see your setup, they need the field names, not the values.

FAQ

Where to go next

• Creating the SMS Connect Account — enter the three values into REDA Connect, field by field.
• Updating your API tokens safely — how credential storage works in REDA Connect and how to rotate values later.