Key Takeaways
- Version your HTTP adapter and webhooks independently of APK or OSS panel releases.
- Pin schemas; do not scatter curl across services.
- Link the open-source hub; SaaS samples are REST, not a fake multi-language SDK.
- Idempotency and signatures are part of the version.
- Devices + volume pricing on SaaS; Free 1 device / 300 SMS lifetime; airtime yours.
Version the contract
Versioning integrations on open-source GitHub SMS gateways means owning an adapter module — not renaming the phone. Hub: open source. SaaS fields: Developer Center.
“If OTP and billing share an unversioned helper, the next ‘small payload tweak’ ships as an outage.”
Maturity
v0
Scattered curls
v1
One adapter
v2
Signed webhooks
v3
Idempotent OTP
What to version
| Layer | Version? | Why |
|---|---|---|
| HTTP send client | Yes | Contract services import |
| Webhook handler | Yes | Old consumers during rollout |
| OSS panel release | Canary | Not the same as adapter semver |
| Android APK | Canary | Radio client |
| Airtime / plan | No | Still your bill / meter |
OSS forks
Pin panel versions; read changelogs before upgrade. SaaS REST samples: PHP, C#.
Rollout
Feature-flag adapters; canary OTP; no dual retry loops.
Cost
Pricing— devices + volume; Free 1/300 lifetime.
Next steps
Related product pages
Jump to the live product docs for this topic—not another long-form article.
- SMS API documentationLive endpoint reference
- device and SMS volume pricingPlans and allowances
- Android SMS gateway product guideDefinition, product, and how to buy
- download the Android gateway appGet the APK




