Get certified

This page covers the IBE-specific scenarios you will need to demonstrate during your certification call. For the full certification process — submitting your request, the pre-certification call, prerequisites, and what happens after — see Certify your app or agent.

What we check for IBE integrations

IBE integrations are reviewed more closely than most integration types because errors have a direct impact on revenue and guest experience. During the day-to-day operations section of your certification call, be prepared to walk through the following scenarios.

Property selector

Apaleo integrations connect at the account level, which means your app gets access to all properties under the customer’s account. For an IBE this creates a real risk: without a property selector, your booking engine would either expose all properties indiscriminately or make unnecessary API calls to properties the customer has not enabled for direct booking.

We recommend implementing a property selector that lets the customer choose which properties their IBE should serve. All API requests — offer searches, booking creation, and webhook subscriptions — should be scoped to the selected properties only.

During the certification call, we will verify that:

  • Your integration presents a property selector during onboarding
  • Offer searches and booking requests target only the properties the customer has selected
  • Webhooks are created only for the selected properties
  • Load properties from GET /inventory/v1/properties and present only those the customer has enabled in the property selector
  • Search for offers using channelCode=Ibe and display the results to the guest
  • Display mandatory services included in the offer — these must be visible before the guest confirms
  • Load optional service offers for a selected rate plan and allow the guest to add them
  • Display totalGrossAmount and prePaymentGrossAmount correctly, with city tax shown separately

Payment

  • Correctly sum prePaymentGrossAmount across the selected stay offer and any added services to calculate the total amount to charge
  • Convert the amount from major to minor units before passing it to Adyen
  • Authorise a Prepayment rate plan using Adyen Drop-in
  • Handle a 3D Secure redirect and resume the booking flow after authentication
  • Handle a declined payment gracefully — the guest should be able to retry with a different card
  • Demonstrate correct behaviour for a CreditCard guarantee type (zero-amount authorisation, no charge at booking)

Booking creation

  • Create a booking with channelCode set to "Ibe"
  • Set transactionReference correctly from the Adyen pspReference
  • Set prePaymentAmount to match the amount authorised with Adyen
  • Create a booking that includes a service offer alongside the stay
  • Create a booking with children, passing childrenAges correctly
  • Handle prices with decimal places without rounding errors

Offboarding

When a customer disconnects your app from their Apaleo account, your integration must clean up after itself. We will ask you to disconnect the integration live during the certification call and verify that:

  • All webhooks your app created are deleted on disconnect
  • No orphaned subscriptions remain on the customer’s account after offboarding

Leaving active webhook subscriptions behind after disconnection is a common failure point in certification. Make sure your offboarding flow handles this before the call.