This section of the website is supply the detailed information about each error code return that you could receive when making method calls.
For each return code there is a specification and details of why it occurs. There is also an example of the return code XML format for reference.
Each return code will contain different information but the XML format that is returned is the same for each error code. Below is a table of all error
return codes that you may encounter while using XML-3.
Return Code |
Description |
Reason |
1 |
Internal Error has occured! We appologise for any issues this has caused you. We are doing all we can to recify this issue. |
This will occur when our internal systems have encountered an issue. We are internally notified when this happens and will work as fast as possible to fix the problem. |
2 |
Username Invalid! Please try again! |
You have supplied a username and account number combination that does not exists. |
3 |
Password Invalid! Password are case sensitive. |
The password you have supplied when trying to login is not the same as on file. |
4 |
Session Ticket has Expired! Please login again to aquire a new ticket. |
The session ticket you have provided has expired and a new ticket needs to be obtained by the Login method. |
5 |
Method Execution Not Authorised! You are not authorised to execute this method. Please contact your account manager for further assistance. |
You have tried to execute a method you are not authorised to execute. This can be rectified by contacting your account manager. |
6 |
Method Usage Exceeded! You have exceeded allowed the maximum time between requests of this method. |
Some methods have limits as to how often they can be called by each account. This message is returned if the limit has been exceeded. |
7 |
Session Tickets do not match! You have supplied a session ticket that does not match the currently active session ticket for the current user. |
When a request is made passing a session ticket, we authenticate the ticket against the user making the request. If the currently active ticket does not match the one supplied, this error is returned. |
8 |
No Inventory table supplied! You have not supplied the [Item] table with any items to validate. |
This will occur if the XML schema is validated as incorrect or the items table is empty in the 'ValidateOrderInventory' methods request. |
9 |
XML Format Incorrect! You have supplied and [Item] table in the incorrect format. All column names are case sensitive and all data types must be as specified. |
This will occur if the column names or XML format is incorrect in the 'ValidateOrderInventory' method request |
10 |
Invalid Item! You have supplied either a VIP SKU or an EAN that was not recognised. |
This will be returned if you do not supply either a valid EAN or VIP product code. |
11 |
No Order Data supplied! You have not supplied the Order or Items table with any data. |
This will occur if the XML schema format is incorrect or there is no data when making a request to the 'PlaceOrders' method. |
12 |
XML Format Incorrect! You have supplied and [Order] table in the incorrect format. All column names are case sensitive and all data types must be as specified. |
This will occur if the column names or XML format is incorrect in the 'PlaceOrders' method request for the Order table. |
13 |
XML Format Incorrect! You have supplied and [Items] table for the orders in the incorrect format. All column names are case sensitive and all data types must be as specified. |
This will occur if the column names or XML format is incorrect in the 'PlaceOrders' method request for the Items table. |
Below is the XML schema definition for the Error Code Return and an example XML file.
Field |
Description |
Type |
Table |
Dataset |
ErrorCode |
The unique code for the error return. |
Integer |
Error |
Errors |
ErrorDescription |
The description for the returned code. |
String |
Error |
Errors |