What it checks
Every finding names the field, says what is wrong, and where the API rejects it, gives the response
you would get back — for example
invalid type with status 700.
It also catches two mistakes that look valid:
- Long IDs sent as numbers. A 19-digit DLT template ID written without quotes is rounded by any JavaScript that parses the JSON on its way to OneXtel, such as a browser, a Node service or a no-code tool. Quote every ID.
- Numbers that cannot receive.
/send_smsaccepts and bills a recipient that is not a real mobile number. The validator flags anything outside the 6–9 mobile series.
What it cannot check
Some rejections depend on your account, so only a real send reveals them:- whether the template is approved, and approved for this sender
- whether the message body matches the registered DLT template word for word
- whether the sender ID, entity ID and template belong to your API key
- your balance and sending limits

