Actions66
- Block Actions
- Block Action Actions
- Booking Actions
- Group Actions
- Offer Actions
- Payment Account Actions
- Payment Account Action Actions
- Reservation Actions
- Reservation Action Actions
- Types Actions
- Folio Actions
- Folio Action Actions
Block → GET blocks
AI-generatedOverview
This node interacts with the Apaleo API to retrieve blocks of booking data. Specifically, for the 'Block' resource and 'GET blocks' operation, it fetches blocks filtered by optional parameters such as property IDs, date range, and status. This is useful for scenarios where users want to query and analyze booking blocks within a specified timeframe or status, for example, to generate reports or manage availability.
Use Case Examples
- Retrieve all blocks for specific property IDs within a date range.
- Filter blocks by their status (Tentative, Definite, or Canceled) to manage booking workflows.
Properties
| Name | Meaning |
|---|---|
| Property IDs | Comma-separated list of property IDs to filter blocks by. |
| From Date | Filter blocks starting from this date. |
| To Date | Filter blocks until this date. |
| Status | Filter blocks by their status, such as Tentative, Definite, or Canceled. |
Output
JSON
blocks- Array of block objects retrieved from the Apaleo API based on the applied filters.
Dependencies
- Requires an API key credential for Apaleo API access, specifically an access token for authentication.
Troubleshooting
- Common issues include authentication failures due to invalid or expired access tokens. Ensure the API credentials are correctly configured.
- Incorrect filter parameters (e.g., invalid date formats or property IDs) may result in empty or error responses. Validate input values before execution.
- API rate limits or network issues may cause request failures; handle errors and retry as needed.
Links
- Apaleo API - Get Blocks - Official API documentation for retrieving blocks from Apaleo.