One endpoint.
Three different problems.
Every message on this page is the same POST /v1/messages call. What differs is the constraint that decides whether the feature works: whether you can observe delivery, what the body costs once segments are counted, and who else can make it fire.
Four questions that
decide the design.
Answer these before writing the integration. Each one changes the code, and three of them change the cost.
If the answer is yes, read delivery status before you design anything. Nishchit reports what the network reported and nothing more, and on the primary route that is unknown, permanently.
One Bangla character switches the whole message to UCS-2 and cuts the segment from 160 characters to 70. Measure the real template in the segment calculator before you price the feature.
A retry, a double tap, a redelivered queue message. An Idempotency-Key makes the duplicate a no-op that returns the original response. Idempotency semantics
Anything a logged-out user can cause is an abuse surface. Trust tiers cap daily volume independently of the credit balance, so a leaked key cannot drain an account overnight. Trust tiers and ceilings
Your product has something to say.
Give it a reliable way to say it.
Self-serve signup, live immediately. Content checked instead of paperwork.
One credit per segment at ৳0.50. No contract, no monthly minimum, no expiry.
An nk_test_ key never reaches a carrier or spends a credit.
One country, done properly — Bangla pricing, observable delivery.