How to replace custom HTTP SMS gateway headers in Blesta

Skip to main content
Print

How to replace custom HTTP SMS gateway headers in Blesta

Update only the intended Custom HTTP Webhook gateway when its provider changes an authentication header or key. The provider credential, the saved gateway and the workflows selecting it are separate choices.

Prepare the replacement

Use the provider’s supported credential-replacement process and identify every application still using the old value. Obtain the new value through your normal credential-handling process. Do not revoke a shared key simply to investigate one failed message, or assume that editing this gateway updates another saved configuration.

Edit the intended gateway

  1. Open PD Modules → SMS Manager → Gateways and select the correct Custom HTTP Webhook configuration.
  2. Check its name, method and endpoint before changing authentication.
  3. Paste the complete replacement Extra headers, one Header: value entry per line.
  4. Retain the required non-authentication headers as well as the updated authentication entry, then save.

Extra headers use saved-secret handling: their previous value is not echoed into the edit form. Leaving that field blank keeps the saved headers; pasting a replacement replaces that saved header block. A blank-looking field is therefore not proof that authentication was removed.

Keep request fields distinct

Use an authentication header when the provider supports it. Credentials placed in Request URL or Request body are different configuration fields and do not acquire the header field’s masking behaviour. Check the provider’s required format rather than moving a credential between fields by guesswork.

Do not change From, recipient formatting or the success rule merely because the authentication value changed. Keep the scope of the edit clear so an unexpected result can be traced.

Check the result

Test connection does not validate this custom endpoint against the provider. An intended real test can send a text and incur charges. Review History and the provider’s response before retiring the old credential through the provider’s own process. Reconcile an Unknown result before another send, and keep credentials out of tickets and screenshots.

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

Table of Contents

Get your website online with PD Hosting

UK hosting, domains and support from a real team. From a first site to a full server.

Terms and Conditions  ·  Privacy Policy

PD Hosting is the trading name of Projektif Digital Ltd, registered in England and Wales, company number 12482555.

PD Hosting
Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.