Error Messages 1.1

From Aviberry API

Jump to: navigation, search

Contents
Still have a question?



Error codes are the same for JSON-RPC and XML-RPC protocol calls.

Code Description
-32768 .. -32000 Protocol errors.
0 No error, output is available for using.
1 .. 32000 Application errors.

Contents

Protocol errors

Code Description
-32700 Parse error.
-32600 Invalid request.
-32601 Method not found.
-32602 Invalid parameters.
-32000 Internal error.

Application errors

Below you will find general description of application errors. In actual fact, many error messages are more detailed and specify why they occured. For example, for error message 7 or 8 in error message it is specified which file does or does not exist.

Code Description
1 Unauthorized API access.
2 Invalid parameter.
3 Account is not active.
4 Limit exceeded.
5 Traffic exceeded.
6 Invalid output format.
7 File does not exist.
8 File already exists.
9 Unauthorized file access.
10 Invalid login/password.
11 Callback error.
12 File upload error.
13 Converter error.
14 File download error.
15 Unknown optional parameter.
16 Unknown file size.
17 File size limit exceeded.
18 Task size limit exceeded.
32000 Internal error.

Examples

JSON-RPC

{ "version": "1.1", "error": { "name": "JSONRPCError", "class": "UnauthorizedAccess_ApiException", "code": 1, "message": "Unauthorized access." } }

XML-RPC

<methodResponse> <fault> <value> <struct> <member> <name>faultClass</name> <value> <int>UnauthorizedAccess_ApiException</int> </value> </member> <member> <name>faultCode</name> <value> <int>1</int> </value> </member> <member> <name>faultString</name> <value>Unauthorized access.</value> </member> </struct> </value> </fault> </methodResponse>



К содержанию
Возникли вопросы?




Contents
Still have a question?

Views
Personal tools