You know what's funny? Every single product we've built eventually needed SMS. Tenant.ph? Needs SMS for verification codes. Our accounting software? SMS for alerts. That random side project? You guessed it—SMS for notifications.
It's like that friend who shows up uninvited to every party. "Hey, can I stay here too?" And you're like, "Seriously? Again?"
So we did what any reasonable startup does when they need something repeatedly. We looked at buying an SMS service. How hard can it be, right? Just find a provider, pay them money, done. Spoiler: It wasn't that simple.
The prices were... let's say "creative." Some wanted arm and a leg. Others had complicated pricing tiers that required a PhD to understand. And don't get me started on the ones with hidden fees that pop up like surprise guests at a birthday party.
Then there was the integration headache. Every provider had their own special way of doing things. Some used REST, some SOAP, some apparently just used vibes. Documentation was either nonexistent or written in a language that seemed to be from another dimension.
And the reliability? Oh boy. We tested a few services and it was like playing Russian roulette with your notifications. Sometimes messages went through. Sometimes they didn't. And good luck figuring out why when things went wrong.
After a few weeks of this SMS provider dating game, I thought to myself: "You know what? Let's just build our own."
My initial reaction was: "Are you crazy? We're not an SMS company!"
But then it hit me—we were already building all these other products, and we're literally the exact users of our own products. What if we had ONE SMS service that EVERYTHING could use? We're basically dogfooding our own solution here. Not just for our current products, but for everything we'd build in the future?
It was one of those "wait, why didn't we think of this earlier" moments. Like when you realize you've been wearing your shirt inside out the whole day.
So we built UniSMS API. A simple, reliable SMS API specifically for Philippine developers. No complicated pricing. No hidden surprises. Just straightforward SMS that works.
Here's what we wanted:
- Simple API - Something a developer could understand in minutes, not days
- All networks covered - Globe, Smart, DITO, Sun, TNT - the whole gang
- Fair pricing - No minimum top-ups, pay as you go
- Reliable - Because nothing says "we don't know what we're doing" like failed SMS notifications
- Developer-friendly - SDKs for Python, Node, PHP, Ruby, and more
Now every product we build just plugs into UniSMS. No more shopping around. No more integration nightmares. It's like having a universal remote for all our SMS needs.
The best part? We're not just using it ourselves. Other developers and businesses in the Philippines can use it too! Because if we needed it, surely others are in the same boat.
So that's the story. We got tired of getting extorted by SMS providers, so we built our own. And honestly? It's kind of awesome. Now we control our own destiny, and our products never have to worry about "will the SMS go through today?"
If you're a developer in the Philippines building something that needs SMS, check out unismsapi.com. You can try it out for as low as ₱1. No credit card required!
And to all those SMS providers we "dated" before building our own—thanks for the inspiration. Category: "We could've just built it from the start."