Actions57
- Booking Actions
- Group Actions
- Offer Actions
- Block Actions
- Block Action Actions
- Reservation Actions
- Reservation Action Actions
- Types Actions
- Folio Actions
- Folio Action Actions
Overview
This node integrates with the Apaleo API to manage bookings and related entities. Specifically, for the Booking resource with the POST Force Add Reservations operation, it allows users to forcibly add one or more reservations to an existing booking. This can be useful in scenarios where reservations need to be added programmatically despite potential conflicts or restrictions that might normally prevent such additions.
Practical examples include:
- Automatically adding guest reservations to a booking after receiving external confirmation.
- Forcibly updating bookings with new reservation details during bulk import or synchronization processes.
- Handling exceptional cases where reservations must be added regardless of standard validation rules.
Properties
| Name | Meaning |
|---|---|
| Booking ID | The unique identifier of the booking to which reservations will be forcibly added. |
| Reservations | JSON-formatted data representing the reservations to add. This should contain all necessary reservation details as per Apaleo's API requirements. |
Output
The node outputs an array of JSON objects corresponding to each input item processed. Each output object contains the response from the Apaleo API regarding the forced addition of reservations to the specified booking.
- The
jsonfield includes the API response data confirming the reservations were added or detailing any errors. - There is no indication that this node outputs binary data.
Dependencies
- Requires an active connection to the Apaleo API.
- Needs an API authentication token (access token) configured in the node credentials to authorize requests.
- The base URL used for API calls is
https://api.apaleo.com. - Proper permissions on the Apaleo account are necessary to perform booking modifications.
Troubleshooting
Common issues:
- Invalid or missing Booking ID may cause the API to reject the request.
- Malformed JSON in the Reservations property can lead to parsing errors.
- Insufficient permissions or expired API tokens will result in authorization failures.
- Network connectivity problems can cause request timeouts or failures.
Error messages:
"Invalid booking ID": Verify the Booking ID is correct and exists."Malformed JSON": Check the Reservations JSON format for syntax errors."Unauthorized"or"Access denied": Refresh or reconfigure the API authentication token."Conflict"or"Reservation cannot be added": Even though this is a force add operation, some constraints might still apply; review the reservation data and API documentation.