...
List of Faults
| Table of Contents |
|---|
1 - 99 Server and Connection
Faults caused by the server being unavailable or not having access to necessary resources such as the Respax database.
...
6 - Database connection failed.
The API was unable to establish a connection to the database. This is a server side configuration error. Please contact the system administrator for assistance.
7-99 - Undefined.
100 - 199 User Authentication
In general these codes are used for any issues that prevent the user from logging in or performing a specific task. This can include password and permission errors as well as configuration issues with the organisations associated with the user.
...
199 - General user configuration error.
The user is not configured correctly for the API. As an example, the respax-external API requires the user to be configured as an agent.
200 - 299 General Data
Generic fault codes that can be used regardless of the type of data.
...
299 - Action not supported.
Although the method may have been called correctly, the API does not support manipulating the data specified.
300 - 399 Reservations
Faults returned when attempting to create or update a reservation.
...
331 - Payment currency error.
The base currency of one or more payments does not match the reservation currency.
332-399 - Undefined
400 - 499 Tour Content
Faults related to tour configurations and content.
...
450 - Invalid category root node.
The starting point for the tour categories is invalid or undefined.
451-499 - Undefined
500 - 599 Hop-On Hop-Off Itinerary
Fault codes related to manipulating hop-on hop-off itineraries.
...
505 - Sector already booked.
A reservation that is not cancelled already exists for one of the sectors specified.
506-599 - Undefined.
600 - 699 Gateway
Fault codes related to gateway interfaces for accessing multiple operators. (eg. RON)
...
699 - Unhandled or unassigned fault.
Used for faults from the gateway that are currently unhandled or do not have a specific fault code.
700 - 799 Communication
Fault codes related to attempts by the API to communicate externally on behalf of the caller. (eg. failed emails)
...
701 - Invalid email address.
An attempt was made to send an email to an invalid address.
Reserved by the XML-RPC Specification for Fault Code Interoperability
| Code Block |
|---|
See: http://xmlrpc-epi.sourceforge.net/specs/rfc.fault_codes.php |
...