Replace the credential on the intended PD Twilio SMS gateway when moving to a dedicated API key or rotating an existing one. Keep the Account SID and sender routing under review so this change does not accidentally select a different account or service.

Prepare the replacement

Have the Twilio account administrator create an appropriate replacement key for the same account and API region. Twilio shows a new key’s secret when it is created; store it securely. An API Key SID beginning `SK` is not itself the secret.

Use a dedicated key for this integration where practical. Replacing the account’s Auth Token can affect other applications that use it, while a dedicated API key has its own lifecycle. Follow Twilio’s key setup guidance and check the permissions needed for message creation and the module’s connection read.

Update the saved gateway

1. Open PD Modules → Twilio SMS → Gateways and configure the intended gateway.
2. Confirm Account SID, From and the gateway label before changing credentials.
3. Select API Key (recommended by Twilio) under Authenticate with.
4. Enter the replacement API Key SID and matching API Key Secret. Use the saved secret field’s replacement control where offered.
5. Choose Save gateway, then Test connection.

Do not assume a masked or saved secret field contains the new value merely because the key identifier changed. Check that both values were replaced and saved together. Never paste the secret into a screenshot or support request to prove the change.

Confirm operation before retiring the old key

The connection read checks authentication for that operation; sending permission and sender eligibility are separate. Review normal operation through the intended gateway, or make a deliberately approved real test. A Log only rehearsal cannot validate a Twilio credential because it makes no Twilio request.

Retire the old dedicated key only after confirming the intended transition and whether anything else still uses it. Do not revoke a shared credential as a troubleshooting shortcut. Preserve an uncertain send’s provider reference and investigate it before repeating the text. If the new key is refused, keep the redacted error and have the account administrator review its account, region and permissions.

Check the replacement credentials

Compare the gateway-save result and connection read with the intended account and replacement credential. Check that both replacement values were saved, that the account matches and that the key uses the default Twilio API region. A successful message-list read does not prove message creation is permitted. Keep an Unknown send under review instead of rotating repeatedly or sending again to diagnose it.

See the PD Twilio SMS Blesta guide for related tasks, or explore PD Twilio SMS.