Error reasons

📘 Please note that the list of error reasons is ever-evolving. If you receive an error that is not listed below, let us know by creating a ticket through the Support Portal.

400 Bad Request Exceptions

A 400 Bad Request error occurs when the server cannot process the request due to invalid or malformed input from the client. This could be caused by incorrect or missing parameters, formatting errors, or data that doesn't meet the API's requirements. Essentially, it means that the request itself has an issue, and the client needs to fix it before retrying.

Common 400 Bad Request Exceptions:

• InvalidChannelException: The channel provided is invalid or not supported.

• BadPhoneException: The phone number format is incorrect or missing.

• BadEmailException: The provided email address is invalid or formatted incorrectly.

• ClientCreationException: Error occurs during client creation.

• InvalidBookingTimeException: Selected booking slot is invalid (already taken or unavailable)

• InvalidPasswordException: The provided password is incorrect. The password must respect pattern.

• PropertyCreationException: Error occurs during client creation.

• UserCreationException: Error occurs during client creation.

• ApiAccountValidationException: The provided API account is invalid or does not meet the required to enable the google engine.

These errors indicate that the client should review the request's structure or the data provided and correct any issues before trying again.

🔴 400 Invalid input

{
    "error": {
        "code": "BAD_REQUEST",
        "message": "Invalid input data provided",
        "class_name": "BadRequestException"
    },
    "success": false
}

🔴 400 Invalid channel

{
    "error": {
        "code": "INVALID_CHANNEL",
        "message": "Invalid booking channel",
        "class_name": "InvalidChannelException"
    },
    "success": false
}

🔴 400 Bad phone number

{
    "error": {
        "code": "BAD_PHONE_NUMBER",
        "message": "Bad phone number",
        "class_name": "BadPhoneException"
    },
    "success": false
}

🔴 400 Bad email

{
    "error": {
        "code": "BAD_EMAIL",
        "message": "Bad email",
        "class_name": "BadEmailException"
    },
    "success": false
}

🔴 400 Invalid client

{
    "error": {
        "code": "BAD_CLIENT",
        "message": "Error during client creation",
        "class_name": "ClientCreationException"
    },
    "success": false
}

🔴 400 Invalid slot

{
    "error": {
        "code": "INVALID_BOOKING_TIME",
        "message": "Invalid booking slot time",
        "class_name": "InvalidBookingTimeException"
    },
    "success": false
}

🔴 400 Invalid password

{
    "error": {
        "code": "INVALID_PASSWORD",
        "message": "Invalid password",
        "class_name": "InvalidPasswordException"
    },
    "success": false
}

🔴 400 Invalid property

{
    "error": {
        "code": "BAD_PROPERTY",
        "message": "Error during property creation",
        "class_name": "PropertyCreationException"
    },
    "success": false
}

🔴 400 Invalid user

{
    "error": {
        "code": "BAD_USER",
        "message": "Error during user creation",
        "class_name": "UserCreationException"
    },
    "success": false
}

🔴 400 Validation error

{
    "error": {
        "code": "API_ACCOUNT_VALIDATION",
        "message": "Validation error",
        "class_name": "ApiAccountValidationException"
    },
    "success": false
}

403 Forbidden Exceptions

A 403 Forbidden error occurs when the server understands the request, but refuses to authorize it. This typically happens when the client doesn't have the necessary permissions to access the requested resource. It means that even though the request is valid, the server is denying access due to restrictions such as insufficient rights or the resource being restricted.

Common 403 Forbidden Exceptions:

• ReservationForbiddenException: The client does not have permission to create, modify, or access the reservation.

• TableForbiddenException: The requested table is restricted, and the client is not authorized to interact with it.

• CalendarForbiddenException: The client is not authorized to view or modify the calendar for a given resource.

• BannedCustomerException: The customer is banned from making reservations or accessing the service.

• MaxRoomCapacityReachedException: The maximum capacity for a room or service has been reached, and further bookings are not allowed.

