Connect your own Infobip account
A full-stack CPaaS with standout coverage across the Middle East, Africa and Southeast Europe — the regions where the big two are often routed through aggregators.
What you need from Infobip
Gather these in the Infobip portal first. The connection form asks for exactly these fields and nothing more.
| Field | What it is |
|---|---|
| apiKey | API Key. A single key; no paired secret. |
Credentials are sealed with AES-256-GCM and the console only ever shows a masked value afterwards. Plaintext is never written to logs and never sent back to the browser.
What we configure on the connection
- Base URL. Infobip gives every account its own API host, so this is required.
- Sender identities. Numbers or alphanumeric sender IDs.
- Default send pacing: 30 messages per second. This is a conservative starting point, applied per connection, and you can change it at any time. Your real ceiling is set by Infobip — check your account quota and raise the value to match.
- Base URL is required. Infobip issues a per-account API host; the connection will not work with a guessed regional hostname.
Why teams pick Infobip
- Strong direct coverage in the Middle East, Africa and Southeast Europe
- Single-key credentials — the simplest connection to set up
- Per-account API host, so traffic never shares an endpoint with other tenants
Worth knowing
- Your account-specific Base URL is mandatory. Copy it from the Infobip portal rather than guessing a regional hostname.
What stays on your side
These are yours to hold — and that is the point of bringing your own account: the relationship, the rates and the compliance stay in your name, not ours.
- Account approval, credit checks and arrears
- Sender ID, number and short-code registration for each destination
- Local telecom and privacy compliance in the countries you send to, including opt-out rules
- The quotas and rate limits Infobip grants your account
Next
Whaleal Messaging currently offers self-service connections to 6 SMS providers. Underlying the SMS channel is an adapter library covering 33 providers; the ones outside this list are unlocked on request rather than self-service.