Skip to main content
The only genuinely free pre-flight check on the API.
The cost is unit_rate × submit_sm_count.

Parameters

submit_sm_count is the segment count

This is how you find out that a message you thought was one is actually three — before you pay for it.
Call this on user-generated content before sending it. One curly apostrophe ’ forces the whole message to UCS-2 and triples the segment count, and nothing in the send path flags it — the message goes out correctly, just three times more expensively.

It costs nothing

  • Sends nothing.
  • Charges nothing.
  • Counts against no rate limit — so it will not consume the throughput you need for real sends.

Rates always show four decimal places

Unlike a total, which honours smsg.money.scale, a rate keeps four places whatever that is set to.
0.0450 shown as 0.05 is 11% out on every message, and a customer computing their bill from a quote would be wrong. CSV exports keep four for the same reason — a spreadsheet sums that column.

Errors particular to this endpoint

The product allow list is the same one a send uses, deliberately — a quote and a send cannot disagree about what you may name.

What it cannot tell you

  • Whether the message would be accepted. Sender-ID approval, template matching and credit are all checked at send time, not here.
  • Whether it would be delivered. That is a receipt.

Encoding and segments

Why the same text costs different amounts.

Check your balance

What is left to spend.