• ProductCalendarOccupiedException: The product or service is unavailable at the requested time due to calendar restrictions or overbooking.

• PropertyForbiddenException: The requested property is forbidden.

• RoomForbiddenException: The requested room is forbidden.

• UserAlreadyExistException: The given user is already exist in system.

• WebhookSubscriptionAlreadyExistException: A webhook subscription with the specified configuration already exists. The client should verify if the subscription is already active or modify the request to avoid duplication.

These errors indicate that even though the request is properly formatted, the client lacks the necessary permissions or the requested resource is restricted for some reason.

🔴 403 Reservation forbidden

{
    "error": {
        "code": "RESERVATION_FORBIDDEN",
        "message": "Reservation not available for a given property",
        "class_name": "ReservationForbiddenException"
    },
    "success": false
}

🔴 403 Table forbidden

{
    "error": {
        "code": "TABLE_FORBIDDEN",
        "message": "Table not available",
        "class_name": "TableForbiddenException"
    },
    "success": false
}

🔴 403 Service forbidden

{
    "error": {
        "code": "SERVICE_FORBIDDEN",
        "message": "Service is not available for a given property",
        "class_name": "CalendarForbiddenException"
    },
    "success": false
}

🔴 403 Customer forbidden

{
    "error": {
        "code": "CUSTOMER_FORBIDDEN",
        "message": "Customer is banned from making reservations",
        "class_name": "BannedCustomerException"
    },
    "success": false
}

🔴 403 Room capacity forbidden

{
    "error": {
        "code": "ROOM_CAPACITY_FORBIDDEN",
        "message": "Room capacity has been exceeded",
        "class_name": "MaxRoomCapacityReachedException"
    },
    "success": false
}

🔴 403 Reservation service forbidden

{
    "error": {
        "code": "RESERVATION_SERVICE_FORBIDDEN",
        "message": "Service has active reservations",
        "class_name": "ProductCalendarOccupiedException"
    },
    "success": false
}

🔴 403 Property forbidden

{
    "error": {
        "code": "PROPERTY_FORBIDDEN",
        "message": "Property forbidden",
        "class_name": "PropertyForbiddenException"
    },
    "success": false
}

🔴 403 Room forbidden

{
    "error": {
        "code": "ROOM_FORBIDDEN",
        "message": "Room forbidden",
        "class_name": "RoomForbiddenException"
    },
    "success": false
}

🔴 403 User exist

{
    "error": {
        "code": "USER_ALREADY_EXIST",
        "message": "User already exist",
        "class_name": "UserAlreadyExistException"
    },
    "success": false
}

🔴 403 Webhook subscription exist

{
    "error": {
        "code": "WEBHOOK_SUNSCRIPTION_ALREADY_EXIST",
        "message": "Webhook subscription already exist for given client and property",
        "class_name": "WebhookSubscriptionAlreadyExistException"
    },
    "success": false
}

404 Not Found Exceptions

A 404 Not Found error occurs when the server is unable to locate the requested resource. This typically happens when the resource (such as a room, reservation, user, or calendar) does not exist or cannot be found in the system. It means the server was unable to match the request to any available data, and the client should verify the resource’s existence or try a different request.

Common 404 Not Found Exceptions:

• PropertyNotFoundException: The requested property does not exist or cannot be found.

• ReservationNotFoundException: The reservation with the specified ID cannot be found in the system.

• RoomNotFoundException: The requested room ID is invalid or does not exist.

• UserNotFoundException: The specified user ID cannot be found in the system.

• ApiAccountNotFoundException: The requested API account does not exist or is incorrect.

• ReservationCanceledException: The reservation has been canceled and is no longer available.

• CalendarNotFoundException: The requested calendar could not be found in the system.

• ClientNotFoundException: The requested client could not be found in the system.

• TableNotFoundException: The requested table could not be found in the system.

• VersionNotFoundException: The requested version could not be found in the system.

• WebhookSubscriptionNotFoundException: The specified webhook subscription does not exist or could not be found in the system.

