July Updates
31.07.2026
During July 2026, our engineering team has made a variety of backward-compatible updates to our API infrastructure:
New Webhooks
Invoice failure webhook: With this webhook, you can get notified whenever an invoice fails to be generated. https://apaleo.dev/guides/webhook/configuration.html#events
Updated Endpoints
The
IsUnitAssignementLockedfield has been added to the following endpoints:
GET /booking/v1/reservations/{id} GET /booking/v1/reservations
When retrieving reservation data, you can now see directly whether the assigned unit has been locked, meaning the reservation can't be reassigned to a different unit without explicit confirmation.
The
marketSegmentfield has been added to the following endpoints:
GET /booking/v1/groups GET /booking/v1/groups/{id} PATCH /booking/v1/blocks/{id}
Now, when calling these endpoints, you can see if a group block has a market segment set, or add a market segment.
API Promotions
The Routing API (which automatically directs charges to a target folio based on service type and date range) has been fully promoted to V1. Here you can see the new V1 endpoints:
GET /finance/v1/routings GET /finance/v1/routings/{id} POST /finance/v1/routings PATCH /finance/v1/routings/{id} DELETE /finance/v1/routings/{id}
For more info on this update, please consult our API Documentation, for questions please refer to our Community announcement or reach out to api@apaleo.com.
