Nvia Technical Guides
SMS API Wiki 1.0
SMS API Wiki 1.0VMS API Wiki 3.0Number Lookup Services Wiki 1.0
SMS API Wiki 1.0
SMS API Wiki 1.0VMS API Wiki 3.0Number Lookup Services Wiki 1.0
  • Basics
    • Glossary
  • 1. Sending SMS-MT
    • 1.1 Interfaces
      • 1.1.1 HTTP Request
        • Sending text, flash and binary messages
        • Sending WAP push messages
      • 1.1.2 JSON Request
        • Sending text, flash and binary messages
        • Sending WAP push messages
      • 1.1.3 Webservices
        • Sending text, flash and binary messages
        • Sending WAP push messages
      • 1.1.4 SMPP interface
        • About the SMPP interface
        • Date time formats for scheduled delivery and validity period
    • 1.2 Date time formats
    • 1.3 Error Codes
    • 1.4 Delivery Report Callback
  • 2. SMS - 2 Ways
    • 2.1 Sonic MQ
    • 2.2 HTTP with Content-Reply (Synchronous)
    • 2.3 HTTP (2 requests)
    • 2.4 Unanswered messages
    • 2.5 Delivery reports (DLR)
  • 3. SMS Certified by Blockchain
    • 3.1 SMS Certified by Blockchain
    • 3.2 Sending a SMS certified by blockchain
  • EXAMPLES
    • GitHub sendMtSms
Powered by GitBook
On this page
  1. 1. Sending SMS-MT

1.3 Error Codes

The Nvia Platform may return a numeric error code as a response to a HTTP request (such as sending an MT). This will occur if something prevents the Nvia Platform from fulfilling the request. The error code will always be presented in the following format:

If such an error occurs, the partner may use the numeric Identifier of the error, to detect the error.

ERROR CODE
DESCRIPTION

0

Internal error

2

Throughput exceeded

3

Blocked account (please contact your account manager)

4

Incorrect username and/or password

5

Syntax error

6

Unsupported operation

7

Deleted account

10

Internal error