An opinionated Postman collection for evaluating the Infobip APIs — 54 requests across 8 channels, in the order you'd actually test them, with the responses explained.
Unofficial. Not affiliated with or endorsed by Infobip. Endpoint shapes are derived from Infobip's public OpenAPI specification.
Infobip publishes an official Postman workspace, and you can import their OpenAPI spec directly to get all ~665 endpoints. Both are more complete than this. Neither is much fun to start with.
This collection is the opposite trade: a small curated slice, wired so that a first hour with the platform is mostly pressing Send.
- IDs chain automatically. A send captures
messageIdandbulkIdinto collection variables, so the delivery-report and log requests below it fire with no copy-paste. - Every request explains itself — what the call does, what to look for in the response, and the failure that usually bites first.
- Auth is set once, at collection level. Nothing to paste per request.
- Optional query parameters are pre-loaded but unchecked, so you tick them in the Params tab instead of going back to the docs.
- Free vs. billable is labelled, which matters on a trial account with ten free SMS.
- Import both files from
postman/into Postman. - Select the Infobip environment (top-right dropdown).
- Fill in the Current value column — never Initial value, which syncs to Postman's cloud:
baseUrl— your account's personal base URL, e.g.abc123.api.infobip.com(Infobip portal → Developers → API keys). The genericapi.infobip.comwill not authenticate.apiKey— from the same screen.testPhoneNumber— international format, no+, e.g.13035550123.
- Run 00 · Start here → Get account balance. A
200means you're wired up. - Run 00 · Start here → List my numbers to find out which senders your account actually has, and fill in
smsSenderaccordingly.
| Folder | Endpoints |
|---|---|
| 00 · Start here | balance, free-message allowance, owned numbers, number search |
| 01 · SMS | send (v3), preview, delivery reports, logs, inbound, scheduled bulks |
| 02 · WhatsApp | text, template, image, document, buttons, list, template listing |
| 03 · Email | send (v4), per-recipient placeholders, reports, logs, domains, address validation, suppressions |
| 04 · Voice | TTS single + advanced, voice listing, reports, Calls API |
| 05 · 2FA | application → message template → send PIN → verify (run in order) |
| 06 · Viber + RCS | send, capability check, reports, logs |
| 07 · Messages API | one endpoint for every channel, with cross-channel failover |
- Delivery reports are consumed on read.
GET /sms/3/reportsreturns each report exactly once. Use/sms/3/logswhen you want to look again. PENDINGis not a failure. A send returnsPENDING_ACCEPTED, meaning the platform accepted the message. The real outcome arrives later, in the report.- WhatsApp has a 24-hour window. Free-form messages only work inside a session the user opened by messaging you. Outside it, every send must be a pre-approved template.
- Email sender domains must be verified, or the send is rejected. Check with Get domains before debugging anything else.
- The base URL is per-account. Nearly every 401 is this or the API key.
- You can only message the phone number you verified at signup. Anything else returns
REJECTED_DESTINATION_NOT_REGISTERED. - Alphanumeric senders (
InfoSMS) don't work for US/Canada destinations — US carriers reject them. Check List my numbers: trial accounts are usually given a shared short code to send from instead. - Free allowances are small and per-channel — often around ten SMS against ninety-odd emails. Get balance + free messages shows what's left.
Free and non-sending: everything in 00 · Start here, all GET requests, plus Preview SMS, Validate a message, Validate an email address and Check RCS capability.
Spends credit and reaches a real handset: anything named Send or Make a call.
postman/Infobip.template.postman_environment.json is a blank template and is the only environment file in this repo. If you export your own filled-in environment, Postman includes the current values — API key included. The .gitignore excludes exported environments for this reason; keep it that way.
Verified against Infobip's public OpenAPI specification in September 2026, using the then-current API generations: SMS v3, Email v4, WhatsApp v1/v2, Messages API v1, 2FA v2, Viber v2, RCS v2, Numbers v1, Voice TTS v3 / Calls v1.
Infobip versions its endpoints, so older generations (/sms/2/text/advanced, /email/3/send) still work but aren't used here. If something in this collection 404s, check the current spec — the authority is always infobip.com/docs/api.
MIT — see LICENSE.