Skip to content

Set up webhooks

Until Cloud has a screen for it, the Hablame team registers your endpoint on request. This is what you need to send and what you get back.

3 min read

What to send support

Email developers@hablame.co with these four items:

Never send us secrets

Not your full API key, an SMPP password or a signing secret. Your organization name is enough to identify your account.

Before you request registration

  • Your URL responds 2xx to a POST in less than 15 s.
  • Your code verifies the signature and drops duplicates. You can start from the example receivers.
  • The URL is not followed through redirects: it must be the final one. A 301 or 302 counts as a failure.

Your signing secret

When the endpoint is registered, you get its signing secret in Cloud: whsec_ followed by 48 hexadecimal characters. It is shown only once and cannot be retrieved again. Keep it in your secrets manager or an environment variable; never in code or in the browser. Each endpoint has its own.

After registration

  • Notifications can take up to 30 seconds to start arriving.
  • SMS that reached your short code before registration are not stored or delivered later. Request registration before you promote the short code.

Suspend, rotate or change the endpoint

Every change is requested the same way, at developers@hablame.co: suspending notifications, changing the URL or the short code, or rotating the secret.

Rotate without losing notifications

During the 24 hours after a rotation, each notification is signed twice: X-Hablame-Signature with the new secret and X-Hablame-Signature-Prev with the previous one. This lets you switch yours whenever it suits you. Verify signatures.

Need help?

Was this page helpful?

See all support channels

Your cookie preferences

You decide what we measure. You can change your choice at any time. Rejecting takes no feature away from the documentation.

Privacy policy