DropPay API - Common Errors¶

DropPay POS API is built around REST paradigm so HTTP Status code are consistently informing about what happened running your request.

Failure conditions are classified by status codes and detailed with a special JSON payload

Error Info payload¶

{
  "code": "100",
  "description": "Missing arguments"
}

Within each status code code and context, property's value begins from 00 and can count until 99.

Failure responses starting missing Content-Type header like this

Generic failure status¶

    HTTP/1.1 400 Bad Request
    ...

On the other hand, failure responses which reports a detailed

Detailed failure status¶

    HTTP/1.1 400 Bad Request
    Content-Type: application/json
    ...

are expected to present a HTTP body filled with the Error Info payload as shown a above.

ErrorInfo can contain addictional properties when relevant in the called API working scope. In that case the specific differences are described in the API's dedicated page of these docs.

Here below common errors in global context 100 are classified under their corresponding HTTP Statuses. Similar nested lists are available for specific API doc pages.