Apaleo icon

Apaleo

Interact with Apaleo API
Join our community

Actions57

Overview

This node interacts with the Apaleo API to perform various actions related to reservations, specifically including the "amend reservation" operation. The "PUT amend reservation" operation allows users to modify existing reservation details by specifying the reservation ID and submitting updated information. This is useful in scenarios where a booking needs to be changed after it has been made, such as updating guest details, changing dates, or modifying other reservation parameters.

Practical examples include:

  • Updating the number of guests for an existing reservation.
  • Changing the check-in or check-out dates.
  • Adjusting special requests or notes associated with the reservation.

Properties

Name Meaning
Reservation ID Filter bookings by reservation ID. This identifies which reservation to amend.

Output

The node outputs JSON data representing the result of the amend reservation operation. This typically includes the updated reservation details returned from the Apaleo API after the amendment is applied. The output structure reflects the reservation resource with its current state post-update.

If the operation fails and "Continue On Fail" is enabled, the output will contain an error message alongside an empty JSON object for that item.

No binary data output is involved in this operation.

Dependencies

  • Requires an API key credential for authenticating with the Apaleo API.
  • The node uses the base URL https://api.apaleo.com for all requests.
  • Proper configuration of the API authentication token is necessary within n8n credentials.

Troubleshooting

  • Common issues:

    • Invalid or missing Reservation ID: The API will reject requests without a valid reservation identifier.
    • Authentication errors: Ensure the API key/token is correctly configured and has sufficient permissions.
    • Network or connectivity problems may cause request failures.

  • Error messages:

    • Errors returned from the Apaleo API will be surfaced in the node's output if "Continue On Fail" is enabled.
    • Typical errors include "Reservation not found," "Unauthorized," or validation errors on the amended data.

  • Resolution tips:

    • Verify the Reservation ID exists and is correct.
    • Check API credentials and renew tokens if expired.
    • Validate the amendment payload conforms to expected formats and constraints.

Links and References

Discussion