Skip to main content

Apaleo (Set Up Connection)

To connect LIKE MAGIC with the PMS Apaleo, you need to create a Custom App. This guide walks you through the required steps.

note

Keeping reservations in sync: automatic pull fallback. Apaleo normally notifies LIKE MAGIC of reservation and folio changes in real time through webhooks (push). If those webhook notifications are delayed or interrupted, LIKE MAGIC automatically switches to pulling the changes directly from Apaleo on a short polling interval, then switches back to webhooks once delivery recovers. This fallback is on by default and runs behind the scenes. There is no toggle for your team to manage, and no action is needed while Apaleo's webhooks are interrupted. Reservations and folios stay in sync either way.

1. Requirements​

  • You need to have Account Admin rights in your Apaleo account.
  • Make sure you are on the Account level.

2. Instructions​

a) Add a Custom App​

  1. Go to Apps > Connected Apps
  2. Click on Add a new app
  3. Select Add custom app

Apaleo's Connected apps page with the Add a new app link

The Apps section of Apaleo's navigation, expanded to show Connected apps

The Context dropdown of the new app, set to Account

b) Configure the custom app​

Fill in the fields as follows:

FieldValue
Client codeLIKEMAGIC
Client nameLIKEMAGIC
Personally identifiable informationRetrieve
Secret descriptionLIKE MAGIC PMS Connection

The custom app's form with Client code and Client name set to LIKEMAGIC, Personally identifiable information set to Retrieve with the returned guest fields shown as JSON, and a secret described as LIKE MAGIC PMS Connection

c) Define scopes for the API​

Core API

Enable all scopes except:

  • folios.payment-with-charges (please deselect)

The Core API scope list with every scope ticked except folios.payment-with-charges, which is highlighted

New since February 2026

Since this Apaleo community announcement on the deprecation of the paymentAccount and accountOwner fields, these Core API scopes are also required:

  • Core API > payment-accounts.manage
  • Core API > payment-accounts.read

The two payment-accounts scopes selected in the Core API scope list

Enable all scopes for the following APIs:

  • Payment API
  • Distribution API
  • Identity API
  • Fiscalization API
  • Profile API

The Scopes overview per API: Core API at 46 of 47, Payment, Distribution, Identity, Integration, Fiscalization and Profile fully enabled, and MCP server at none

d) Share the Credentials​

  1. Click Save
  2. A popup will display the following credentials:
  • ClientId
  • ClientSecret

The popup showing the generated ClientId and ClientSecret

warning

Important: Please do not send these credentials via email. Instead, use a secure one-time link service like onetime.secret.

Was this article helpful?