Standard errors
The following is a list of standard errors that may be returned by the API regardless of the specific method being called.
Number | Name | Description |
---|---|---|
1 | Unknown method | Returned if the server was asked to dispatch a method it didn’t know about. |
2 | Invalid return payload | This error is actually generated by the client, not server, code, but signifies that a server returned something it couldn’t understand. A more detailed error report is sometimes added onto the end of the phrase above. |
3 | Incorrect parameters | Generated when the server has signature(s) defined for a method, and the parameters passed by the client do not match any of signatures. |
4 | Can’t introspect: method unknown | Generated by the builtin system.* methods when any kind of introspection is attempted on a method undefined by the server. |
5 | Didn’t receive 200 OK from remote server | Generated by the client when a remote server doesn’t return HTTP/1.1 200 OK in response to a request. A more detailed error report is added onto the end of the phrase above. |
6 | No data received from server | Generated by the client when a remote server returns HTTP/1.1 200 OK in response to a request, but no response body follows the HTTP headers. |
7 | No SSL support compiled in | Generated by the client when trying to send a request with HTTPS and the CURL extension is not available to PHP. |
8 | CURL error | Generated by the client when trying to send a request with HTTPS and the HTTPS communication fails. |
100 – 799 | XML parse errors | Returns 100 plus the XML parser error code for the fault that occurred. The faultString returned explains where the parse error was in the incoming XML stream. |
800 | Unknown error | Used when a custom error number has not been allocated. The error message should contain further details on the cause of the error. |
801 | Invalid login | Generated when the username and password supplied are unable to be validated against any user in the database. |
802 | Invalid method | Returned if the server was asked to dispatch a method it didn’t know about. |
803 | Invalid return | Generated when the method is unable to process the request and no further information is available. |
Keep up to date with us
Menu
Visit our website
ResRequest Modules
- Business Intelligence
- Central Reservations
- Channel Management
- Customer Relationship Management
- Developer
- Email Series 2022
- Email Series 2023
- Financial Management
- Marketing tools
- Payment Gateways
- Point of sale
- Product
- Professional Services
- Property Management
- ResConnect
- ResInsite
- ResNova
- System Setup
- Technical Alerts
- Technical Tips
- Telephone Management
- Webinars Index