Deprecation of paymentAccount and accountOwner fields

11.11.2025

#PAYMENTACCOUNTS #DEPRECATION

Over the past few months, we’ve introduced significant enhancements to our payment account features, including the ability to add payment accounts by terminal and link. To support these improvements, we’ve released new APIs that make it easier to add and manage payment accounts.

As part of this update, certain fields in the existing APIs are deprecated in accordance with our deprecation plan and will be permanently removed from the current API. These changes will take effect on February 15, 2026.

Specifically, the paymentAccount field in the CreateBookingModel is deprecated. To add and manage payment accounts, please use the new Payment Account APIs available in the booking section. If you need to pass details for a card that should be activated later, you can use the registeredCard model within the CreateBookingModel itself. This would correspond to passing a paymentAccount without a payerReference in the deprecated APIs.

Also the accountOwner field is deprecated both in POST /booking/v1/authorizations/by-payment-account and POST /finance/v1/folios/{folioId}/payments/by-payment-account. Instead, please use the paymentAccountID field to target the exact payment account that should be used for making the authorization or the payment.

We recommend updating your integrations to use the new APIs as soon as possible to ensure continued compatibility and take advantage of the latest features.

For more info on this update, please consult our API Documentation(Link), for questions please refer to our Community announcement or reach out to api@apaleo.com.

Payment Accounts Webhook Event on Booking

03.11.2025

#PAYMENTACCOUNTS #APALEOPAY #WEBHOOK

We have released a new webhook event: Payment account set on the booking topic. The payment-account-set event will notify you when a when a payment account details are added or updated for a booking. By subscribing to this event, you can stay on top of the changes related to payment account.

{ "endpointUrl": "https://example.com", "events": [ "booking/payment-account-set" ] }

For detailed instructions on how to work with webhook subscriptions, please refer to our developer documentation.

For questions please refer to our Community announcement or reach out to api@apaleo.com.

Payment Accounts now available on V1

03.11.2025

#PAYMENTACCOUNTS #APALEOPAY #V1

We're excited to announce that Payment Account APIs are now available on the V1. This change affects the main API. For more details please refer to the following links: • Booking API • Finance API • Developer guide 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.

Authorizations now available on V1

22.10.2025

#AUTHORIZATIONS #APALEOPAY #V1

We're excited to announce that Authorizations APIs are now available on the v1.

This change affects the main API. For more details please refer to the following links:

• Booking API • Developer guide

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.

IsOpenForCharges : Charge Privileges for Reservations

16.10.2025

#RESERVATIONS #IsOpenForCharges #V1

We're happy to announce an update to the Apaleo Booking API that gives you better control over charge management for your reservations.

What's New? Charge Privileges introduces a new property called isOpenForCharges at the reservation level. This flag provides Point of Sale (POS) systems and other applications with clear information about whether a reservation should accept charges to its folios.

How It Works: Default Behavior

• All reservations default to open for charges (isOpenForCharges: true)

• The flag is purely informational—Apaleo doesn't enforce charge blocking

• POS systems and apps check this flag before posting charges

Managing Charge Privileges You can manage charge privileges in three ways:

1. Through the UI: Authorized staff can toggle the charge privilege flag directly on any reservation

2. Via API: Use the PATCH endpoint to update the flag programmatically

3. With Automation: Set up business rules using tools like Make or Retool to automatically manage the flag based on your criteria

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.

External References Promoted to V1

01.09.2025

#RESERVATIONS #DISTRIBUTION #V1

We're excited to announce that ExternalReferences are now available on the v1. This change spans both the main API and the distribution API. For more details please refer to the following links:

• main API

• Distribution

For any questions regarding this announcement, feel free to contact us at api@apaleo.com or join the community to discuss it!

External References Promoted to V1

01.09.2025

#RESERVATIONS #DISTRIBUTION #V1

We're excited to announce that ExternalReferences are now available on the v1. This change spans both the main API and the distribution API. For more details please refer to the following links:

• main API

• Distribution

For any questions regarding this announcement, feel free to contact us at api@apaleo.com or join the community to discuss it!

External References Promoted to V1

01.09.2025

#RESERVATIONS #DISTRIBUTION #V1

We're excited to announce that ExternalReferences are now available on the v1. This change spans both the main API and the distribution API. For more details please refer to the following links:

• main API

• Distribution

For any questions regarding this announcement, feel free to contact us at api@apaleo.com or join the community to discuss it!

isPreCheckedIn is on V1

13.08.2025

#RATEPLANS #V1

We're excited to announce that the isPreCheckedIn flag is now available across our v1 API endpoints. The following models have been enhanced with this new flag: • ReservationItemModel • ReservationModel • BookingReservationModel • ReservationListRequest Please refer to this link to view the updated API documentation. For any questions regarding this announcement, feel free to contact us at api@apaleo.com or join the community to discuss it!

isPreCheckedIn is on V1

13.08.2025

#RATEPLANS #V1

We're excited to announce that the isPreCheckedIn flag is now available across our v1 API endpoints. The following models have been enhanced with this new flag: • ReservationItemModel • ReservationModel • BookingReservationModel • ReservationListRequest Please refer to this link to view the updated API documentation. For any questions regarding this announcement, feel free to contact us at api@apaleo.com or join the community to discuss it!

isPreCheckedIn is on V1

13.08.2025

#RATEPLANS #V1

We're excited to announce that the isPreCheckedIn flag is now available across our v1 API endpoints. The following models have been enhanced with this new flag: • ReservationItemModel • ReservationModel • BookingReservationModel • ReservationListRequest Please refer to this link to view the updated API documentation. For any questions regarding this announcement, feel free to contact us at api@apaleo.com or join the community to discuss it!