||Redirection. Customers should resolve any 301 HTTP error codes returned from GET method calls by implementing the new URI for the API calls.
||Client errors. These errors need to be resolved from the customer side.
|400 - Bad Request
||Usually caused by a an invalid URI or invalid payload data. Examples include: 1. Using a GET instead of a POST 2. Typo in the URI 3. Most common call with this error - Single Sign On Login API call
|401 - Unauthorised
||Caused by Admin or Member not being logged in to JRNI, JRNI Auth-Token expired or an invalid App-Id.
|403 - Forbidden
||Forbidden request. Do not repeat. Resolve the issue with the request before submitting the call again. Usually caused by a mismatch in Company ID and another entity ID (Person, Resource, Schedule, Client, Queuer, Service, Event etc).
|404 - Not Found
||The resource requested cannot be found. This is typical if the entity record has been deleted from JRNI. Eg the staff member, service, company, or client record has been deleted or the associated reference has been updated.
|405 - Method Not Allowed
||The Method used for the API call is incorrect. Eg using a PUT instead of a GET. Fix the Method before repeating the call again.
|409 - Conflict
||This is the most common response when adding items to the Basket, Checking out the basket or using the Booking API call. The appointment slot or event is fully booked. It may also be returned if using a Service ID for a non bookable service with a Public API call or if the Minimum Advance Time for a service is incorrectly configured in the JRNI platform.
|415 - Unsupported Media Type
||Only returned if using Booking Attachments or Images with JRNI and not setting the HTTP Header correctly for the Content-Type