These errors indicate that the requested data or resource is missing, and the client should check the details (such as IDs or resource names) to ensure they are correct or to verify that the resource exists.

🔴 404 Property not found

{
    "error": {
        "code": "PROPERTY_NOT_FOUND",
        "message": "Property not found",
        "class_name": "PropertyNotFoundException"
    },
    "success": false
}

🔴 404 Reservation not found

{
    "error": {
        "code": "RESERVSTION_NOT_FOUND",
        "message": "Reservation not found",
        "class_name": "ReservationNotFoundException"
    },
    "success": false
}

🔴 404 Room not found

{
    "error": {
        "code": "ROOM_NOT_FOUND",
        "message": "Room not found",
        "class_name": "RoomNotFoundException"
    },
    "success": false
}

🔴 404 User not found

{
    "error": {
        "code": "USER_NOT_FOUND",
        "message": "User not found",
        "class_name": "UserNotFoundException"
    },
    "success": false
}

🔴 404 API account not found

{
    "error": {
        "code": "API_ACCOUNT_NOT_FOUND",
        "message": "Api account not found",
        "class_name": "ApiAccountNotFoundException"
    },
    "success": false
}

🔴 404 Reservation canceled

{
    "error": {
        "code": "RESERVATION_CANCELED",
        "message": "Reservation canceled",
        "class_name": "ReservationCanceledException"
    },
    "success": false
}

🔴 404 Service not found

{
    "error": {
        "code": "SERVICE_NOT_FOUND",
        "message": "Service not found",
        "class_name": "CalendarNotFoundException"
    },
    "success": false
}

🔴 404 Client not found

{
    "error": {
        "code": "CLIENT_NOT_FOUND",
        "message": "Client not found",
        "class_name": "ClientNotFoundException"
    },
    "success": false
}

🔴 404 Table not found

{
    "error": {
        "code": "TABLE_NOT_FOUND",
        "message": "Table not found",
        "class_name": "TableNotFoundException"
    },
    "success": false
}

🔴 404 Version not found

{
    "error": {
        "code": "VERSION_NOT_FOUND",
        "message": "Version not found",
        "class_name": "VersionNotFoundException"
    },
    "success": false
}

🔴 404 Webhook subscription not found

{
    "error": {
        "code": "WEBHOOK_SUNSCRIPTION_NOT_FOUND",
        "message": "Webhook subscription not found",
        "class_name": "WebhookSubscriptionNotFoundException"
    },
    "success": false
}

500 Internal Server Error Exceptions

A 500 Internal Server Error occurs when something goes wrong on the server side while processing the request. This error indicates that the server encountered an unexpected issue or exception that prevented it from fulfilling the request. It's a general error message indicating a problem that wasn't anticipated or handled properly by the system.

Common 500 Internal Server Error Exceptions:

• FileIOException: An issue occurred while trying to read or write a file, such as a corrupted file or an inaccessible directory.

These errors are usually related to problems on the server, and often require server-side intervention to resolve. The client typically does not need to make changes to the request itself, but the server will need to be checked for internal issues.

🔴 500 Internal server error

{
    "error": {
        "code": "INTERNAL_SERVER_ERROR",
        "message": "Unknown error",
        "class_name": "Exception"
    },
    "success": false
}

503 Service Unavailable Exceptions

A 503 Service Unavailable error occurs when the server is temporarily unable to handle the request, often due to being overloaded, undergoing maintenance, or facing temporary issues. The server may be down for a short time, but will likely recover once the issue is resolved.

Common 503 Service Unavailable Exceptions:

• ServiceNotAvailableException: The requested service is temporarily unavailable, possibly due to server overload, scheduled maintenance, or temporary disruptions.

These errors generally indicate a temporary issue with the server, and the client should try again later. It's a server-side issue that requires attention but typically resolves after some time.

🔴 503 Service Unavailable

{
    "error": {
        "code": "SERVICE_BOOK_UNAVAILABLE",
        "message": "Service not available for given date",
        "class_name": "ServiceNotAvailableException"
    },
    "success": false
}