BhashSMS Test Console

Configure real request parameters, preview the exact URL, and fire test sends.

your credentials, your config
Ch·1 — GETSMS API
Ch·2 — GETWhatsApp API
Ch·3 — GETRCS API

Request Parameters

6-char DLT-registered header, linked to the template below.
With or without the 91 country code. Comma-separate for multiple numbers (each will be sent as a separate test).
stype = normal  ·  fixed for the SMS API

Test Log

No test sends logged yet — they'll appear here after you hit "Send test".
SMS response reference
Response stringMeaning
success:1701XXXXXXXXXAccepted — the number is the message ID for tracking.
failure:invaliduserWrong username or password.
failure:invalidsenderSender ID not registered / not DLT-approved.
failure:invalidtemplateText doesn't match an approved DLT template exactly.
failure:insufficientcreditsAccount balance too low.
failure:invalidphoneMobile number format is incorrect.
failure:spamdetectedFlagged — usually a template mismatch.
WhatsApp response reference
The endpoint returns plain text: a numeric message ID (or the word "sent") on success, or a plain error string such as an invalid-user or low-balance message on failure. There's no fixed error-code table for this API — read the exact text of the response you get back.
RCS response & media reference

A successful call returns s.<random_number> — e.g. s.898746 — where the number is a message/ticket ID for delivery tracking. Anything else in the response is an error string to read directly.

htype valueRenders as
imageSingle image card (jpg / png)
videoPlayable video card (mp4)
documentDownloadable document card — pair with a display file name
carouselMultiple swipeable cards — comma-separate each media URL
This page runs entirely in your browser — nothing you enter here is sent anywhere except the BhashSMS request you choose to fire. Saved values are stored in this browser's local storage on your device only.