Hello OwnerRez Team,
I’d like to request support for full block lifecycle management through the API (v2).
## Current Limitation
When working with blocks (is_block = true), the API currently does not allow:
- Deleting a block
- Converting a block into a real booking
Attempting to convert a block results in:
{
"messages": [
"You can't change booking type via API."
],
"status": "bad_request",
"status_code": 400
}
## Why This Matters
In real production environments, blocks are often temporary and part of automated workflows, such as:
- Pending reservation holds
- Maintenance scheduling
- External partner synchronization
- Availability locking during payment flows
However, real integrations require the ability to:
- Confirm a block → convert it into a booking
- Cancel a block → remove it and restore availability
Currently, this forces developers to:
- Use manual UI intervention
- Implement unreliable workarounds
- Break otherwise fully automated booking flows
## Industry Expectation
Most booking systems and channel manager APIs support full inventory hold lifecycle operations:
- Create hold/block
- Confirm hold → booking
- Cancel/delete hold
These capabilities are critical for:
- Preventing double bookings
- Supporting real-time integrations
- Building scalable automation systems
- Enabling partner API ecosystems
## Requested Features
1. Delete Block via API
Example:
DELETE /v2/bookings/{id}
Or any dedicated endpoint for removing blocks.
2. Convert Block → Booking
Allow updating a block into a normal booking through API.
Example:
PATCH /v2/bookings/{id}
{
"is_block": false
}
Or provide a dedicated conversion endpoint.
## Additional Notes
This feature would significantly improve API completeness and reduce dependence on manual operations.
For integration-heavy systems like ours, this functionality is extremely important and would unlock much more reliable automation workflows.
Thank you for considering this request.
