Knowledge base

Android SMS Gateway webhooks: Setup

Featured illustration for Android SMS Gateway webhooks: Setup

Android SMS Gateway webhooks — setup. Feature deep dive on webhooks (setup). Unique examples and failure modes; link matching /features path when exists. Priced by devices and SMS send volume; BYO phone and operator credit.

Written by the SMS Gateway team for operators who run phones and airtime themselves — not for theoretical cloud SMS demos.

InformationAndroid SMS GatewayFeaturesOperations
Article
Published
March 24, 2025
Updated
April 19, 2025
Reading time
16 minute read

Key Takeaways

  • android sms gateway webhooks setup is POST /webhooks, HTTPS URL, signature headers, and an idempotent handler.
  • Prefer webhooks over polling GET /messages/{id} in production. DLR still depends on the carrier path.
  • Verify X-SmsGateway-Signature as documented. Do not skip “just in staging” that later ships.
  • message.delivered / message.failed / message.received / ussd.response — subscribe to what you handle.
  • Priced by devices and SMS send volume. You use your own phone and operator SMS credit. Webhooks do not include operator airtime.
  • Live event names: Developer Center OpenAPI webhooks key.

Register with POST /webhooks

Search intent for android sms gateway webhooks setup is wiring DLR and inbound events into your backend. Service pricing is based on device count and total SMS sent through the gateway. Register an HTTPS URL. Events are listed under the OpenAPI webhooks key — do not invent names.

A webhook you never signature-check is an unauthenticated write API you published to the internet.

Product: SMS webhook integration. Docs: docs.sms-gateway.app. Samples are REST, not a packaged SDK.

Events you actually need

EventUseSkip if
message.deliveredMark OTP/order delivered in your appYou only poll and accept staleness
message.failedPage on-call; do not infinite-retry MMSYou ignore radio death
message.receivedTwo-way inbox → ticketNo human owns replies
ussd.responseBalance check finishedYou never POST /ussd

DLR depth: delivery reports. Inbox: two-way inbox. USSD: USSD overview.

Verify signatures

X-SmsGateway-Signature = v1=hex(HMAC-SHA256("{timestamp}.{body}", secret)). Timestamp header is unix seconds. Deduplicate on X-SmsGateway-Event-Id. Keep the secret in env — API keys in env. OWASP webhook verification notes are a useful floor (do not log secrets).

HTTPS callbacks only

Local-panel TLS: reverse proxy and HTTPS. Do not point production at an ngrok you forgot. Priced by devices and SMS send volume. You use your own phone and operator SMS credit.

Idempotency on event id

Carriers and retries will duplicate. Store event ids. Do not send a second OTP because delivered fired twice. OTP isolation: OTP verification. Setup phones: device setup.

Webhook setup checklist

  • POST /webhooks with HTTPS URL.
  • Signature + timestamp verified.
  • Event-id dedupe.
  • Handler fast; work async.
  • Staff canary send → delivered/failed observed.

Next steps

Register, canary, then subscribe production events. Pricing. App: downloads.

Related product pages

Jump to the live product docs for this topic—not another long-form article.

FAQ

Frequently asked questions

Direct answers about android sms gateway webhooks.

Where do I register a webhook?

POST https://app.sms-gateway.app/api/v1/webhooks with Bearer auth. Live schema: https://docs.sms-gateway.app/.

How is the body signed?

X-SmsGateway-Signature = v1=hex(HMAC-SHA256("{timestamp}.{body}", secret)). Timestamp is X-SmsGateway-Timestamp. Deduplicate on X-SmsGateway-Event-Id.

Can the callback be HTTP?

Use HTTPS. HTTP callbacks leak and fail audits. Signature checks still required.

Does this include carrier credit?

No. Android + operator SMS credit. Platform meters devices and volume.

Free canary?

300 SMS lifetime on one device — enough to fire a delivered/failed event to a staff URL.
Keep learning

Related articles

Topically related guides—chosen by subject overlap, not a fixed sitewide footer.

Information
android sms gateway auto reply

Android SMS Gateway auto-reply and STOP: Setup

Android SMS Gateway auto reply and stop — reply and STOP-setup. Feature deep dive on auto-reply and STOP (setup). Unique examples and failure modes; link matching /features path when exists. Priced by devices and SMS send volume; BYO phone and operator credit.

Oct 9, 202516 min
Read article
Information
android sms gateway bulk csv

Android SMS Gateway bulk CSV import: Setup

Android SMS Gateway bulk csv import — setup. Feature deep dive on bulk CSV import (setup). Unique examples and failure modes; link matching /features path when exists. Priced by devices and SMS send volume; BYO phone and operator credit.

May 29, 202616 min
Read article
Information
android sms gateway contacts

Android SMS Gateway contact lists: Setup

Android SMS Gateway contact lists — setup. Feature deep dive on contact lists (setup). Unique examples and failure modes; link matching /features path when exists. Priced by devices and SMS send volume; BYO phone and operator credit.

Aug 3, 202516 min
Read article
Information
android sms gateway delivery reports

Android SMS Gateway delivery reports: Setup

Android SMS Gateway delivery reports — setup. Feature deep dive on delivery reports (setup). Unique examples and failure modes; link matching /features path when exists. Priced by devices and SMS send volume; BYO phone and operator credit.

Jun 17, 202616 min
Read article

Browse the full Android SMS gateway knowledge base or return to how an Android SMS gateway works.

Get started

Test the gateway on your own Android phone

Install the app, pair one device, and validate your API flow before choosing a paid plan.

You supply the phone, SIM, and operator SMS credit.

Download the Android appView pricing