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 interacts with the Apaleo API, specifically to manage and retrieve data related to various hospitality management resources. When using the Block resource with the GET block operation, the node fetches detailed information about a specific block identified by its ID. This is useful in scenarios where you need to retrieve booking blocks or inventory blocks for hotel management, enabling integrations such as reporting, synchronization with other systems, or custom workflows that depend on block-level data.
Practical example:
A hotel management system could use this node to fetch details of a particular block to display availability or restrictions before confirming new bookings or adjusting existing ones.
Properties
| Name | Meaning |
|---|---|
| Block ID | The unique identifier of the block to retrieve. This is required to specify which block's details should be fetched. |
Output
The output is an array of JSON objects representing the retrieved block(s). Each object contains detailed information about the block, such as its ID, associated dates, status, and any other metadata provided by the Apaleo API for blocks.
If the node supports binary data (not indicated here), it would typically represent attachments or documents related to the block, but in this case, the output is purely JSON data describing the block.
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 for API requests is
https://api.apaleo.com. - No additional external services are required beyond the Apaleo API.
Troubleshooting
Common issues:
- Invalid or missing Block ID: The node requires a valid block ID; ensure this is correctly provided.
- Authentication errors: If the API token is expired or invalid, the node will fail to authenticate.
- Network connectivity problems may prevent reaching the Apaleo API endpoint.
Error messages:
"Unauthorized"or similar indicates issues with the API token; refresh or reconfigure credentials."Not Found"suggests the specified Block ID does not exist or is incorrect."Request failed"or timeout errors indicate network or service availability problems.
To resolve these, verify the Block ID, check API credentials, and ensure network access to the Apaleo API.
Links and References
- Apaleo API Documentation – Official API docs for detailed resource and operation descriptions.
- Apaleo Developer Portal – For managing API credentials and developer support.