Bangalore
Bulk SMS and WhatsApp API for Bangalore startups
Bangalore teams do not want an account manager and a PDF rate card. They want an API key, a docs page and a webhook that fires. BrookTel is self-serve by default: generate keys yourself, read the public API reference before you sign up, and only talk to a human when you actually want volume pricing.
Built the way engineers expect
- Public API documentation at /api-docs — readable before you create an account
- Self-serve API key generation and revocation, no support ticket to rotate a leaked key
- REST over HTTPS with JSON bodies and sane HTTP status codes
- Delivery webhooks instead of polling
- Idempotent sends so a retry does not double-charge or double-deliver
- Per-message failure reasons, so your on-call engineer can diagnose without emailing us
The two messaging problems startups hit
The first is OTP delivery at signup. A code that takes fifteen seconds is a conversion leak you will see in your funnel and misattribute to UX. Transactional DLT routing and sub-3-second delivery is the fix.
The second is DLT compliance discovered late — usually two days before launch, when someone realises SMS to Indian numbers needs a registered entity, header and template. That process is measured in working days, not hours, and it is the single most common reason Indian launches slip.
- Start DLT registration before you need it, not when you are blocked
- WhatsApp needs no DLT, so it is a viable interim channel while SMS approvals land
- Template variable and category mistakes are validated pre-submission, not discovered in production
Pricing that survives a finance review
Three separable lines means your unit economics are computable. A single bundled per-message figure means they are not.
| Line item | Billed by | Scales with |
|---|---|---|
| Platform plan | BrookTel, ₹0-₹999/month standard | Features and seats, not volume |
| SMS delivery | BrookTel prepaid wallet | Per message, rate by monthly volume |
| WhatsApp delivery | Meta, directly to your Meta account | Meta's published per-message rates |
Typical stack integrations
- Node.js, Python, Go, Java, PHP, Laravel, Ruby — plain HTTP, no SDK required
- Queue-driven sends with retry and backoff
- Webhook consumers behind your existing event bus
- WhatsApp as an authentication and support channel alongside SMS
Frequently asked questions
Can I integrate without talking to sales?
Yes. Sign up, generate an API key, and send. The API reference is public at /api-docs. You only need a conversation if you want a volume-based SMS rate or a Custom plan.
Do you have a sandbox?
You can test on the Free Launch plan by sending to your own number. Because template matching is validated before submission, most integration bugs surface as an explicit 4xx rather than a burnt message credit.
How do you handle rate limits and bursts?
Throughput is set against your plan and expected volume. If you have a launch or a scheduled fan-out coming, tell us the numbers ahead of time and we will size it rather than have you discover a ceiling in production.
Are you based in Bangalore?
No — we are in Chennai, under Paybrook Payments Tech Private Limited. Everything is self-serve and online, and support runs on Indian business hours.