Resources · Make integration

apaleo Make integrationAutomate apaleo with Make.

Can Make take the repetitive desk work out of your apaleo property? Yes: the apaleo Make integration offers 218 modules, with 1 instant trigger, 162 actions and 55 searches. This guide is for hotel ops and revenue teams, from connection to a first working scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the apaleo Make integration do for your hotel?

The apaleo Make integration links your apaleo property management system to Make, a no-code tool where you build a scenario: an automation made of modules, each one a brick that watches, creates or searches something. An apaleo event can start the scenario, and the actions that follow handle reservations, folios, invoices and property setup.

Corporate clients ready before they arrive. When a sales rep closes a deal in your CRM, Create Company adds the firm to apaleo, Create Group opens the group booking, and Create Group Reservation fills it with the rooms the client asked for.

Extras on the right bill. A spa treatment or a parking pass sold through another tool reaches the guest folio with Create Charge Folio, and Create Invoice turns the settled folio into an invoice when the stay is over.

Accounting data without the manual export. Create Accounting Report Export pulls the raw transactions of a property for the period you pick, and the next module can pass them to a spreadsheet or to your accounting software.

What Make will not do for you here: the apaleo doc gives no numeric limit, but every module needs the right scope on the app you register in apaleo, and a few actions, Close Folio among them, cannot be reversed. For anything the 218 modules miss, Make an API Call reaches the rest of the apaleo API with the same connection.

New to the editor? The Make training starts from zero, Make pricing explains how operations are counted, and n8n vs Make helps if you are still choosing a tool.

Connect

How do you connect apaleo to Make?

  1. 01

    Register an app in apaleo

    Sign in to your apaleo developer account, open Apps then My store apps, and click + Add a new app. Complete the form, click Save, then copy the Client ID and Client Secret and keep them somewhere safe.

  2. 02

    Open the connection in Make

    Add an apaleo module to your scenario and click Create a connection. A connection is your apaleo account linked to Make once and reused by every apaleo module. With Watch apaleo Events, click Create a webhook first.

  3. 03

    Paste the keys and save

    Name the connection in Connection name if you like, paste the two values into Client ID and Client Secret, and click Save. If apaleo asks, sign in and confirm access.

First scenario

Your first apaleo scenario in Make

GoalWhen a new corporate client is added in your CRM, Make creates the matching company in apaleo.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Pick your CRM as the first module: it is the source of the client details.

  2. 02

    Add Create Company

    Click the + on the right of the CRM module, search for apaleo and choose Create Company. Click Create a connection and paste the keys from the section above.

  3. 03

    Map the client details

    Fill the Create Company fields by mapping the values from the CRM module. Each bundle, one client record moving from module to module, becomes one company in apaleo.

  4. 04

    Test with Run once

    Click Run once to execute the scenario a single time, open the bundles each module received, then look for the new company in apaleo.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module, every 15 minutes by default, and switch the scenario on. Every module run on a bundle is one operation on your Make plan.

Triggers

What starts an apaleo scenario?

1 module starts a scenario when something happens in apaleo. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by apaleo as soon as it happens.

apaleo1Watch apaleo Events

Watch apaleo Events

Instant trigger

In Make“Runs when an event occurs in your apaleo account.”

Watch apaleo Events starts your scenario when something happens in your apaleo account and passes that event to the next module as a bundle, so the rest of the flow works on fresh data.

How it fires
instant, apaleo calls Make through a webhook as soon as it happens (the lightning badge on the module).
When to use it
Any flow that should react to activity in the property instead of waiting for a schedule.
Watch out
The doc asks you to click Create a webhook before Create a connection. After that, a Run once shows exactly what the event carries.
Modules

What can apaleo do in a Make scenario?

apaleo gives you 217 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

apaleo1

Add City Tax Reservation

Action

In Make“Use this if you want to add the city tax to a reservation. You must have this scope: 'reservations.manage'.”

Puts the city tax on one reservation, so the guest's bill carries the levy without anyone editing it at the front desk.

When to use it
A booking came in through a channel that left the tax out and the stay has to match local rules.
Watch out
The app registered in apaleo needs the reservations.manage scope for this module.
apaleo2

Amend Block

Action

In Make“Use this call to modify a block. You must have at least one of these scopes: 'blocks.manage, reservations.manage'.”

Changes an existing block, the set of rooms held for a group, so the allotment in apaleo follows what was agreed with the organizer.

When to use it
The event planner sends revised numbers and you want the block updated from that message.
Watch out
It takes blocks.manage or reservations.manage; check the scope before blaming the mapping.
apaleo3

Amend Reservation

Action

In Make“Modifies the stay-related data of a reservation. If a reservation is 'Confirmed', you can change all fields. If a reservation is 'InHouse', only changes to future time slices are possible. Changes to reservations that are in the status 'CheckedOut' or 'Canceled' are not possible at all. You must have this scope: 'reservations.manage'.”

Edits the stay details of a reservation, such as dates, so the booking in apaleo matches what the guest asked for.

When to use it
A guest requests a shorter or longer stay by email and you want the change applied without retyping.
Watch out
A Confirmed reservation accepts every change, an InHouse one only changes to future time slices, and CheckedOut or Canceled ones cannot be amended at all.
apaleo4

Assign Specific Unit Reservation

Action

In Make“Assigns a specific unit to a reservation which is in state 'Confirmed' or 'InHouse'. If the unit is not available, the call will return an error, and no unit will be assigned. You must have at least one of these scopes: 'reservations.assign-unit, reservations.manage'.”

Gives a reservation the exact room you name, for guests who were promised a particular unit.

When to use it
A returning guest always gets the corner room and the request sits in your CRM.
Watch out
The reservation must be Confirmed or InHouse, and if that unit is not free the call returns an error and assigns nothing, so plan an error route.
apaleo5

Assign Unit Reservation

Action

In Make“Assigns one of the available units to a reservation which is in state 'Confirmed' or 'InHouse'. You must have at least one of these scopes: 'reservations.assign-unit, reservations.manage'.”

Lets apaleo pick any available room for a reservation, which is the quick way to get bookings ready for check-in.

When to use it
The guest has no room preference and the only goal is that a unit is attached before arrival.
Watch out
Only Confirmed or InHouse reservations qualify; prefer Assign Specific Unit Reservation when the room number matters.
apaleo6

Book Service Reservation

Action

In Make“Use this to book a service for a specific reservation. Please note that when dates are specified, all desired dates must be specified or they will be removed if not posted to the folio. You must have this scope: 'reservations.manage'.”

Adds a service, breakfast or parking for instance, to one reservation so it shows up on the stay and later on the bill.

When to use it
The guest ticks an extra in your pre-arrival form and it should land on the booking.
Watch out
When you send dates, send all of them; dates you leave out are removed unless they were already posted to the folio.
apaleo7

Cancel Block

Action

In Make“Cancel a specific block which is in status 'Definite' or 'Tentative'. This changes the status to 'Canceled'. You must have at least one of these scopes: 'blocks.manage, reservations.manage'.”

Releases a group block by switching it to Canceled, which frees the held rooms for regular sale.

When to use it
The organizer confirms in writing that the event is off and the allotment should disappear.
Watch out
It only works on blocks in Definite or Tentative status, and it needs blocks.manage or reservations.manage.
apaleo8

Cancel Invoice

Action

In Make“For regular invoices and AR invoices that haven't been paid yet, creates a new cancellation invoice and opens the folio again. For advance invoices, creates a new cancellation invoice. You must have this scope: 'invoices.manage'.”

Voids an invoice by creating a cancellation invoice; for a regular or AR invoice not yet paid, the folio opens again so you can fix it.

When to use it
The billing address was wrong and finance needs a clean invoice.
Watch out
On an advance invoice you only get the cancellation invoice, the folio is not reopened. Scope: invoices.manage.
apaleo9

Cancel Payment

Action

In Make“Sets a payment to cancelled and triggers the cancellation. You must have this scope: 'folios.manage'.”

Marks a payment as cancelled and starts the cancellation, so a payment taken by mistake does not stay on the folio.

When to use it
Your payment tool flags a duplicate charge and the matching apaleo payment has to go.
Watch out
This touches money; test it with Run once on a test folio and check the folios.manage scope.
apaleo10

Cancel Reservation

Action

In Make“Cancel a specific reservation which is in status 'Confirmed' and where the arrival time is in the future. This changes the status to 'Canceled', and sets the cancellation date and time. You must have this scope: 'reservations.manage'.”

Cancels a single reservation, sets its status to Canceled and records the cancellation date and time.

When to use it
A guest cancels through a form or a chat tool and you want apaleo to reflect it straight away.
Watch out
Only Confirmed reservations whose arrival is still in the future can be cancelled; past arrivals need another path.
apaleo11

Checkin Reservation

Action

In Make“Check in a specific reservation which is in status 'Confirmed', and has a unit assigned. This changes the status to 'InHouse', and sets the check-in date and time. You must have this scope: 'reservations.manage'.”

Checks a guest in: the reservation moves to InHouse and apaleo stores the check-in date and time.

When to use it
A self check-in kiosk or a digital key tool confirms the guest is on site.
Watch out
The reservation must be Confirmed and already have a unit, so place Assign Unit Reservation before it in the flow when needed.
apaleo12

Checkout Reservation

Action

In Make“Check out a specific reservation which is in status 'InHouse'. This changes the status to 'CheckedOut', and sets the check-out date and time. All open charges on the folio will be posted. Check-out is only possible, if the departure date is not later than tomorrow. Otherwise, first amend the reservation and shorten the stay. You must have this scope: 'reservations.manage'.”

Checks a guest out, sets the reservation to CheckedOut and posts every open charge on the folio.

When to use it
An express checkout link is completed and the room should be freed.
Watch out
The reservation must be InHouse and the departure date no later than tomorrow; for an early departure, amend the reservation first to shorten the stay.
apaleo13

Close Folio

Action

In Make“Mark a folio as closed to prevent adding charges and payments. This action cannot be undone, and is only possible if the balance is 0. Requires 'allowed action': Close. You must have this scope: 'folios.manage'.”

Locks a folio so no charge or payment can be added, which keeps a settled account from moving afterwards.

When to use it
The invoice is issued, the balance is zero and the file should be frozen.
Watch out
This cannot be undone, it requires a balance of 0 and the Close allowed action; add a filter on the balance before this module.
apaleo14

Confirm Block

Action

In Make“Confirm a specific block which is in status 'Tentative'. This changes the status to 'Definite'. You must have at least one of these scopes: 'blocks.manage, reservations.manage'.”

Turns a Tentative block into a Definite one, the signal that a group booking is firm.

When to use it
The group contract comes back signed through your e-signature tool.
Watch out
A block that is already Definite or Canceled will not move; read it first with a search if the status is uncertain.
apaleo15

Correct Folio

Action

In Make“Allowance value posted must not exceed sum of charges minus existing allowances You must have this scope: 'folios.manage'.”

Posts a correction on a folio as an allowance, to fix an amount charged by mistake without deleting the original line.

When to use it
The manager approves a goodwill reduction in a ticket and the folio should follow.
Watch out
The value cannot exceed the sum of charges minus the allowances already posted; scope folios.manage.
apaleo16

Create Accounting Report Aggregate

Action

In Make“Returns credited and debited amounts aggregated by transactions' timestamp for all accounts and a given period. Stores an entry in the export audit log. You must have at least one of these scopes: 'subledger.read, accounting.read'.”

Returns credited and debited totals for all accounts over a period, grouped by the timestamp of each transaction.

When to use it
The controller wants totals by exact posting time rather than by business day.
Watch out
Each run writes an entry in the export audit log, and the connection needs subledger.read or accounting.read.
apaleo17

Create Accounting Report Aggregate Daily

Action

In Make“Returns credited and debited amounts aggregated by transactions' date (business day) for all accounts and a given period. Stores an entry in the export audit log. You must have at least one of these scopes: 'subledger.read, accounting.read'.”

Gives the same credited and debited totals, grouped by business day instead of timestamp, which is how most hotel accountants read a period.

When to use it
You reconcile revenue day by day of operation.
Watch out
Like the timestamp version, it leaves a trace in the export audit log.
apaleo18

Create Accounting Report Aggregate Pairs Daily

Action

In Make“Returns total amount credited from one account to another You must have at least one of these scopes: 'subledger.read, accounting.read'.”

Shows how much moved from one account to another, pair by pair, so you see the flows rather than just balances.

When to use it
Your accountant maps apaleo accounts to the general ledger and needs the account-to-account totals.
Watch out
Scope subledger.read or accounting.read is required, as for the other aggregate modules.
apaleo19

Create Accounting Report Export

Action

In Make“Returns the raw transaction data for a given property and time period. Stores an entry in the export audit log. You must have at least one of these scopes: 'transactions.export, accounting.read'.”

Pulls the raw transactions of one property over a time period, the line-level data behind every total.

When to use it
A finance tool needs detailed entries to import, not a summary.
Watch out
It needs transactions.export or accounting.read, and each export lands in the audit log; add an iterator if the next app expects one line per bundle.
apaleo20

Create Accounting Report Export Daily

Action

In Make“Returns the raw transaction data for a given property and time period. Stores an entry in the export audit log. You must have at least one of these scopes: 'transactions.export, accounting.read'.”

Delivers the raw transaction data of a property for a period, in the daily variant of the export, for tools that load data one business day at a time.

When to use it
Your bookkeeping import is organized by business day.
Watch out
Compare its output with Create Accounting Report Export on a Run once before choosing one.
apaleo21

Create Accounting Report Export Gross Daily

Action

In Make“Returns the raw transaction data for a given property and time period. Stores an entry in the export audit log. You must have at least one of these scopes: 'transactions.export, accounting.read'.”

Exports raw transactions for a property and period in the gross daily variant, the third flavor of the transaction export.

When to use it
Your accountant asks for gross figures rather than the standard export.
Watch out
The doc describes all three exports in the same words, so run each once and read the bundles to confirm which format fits.
apaleo22

Create Age Category

Action

In Make“Use this call to create a new age category. The age ranges for categories must not overlap each other and the allowed values span from 0 to 17. You must have at least one of these scopes: 'settings.manage, setup.manage'.”

Adds an age category, such as infants or teens, that rates and occupancy rules can then refer to.

When to use it
You open a new property and want its child categories set up from a template.
Watch out
Ranges must not overlap and allowed ages span from 0 to 17; scope settings.manage or setup.manage.
apaleo23

Create Allowance Folio

Action

In Make“Allowance value posted must not exceed sum of charges minus existing allowances You must have at least one of these scopes: 'allowances.post, folios.manage'.”

Posts an allowance, a credit that lowers what the guest owes, on a whole folio.

When to use it
A complaint is resolved with a gesture on the total bill rather than on one charge.
Watch out
The credit cannot exceed the charges minus existing allowances; for one precise line, choose Create Charge Allowance Folio.
apaleo24

Create Block

Action

In Make“You must have at least one of these scopes: 'blocks.create, reservations.manage'.”

Holds a set of rooms for a group in apaleo, so they stop selling to individual guests while the deal is discussed.

When to use it
A wedding or seminar request reaches your sales pipeline and inventory should be protected.
Watch out
The connection needs blocks.create or reservations.manage; confirm the block later with Confirm Block.
apaleo25

Create Booking

Action

In Make“Creates a booking taking a list of reservations as input You must have at least one of these scopes: 'reservations.create, reservations.manage'.”

Creates a booking from a list of reservations, the container that ties several rooms to one booker.

When to use it
A direct booking form or a partner channel sends a complete order that apaleo has to store.
Watch out
It takes a list of reservations as input, so build that list with an aggregator when the rooms come in as separate bundles.
apaleo26

Create Booking Reservation

Action

In Make“Creates new reservations and adds them to an existing booking taking a list of reservations as input You must have at least one of these scopes: 'reservations.create, reservations.manage'.”

Adds new reservations to a booking that already exists, without creating a second booking for the same guest.

When to use it
A family books one room, then adds a second one for the grandparents.
Watch out
You need the booking identifier; fetch it with Search Bookings earlier in the scenario.
apaleo27

Create Bulk Allowances Folio

Action

In Make“Allowance value posted must not exceed sum of charges minus existing allowances You must have at least one of these scopes: 'allowances.post, folios.manage'.”

Posts several allowances on a folio in one module run, instead of looping over them one by one.

When to use it
A service outage affects several charges on the same stay and each needs its credit.
Watch out
The total still cannot exceed the charges minus the allowances already posted; scope allowances.post or folios.manage.
apaleo28

Create Cancellation Fee Folio

Action

In Make“Adds a cancellation fee, and directly posts it. Cancellation fees can only be posted on guest folios. Requires 'allowed action': AddCancellationFee. You must have at least one of these scopes: 'charges.create, folios.manage'.”

Adds a cancellation fee and posts it at once, so the penalty from your policy is actually billed.

When to use it
Right after Cancel Reservation, when the late cancellation falls under a fee.
Watch out
Fees go on guest folios only, and the folio must allow the AddCancellationFee action.
apaleo29

Create Cancellation Policy

Action

In Make“Create a cancellation policy. You must have at least one of these scopes: 'settings.manage, setup.manage'.”

Sets up a cancellation policy in apaleo, the rule that later decides which fee applies when a guest cancels.

When to use it
You roll out a new flexible or non-refundable policy across properties from one source list.
Watch out
This is setup, not daily work; scope settings.manage or setup.manage.
apaleo30

Create Charge Allowance Folio

Action

In Make“Allowance value posted must not exceed source charge minus allowances posted for this charge You must have at least one of these scopes: 'allowances.post, folios.manage'.”

Grants an allowance against one specific charge, so the credit is tied to the line it corrects.

When to use it
The minibar was billed twice and only that item should be offset.
Watch out
The credit cannot exceed that charge minus the allowances already posted on it; for the whole folio, use Create Allowance Folio.
apaleo31

Create Charge Folio

Action

In Make“Adds a charge for any good or service, and directly posts it. Can be used to charge items that are not part of the reservation, but should appear on the invoice. Requires 'allowed action': AddCharge. You must have at least one of these scopes: 'charges.create, folios.manage'.”

Adds and posts a charge for any good or service, even one that is not part of the reservation but belongs on the invoice.

When to use it
Your restaurant or spa system records a sale for a room and the guest should find it on the bill.
Watch out
The folio must allow the AddCharge action, and the scope is charges.create or folios.manage.
apaleo32

Create City Tax

Action

In Make“You can only create one city tax per property. It can be changed and deleted any time. You must have at least one of these scopes: 'settings.manage, setup.manage'.”

Defines the city tax of a property, which Add City Tax Reservation then applies to stays.

When to use it
A new property joins your account and its local tax must exist before bookings flow in.
Watch out
One city tax per property only; change the existing one instead of creating a second.
apaleo33

Create Company

Action

In Make“Use this call to create a new company. You must have at least one of these scopes: 'companies.create, companies.manage'.”

Creates a company in apaleo, the business profile that corporate bookings and invoices can point to.

When to use it
A B2B client is won in your CRM and should exist in the PMS before the first booking.
Watch out
To avoid a second profile for the same client, run Search Companies first and add a filter on the result.
apaleo34

Create Folio

Action

In Make“Use this call to create a new folio. You must have at least one of these scopes: 'reservations.create, reservations.manage, folios.manage'.”

Opens a new folio, the account where charges and payments of a stay or a guest are recorded.

When to use it
An extra account is needed, for example to separate what the company pays from what the guest pays.
Watch out
Scope reservations.create, reservations.manage or folios.manage; charges come afterwards with Create Charge Folio.
apaleo35

Create Group

Action

In Make“You must have at least one of these scopes: 'groups.create, reservations.manage'.”

Starts a group booking, the umbrella under which blocks and group reservations are gathered.

When to use it
A tour operator confirms a stay for a team and you want one place to follow all their rooms.
Watch out
The group is empty at first; add rooms with Create Group Reservation once it exists.
apaleo36

Create Group Reservation

Action

In Make“Creates new reservations and adds them to an existing group booking taking a list of reservations as input You must have at least one of these scopes: 'groups.manage, reservations.manage'.”

Adds new reservations to an existing group booking from a list, so each traveler gets a room under the same group.

When to use it
The rooming list arrives in a spreadsheet and every name should become a reservation.
Watch out
The input is a list, so aggregate the rows first; scope groups.manage or reservations.manage.
apaleo37

Create Invoice

Action

In Make“Creates an invoice for one specific folio. The invoice can only be created once. The debitor needs to have name, city, postal code and country code, as these are required for invoices. If the folio is not fully paid, this will check out the reservation on AR and create an invoice with outstanding payments. You must have at least one of these scopes: 'invoices.create, invoices.manage'.”

Produces the invoice for one folio, the document the guest or the company receives at the end of the stay.

When to use it
Checkout is done and the invoice should be generated and sent without a desk agent.
Watch out
It can be created only once, the debitor needs a name, city, postal code and country code, and an unpaid folio triggers a checkout on AR.
apaleo38

Create Maintenance

Action

In Make“Use this call to create a new maintenance window for the given unit. You can only create maintenances for today and days in the future. You must have at least one of these scopes: 'maintenances.create, maintenances.manage'.”

Opens a maintenance window on one unit, so a room under repair is not sold during that time.

When to use it
Housekeeping reports a leak in your ticketing tool and the room must be blocked.
Watch out
Only today or future days are accepted; a backdated window will fail.
apaleo39

Create Multiple Maintenances

Action

In Make“Use this call to create multiple maintenances. You must have at least one of these scopes: 'maintenances.create, setup.manage'.”

Creates several maintenance windows in one go, which suits a renovation that touches many rooms.

When to use it
A floor is being repainted and every unit on it should leave inventory together.
Watch out
Its scope differs from the single version: maintenances.create or setup.manage.
apaleo40

Create Multiple Units

Action

In Make“Use this call to create multiple units, following a naming rule. You must have at least one of these scopes: 'units.create, setup.manage'.”

Generates a batch of units, the rooms apaleo sells, from a naming rule instead of typing them one at a time.

When to use it
You set up a new wing or a new property with rooms numbered in sequence.
Watch out
Check the naming rule on a Run once in a test property; scope units.create or setup.manage.
apaleo41

Create No Show Fee Folio

Action

In Make“Adds a no-show fee, and directly posts it. No-show fees can only be posted on guest folios. Requires 'allowed action': AddNoShowFee. You must have at least one of these scopes: 'charges.create, folios.manage'.”

You get the no-show fee added and posted straight onto the guest's bill, with no manual step at the front desk. In apaleo, a folio is the running bill of a stay.

When to use it
A guest never arrived and your policy says the night is charged: the scenario posts the fee as soon as the no-show is known.
Watch out
It only works on guest folios; the connection needs the charges.create or folios.manage scope.
apaleo42

Create No Show Policy

Action

In Make“Create a no-show policy. You must have at least one of these scopes: 'settings.manage, setup.manage'.”

This module sets up a new no-show policy in apaleo from your scenario, so the rule that decides what an absent guest pays exists before any booking relies on it.

When to use it
You open a new property or rate and want its no-show rule created along with the rest of the setup, from the same scenario.
Watch out
The connection needs the settings.manage or setup.manage scope, otherwise apaleo refuses the call.
apaleo43

Create Payment

Action

In Make“A custom payment will not involve any automatic processing. This is best to be used for cash, cheque or voucher payments or payments that have been processed by an external system and it should just be recorded in apaleo for accounting purposes. You must have this scope: 'folios.manage'.”

You record a payment on a folio for bookkeeping, without apaleo processing any money. It suits cash, cheques, vouchers, or payments already handled by another system.

When to use it
Your external payment tool confirms a transfer and you want apaleo's accounts to show it on the right bill.
Watch out
No card is charged here; if you need an actual charge, pick one of the payment modules that process it, such as Create Payment By Terminal.
apaleo44

Create Payment By Authorization

Action

In Make“Captures a specific amount from a pre-authorization and posts it to the folio. For the pre-authorization please ensure to set the respective metadata in the original payment transaction. The flow type has to be set to <i>CaptureOnly</i>. For more information please refer to the documentation of <a href="https://apaleo.dev/guides/business-cases/ibe/getting-the-money" target="_blank">how to do a pre-authorization on a booking engine</a>. The payment will be processed asynchronously. Use the location header to poll for the status of the payment. As long as a payment is pending it reduces the amount of allowed payments for the folio. The payment times out after 60 minutes automatically You must have this scope: 'folios.manage'.”

This takes a chosen amount from a card pre-authorization and posts it to the folio, so money held at booking becomes an actual payment on the bill.

When to use it
Your booking engine placed a hold at reservation time and you want to capture part or all of it when the stay is billed.
Watch out
The original transaction must carry the CaptureOnly flow type; the payment is processed asynchronously and times out after 60 minutes.
apaleo46

Create Payment By Payment Account

Action

In Make“Trigger a payment for the folio using the payment account stored on the reservation. The payment will be processed asynchronously. Use the location header to poll for the status of the payment. As long as a payment is pending it reduces the amount of allowed payments for the folio. The payment times out after 60 minutes automatically You must have this scope: 'folios.manage'.”

This charges the folio using the payment account already stored on the reservation, so the guest pays without handing over a card again.

When to use it
The guest left card details at booking and you want the bill settled automatically when a stay event lands in your scenario.
Watch out
Processing is asynchronous and times out after 60 minutes; while pending, it lowers the amount still allowed for payments on that folio.
apaleo47

Create Payment By Terminal

Action

In Make“Trigger a terminal payment for the folio. The payment will be processed asynchronously. Use the location header to poll for the status of the payment. As long as a payment is pending it reduces the amount of allowed payments for the folio. The payment times out after 60 minutes automatically You must have this scope: 'folios.manage'.”

You send a payment request to a card terminal for a given folio, so the amount appears on the device without anyone typing it in.

When to use it
Guests pay in person at the desk and you want the terminal prompted from the scenario that prepares the bill.
Watch out
The payment is asynchronous and times out after 60 minutes; a pending one reduces what the folio can still accept.
apaleo48

Create Payment Refund

Action

In Make“Trigger a refund for a specific payment on this folio. The refund will be processed asynchronously. Use the location header to poll for the status of the refund. As long as a refund is pending the allowed refund amount for this payment will be reduced by the amount. The refund times out after 10 minutes automatically You must have this scope: 'folios.manage'.”

This refunds one specific payment on a folio, so the money goes back through the same payment it came from.

When to use it
A guest paid twice or cancelled within policy and you know exactly which payment to reverse.
Watch out
It times out after 10 minutes; while pending, the refundable amount for that payment is reduced. For a refund not tied to one payment, see Create Refund.
apaleo49

Create Property

Action

In Make“Use this call to create a new property. You must have at least one of these scopes: 'properties.create, setup.manage'.”

You create a new property in apaleo from a scenario, the hotel or building that everything else (units, rates, services) hangs from.

When to use it
You roll out a new site and want it created from a sheet or form row instead of filling the setup screens by hand.
Watch out
The connection needs the properties.create or setup.manage scope.
apaleo50

Create Rate Plan

Action

In Make“Use this call to create a new rate plan. The rate plan will already contain empty rates, fill them later using PUT rates. You must have at least one of these scopes: 'rateplans.create, setup.manage'.”

This creates a rate plan, the pricing frame a room is sold under, with its rates already in place but empty, waiting for prices.

When to use it
You launch a new offer and want the plan created first, then priced by a following module such as Update Rates.
Watch out
The new plan has no prices yet, so add a module that fills its rates before selling; scope rateplans.create or setup.manage.
apaleo51

Create Refund

Action

In Make“Trigger a generic refund for the folio. The refund will be processed asynchronously. Use the location header to poll for the status of the refund. As long as a refund is pending it reduces the amount of allowed refunds for the folio. The refund times out after 60 minutes automatically You must have this scope: 'folios.manage'.”

You trigger a general refund on a folio, not linked to one particular payment, so a credit owed to the guest can be paid back.

When to use it
The amount to return does not match a single payment, for example after a goodwill gesture decided by the manager.
Watch out
It is asynchronous and times out after 60 minutes; a pending refund reduces what the folio can still refund. To reverse one payment, use Create Payment Refund.
apaleo52

Create Service

Action

In Make“Create a service. You must have at least one of these scopes: 'services.create, setup.manage'.”

This adds a service to apaleo's catalogue, an extra the guest can book on top of the room, such as breakfast or parking.

When to use it
You add a new extra to your offer and want it created alongside its listing in your other tools, from one scenario.
Watch out
Creating the service does not attach it to any stay; booking it on a reservation is a separate module. Scope services.create or setup.manage.
apaleo53

Create Sub Account

Action

In Make“Create a sub-account. You must have at least one of these scopes: 'subledger.manage, setup.manage'.”

You create a sub-account in apaleo's accounting, a finer line under which revenue or charges can be booked and later reported.

When to use it
Your accountant asks for a dedicated line for a new revenue stream and you want it created from the scenario that sets it up.
Watch out
The connection needs the subledger.manage or setup.manage scope.
apaleo54

Create Time Slice Definition

Action

In Make“Use this call to create a time slice definition. You must have at least one of these scopes: 'settings.manage, setup.manage'.”

This creates a time slice definition, the unit of time apaleo uses to sell and price a stay, from a scenario instead of the settings screen.

When to use it
You configure a new property from a template sheet and want its time slices created in the same run as the rest of the setup.
Watch out
The connection needs the settings.manage or setup.manage scope.
apaleo55

Create Transitory Charge Folio

Action

In Make“Adds a transitory item for any good or service, and directly posts it. To be used for sales that are not revenue of the property, but should appear on te guest's invoice. Requires 'allowed action': AddCharge. You must have at least one of these scopes: 'charges.create, folios.manage'.”

You add and post a transitory item on a folio: a sale that is not the property's own revenue but must still appear on the guest's invoice.

When to use it
The guest bought theatre tickets or a tour through the desk on behalf of a partner, and the amount has to show on their bill.
Watch out
Use it only for third-party sales; the property's own extras belong in a regular charge. Scope charges.create or folios.manage.
apaleo56

Create Unit

Action

In Make“Use this call to create a new unit. You must have at least one of these scopes: 'units.create, setup.manage'.”

This creates a unit in apaleo, a room or bookable space, so it can be assigned to reservations as soon as it exists.

When to use it
You add rooms after a renovation and want each one created from a list rather than entered one by one.
Watch out
To create several at once there is a separate multi-unit module; the connection needs the units.create or setup.manage scope.
apaleo57

Create Unit Attribute

Action

In Make“Use this call to create a new unit attribute. You must have at least one of these scopes: 'unitattributes.create, setup.manage'.”

You create a unit attribute, a label such as sea view or balcony that you can then attach to rooms to describe and filter them.

When to use it
You start selling a feature some rooms have and want the attribute ready before tagging those rooms.
Watch out
Creating the attribute tags no room by itself; the connection needs the unitattributes.create or setup.manage scope.
apaleo58

Create Unit Group

Action

In Make“Use this call to create a new unit group. You must have at least one of these scopes: 'unitgroups.create, setup.manage'.”

This creates a unit group, the room category guests actually book (for example double or suite), under which individual units are gathered.

When to use it
You introduce a new room type and want the category in place before creating its rooms and rate plans.
Watch out
The connection needs the unitgroups.create or setup.manage scope; create the group before the units that belong to it.
apaleo59

Delete Age Category

Action

In Make“Use this call to delete an age category. You can only delete an age category if it is not already used in a rate plan to define age specific prices. You must have at least one of these scopes: 'settings.manage, setup.manage'.”

You remove an age category, such as a child bracket, that you no longer price separately, keeping the setup list clean.

When to use it
You simplify your offer and stop charging a specific age range differently.
Watch out
apaleo refuses the deletion while a rate plan still uses the category for age-based prices; scope settings.manage or setup.manage.
apaleo60

Delete Block

Action

In Make“Use this call to delete a block. This is only possible as long as no reservation was picked up yet even if all of them are canceled You must have at least one of these scopes: 'blocks.manage, reservations.manage'.”

This deletes a block, a set of rooms held for a group or event, when the deal falls through before any room was taken.

When to use it
A group enquiry ends without a signed contract and the rooms held for it must go back on sale.
Watch out
Deletion is only possible while no reservation has been picked up from the block, even cancelled ones; otherwise use the cancel module.
apaleo61

Delete Cancellation Policy

Action

In Make“Use this call to delete a cancellation policy. You must have this scope: 'setup.manage'.”

You delete a cancellation policy you no longer offer, so it stops appearing among the conditions you can attach to rates.

When to use it
You retire a flexible condition at the end of a promotion and want the setup cleaned as part of the same scenario.
Watch out
It requires the setup.manage scope; check first with a read or search module that no rate still depends on it.
apaleo62

Delete City Tax

Action

In Make“Use this call to delete a city tax. You must have at least one of these scopes: 'settings.manage, setup.manage'.”

This removes a city tax definition from apaleo, so it is no longer applied to new stays once the rule has ended.

When to use it
Your municipality drops or replaces a tourist tax and the old definition should go.
Watch out
Scope settings.manage or setup.manage required; to take the tax off one booking only, use the reservation module that removes it.
apaleo63

Delete Company

Action

In Make“Deletes a company. Warning: This operation also removes company from all rate plans if not yet used. The deleted company won't be available in the company VAT report anymore. You must have this scope: 'companies.manage'.”

You delete a company record, a corporate client, when you stop working with it, so staff cannot pick it on new bookings.

When to use it
A corporate account closes and you want apaleo in line with your CRM when the deal is marked lost there.
Watch out
It also removes the company from rate plans where it is not yet used, and it disappears from the company VAT report; scope companies.manage.
apaleo64

Delete Folio

Action

In Make“Deletes a folio. This cannot be undone. You can delete a folio only if it's not a main folio, and the folio is empty (it has no charges, allowance, payments or pending payments). Requires 'allowed action': Delete. You must have this scope: 'folios.manage'.”

This deletes a folio for good, clearing an extra bill that was opened by mistake or is no longer needed.

When to use it
A secondary bill was split off for a colleague who ended up paying nothing, and it clutters the stay.
Watch out
It cannot be undone and only works on an empty, non-main folio: no charges, allowances, payments or pending payments. Scope folios.manage.
apaleo65

Delete Group

Action

In Make“Use this call to delete a group booking. This is only possible as long as no blocks exist that are linked to this group booking You must have at least one of these scopes: 'groups.manage, reservations.manage'.”

You delete a group booking, the umbrella record for a party of guests, when it never turned into held rooms.

When to use it
An option for a wedding or seminar was entered early and the client declined before any rooms were blocked.
Watch out
apaleo only allows it while no block is linked to the group; delete or handle the blocks first. Scope groups.manage or reservations.manage.
apaleo66

Delete Maintenance

Action

In Make“Use this call to delete a maintenance. It is not possible to delete maintenances that started yesterday or earlier. You must have at least one of these scopes: 'maintenances.delete, maintenances.manage'.”

This deletes a planned maintenance, giving a room back to sale when the works it was blocked for are called off.

When to use it
The plumber cancels an intervention booked in your maintenance tool and the room should be sellable again.
Watch out
Maintenances that started yesterday or earlier cannot be deleted; scope maintenances.delete or maintenances.manage.
apaleo67

Delete Multiple Rate Plans

Action

In Make“Use this call to delete multiple rate plans. You must have at least one of these scopes: 'rateplans.delete, setup.manage'.”

You delete several rate plans in a single call, handy when a whole season or promotion is retired at once.

When to use it
A batch of seasonal plans has expired and you want them all gone without one module per plan.
Watch out
The deletion covers every plan you pass, so check the list first; scope rateplans.delete or setup.manage. For a single plan, Delete Rate Plan is simpler.
apaleo68

Delete No Show Policy

Action

In Make“Use this call to delete a no-show policy. You must have this scope: 'setup.manage'.”

This deletes a no-show policy, so a rule you no longer apply to absent guests stops being offered on your rates.

When to use it
You change how you treat no-shows and the old rule must not be picked again by mistake.
Watch out
The connection needs the setup.manage scope; replace the policy on existing rates before removing it.
apaleo69

Delete Rate Plan

Action

In Make“Use this call to delete a rate plan. You must have at least one of these scopes: 'rateplans.delete, setup.manage'.”

You delete one rate plan, the pricing frame of an offer, when that offer ends for good.

When to use it
A package deal stops and its plan should vanish from your channels and setup together.
Watch out
Scope rateplans.delete or setup.manage is required; to remove only some prices and keep the plan, Delete Rates is the right module.
apaleo70

Delete Rates

Action

In Make“Deletes all rates in the specifed time range. You must have at least one of these scopes: 'rates.delete, rates.manage'.”

This clears every rate within a time range you choose, leaving the rate plan itself in place and ready for new prices.

When to use it
A period is closed to sale or will be repriced, and the current prices on those dates must go first.
Watch out
Everything in the range is deleted, not just some days, so set the dates carefully; scope rates.delete or rates.manage.
apaleo71

Delete Service

Action

In Make“Use this call to delete a service. You must have at least one of these scopes: 'services.create, setup.manage'.”

You delete a service from the apaleo catalogue, so an extra you stopped offering can no longer be booked.

When to use it
The spa closes or a shuttle is discontinued, and staff should no longer see it when adding extras.
Watch out
This removes the catalogue entry, not a service already on a stay (that is Delete Service For Reservation); scope services.create or setup.manage.
apaleo72

Delete Service For Reservation

Action

In Make“Removes a service from a reservation. The service will not be removed if it is mandatory, already posted or if the service date is in the past. You must have this scope: 'reservations.manage'.”

This takes a service off one reservation, for instance a breakfast the guest no longer wants, without touching the catalogue.

When to use it
A guest changes plans through your messaging tool and the extra should drop from their stay.
Watch out
apaleo keeps the service if it is mandatory, already posted, or dated in the past; scope reservations.manage.
apaleo73

Delete Sub Account

Action

In Make“Use this call to delete a custom sub-accounts. When you delete a custom sub-account, the corresponding accounting accounts are either archived (if there are some transactions posted), or deleted (if no transactions were posted). You must have at least one of these scopes: 'subledger.manage, setup.manage'.”

You delete a custom sub-account from apaleo's accounting when that revenue line is no longer used.

When to use it
Your chart of accounts is simplified and a dedicated line created earlier becomes redundant.
Watch out
If transactions were posted on it, the linked accounting accounts are archived rather than deleted; scope subledger.manage or setup.manage.
apaleo74

Delete Time Slice Definition

Action

In Make“Use this call to delete a time slice definition. This is only possible if a time slice definition is not in-use You must have at least one of these scopes: 'settings.manage, setup.manage'.”

This removes a time slice definition you no longer sell by, keeping the property settings free of unused options.

When to use it
You tested a day-use slot and dropped it, and the definition should not remain available.
Watch out
apaleo only deletes a definition that is not in use; scope settings.manage or setup.manage.
apaleo75

Delete Unit

Action

In Make“Use this call to delete a unit. You must have at least one of these scopes: 'units.delete, setup.manage'.”

You delete a unit, a single room or space, so it no longer counts in your inventory or gets assigned to guests.

When to use it
A room is merged into a suite or converted into storage, and it has to leave the sellable stock.
Watch out
The connection needs the units.delete or setup.manage scope; to take a room out only for a while, a maintenance fits better.
apaleo76

Delete Unit Attribute

Action

In Make“Deletes unit attribute You must have at least one of these scopes: 'unitattributes.delete, setup.manage'.”

This deletes a unit attribute, one of the labels describing your rooms, when that feature no longer exists or is no longer promoted.

When to use it
The terrace is closed off for good and the attribute should stop showing on the rooms that had it.
Watch out
The connection needs the unitattributes.delete or setup.manage scope.
apaleo77

Delete Unit Group

Action

In Make“Use this call to delete a unit group. You must have at least one of these scopes: 'unitgroups.delete, setup.manage'.”

You delete a unit group, a room category, once that type of room is no longer sold at the property.

When to use it
You stop selling a category after rooms are merged, and it should not be offered anymore.
Watch out
The connection needs the unitgroups.delete or setup.manage scope; move or delete its units and plans first to keep the setup coherent.
apaleo78

Download PDF Invoice

Action

In Make“Gets an invoice PDF file by its ID. Only works for invoices that have already been created using POST /invoices. You must have this scope: 'invoices.read'.”

This fetches the PDF of an issued invoice, as a file the next module can attach to an email or save to your storage.

When to use it
An invoice has just been created and your accountant or the guest should receive the PDF without anyone downloading it by hand.
Watch out
It only works on invoices already created in apaleo; for a draft of a bill, use Download PDF Invoice Preview. Scope invoices.read.
apaleo79

Download PDF Invoice Preview

Action

In Make“Gets a preview invoice PDF for one specific folio. You must have this scope: 'invoices.read'.”

You get a preview PDF of what the invoice for one folio would look like, before the real invoice is issued.

When to use it
The guest asks to check their bill before checkout, or a corporate client wants to validate amounts before the final document.
Watch out
The preview is not an issued invoice, so do not send it as the final one; it covers one folio at a time. Scope invoices.read.
apaleo80

Force Amend Reservation

Action

In Make“Modifies the stay-related data of a reservation. If a reservation is 'Confirmed', you can change all fields. If a reservation is 'InHouse', only changes to future time slices are possible. Changes to reservations that are in the status 'CheckedOut' or 'Canceled' are not possible at all. You must have this scope: 'reservations.force-manage'.”

This changes the stay details of a reservation, such as dates or room category, with the stronger force permission rather than the regular amend.

When to use it
The normal Amend Reservation is refused for a change your team has already approved, and the scenario must push it through.
Watch out
A Confirmed booking can change everything, an InHouse one only future time slices, and CheckedOut or Canceled ones nothing; scope reservations.force-manage.
apaleo81

Force Book Service Reservation

Action

In Make“Use this to book a service for a specific reservation. Please note that when dates are specified, all desired dates must be specified or they will be removed if not posted to the folio. You must have this scope: 'reservations.manage'.”

Adds a service, such as breakfast or parking, to one reservation in apaleo so it shows on the guest's bill.

When to use it
A guest asks for an extra through your web form and the scenario books it straight onto the stay.
Watch out
If you set dates, list every date you want: dates left out are removed when they were not yet posted to the folio. The connection needs the reservations.manage scope.
apaleo82

Force Create Booking

Action

In Make“Creates a booking taking a list of reservations as input You must have at least one of these scopes: 'reservations.force-create, reservations.force-manage'.”

Creates a full booking in apaleo from a list of reservations you pass in, so a group of rooms lands in one place.

When to use it
Your own booking tool or a spreadsheet collects stays and you want them written into apaleo as a single booking.
Watch out
The connection needs reservations.force-create or reservations.force-manage. Map each reservation carefully, since one bundle (one item passed between modules) becomes one whole booking.
apaleo83

Force Create Booking Reservation

Action

In Make“Creates new reservations and adds them to an existing booking taking a list of reservations as input You must have at least one of these scopes: 'reservations.force-create, reservations.force-manage'.”

Adds new reservations to a booking that already exists, instead of opening a second booking for the same guest.

When to use it
A family extends their trip with an extra room and you want it attached to the booking they already hold.
Watch out
You need the ID of the existing booking first, for example from Read Booking. The connection needs reservations.force-create or reservations.force-manage.
apaleo84

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Calls any endpoint of the apaleo API from your scenario, reusing the connection you already created, so nothing is out of reach.

When to use it
The listed modules do not cover what you need, and the apaleo API documentation shows an endpoint that does.
Watch out
You write the request yourself: path, method and body. Test it with Run once and read the returned bundle before building on it.
apaleo85

Move All Charges Folio

Action

In Make“If one of the folios is closed, this action cannot be performed. Only charges that can be moved will be moved. You must have at least one of these scopes: 'charges.move, folios.manage'.”

Moves every movable charge from one folio (the guest's running bill in apaleo) to another in a single step.

When to use it
A guest wants the company to pay the whole stay, and the charges must move to the company folio.
Watch out
The move fails if either folio is closed, and charges that cannot be moved stay where they are. Scope: charges.move or folios.manage.
apaleo86

Move Charges Folio

Action

In Make“If one of the folios is closed, this action cannot be performed. If any of the specified charges does not exist, this action cannot be performed. Moving negative charges to a house folio is not supported. Create additional folios instead, and move the charges there. You must have at least one of these scopes: 'charges.move, folios.manage'.”

Moves only the charges you pick from one folio to another, leaving the rest of the bill untouched.

When to use it
Room nights go to the employer while the minibar stays on the guest's own folio.
Watch out
One unknown charge ID blocks the whole move, and so does a closed folio. Negative charges cannot go to a house folio: create an extra folio and move them there.
apaleo87

Move Charges For Multiple Folios

Action

In Make“If one of the folios is closed, this action cannot be performed. If any of the specified charges does not exist, this action cannot be performed. Moving negative charges to a house folio is not supported. Create additional folios instead, and move the charges there. You must have this scope: 'folios.manage'.”

Handles several charge transfers at once, across more than one folio, instead of calling Move Charges Folio again and again.

When to use it
A group checks out and many bills need the same cleanup before invoicing.
Watch out
Same rules as the single version: closed folios and missing charges stop it, and negative charges cannot land on a house folio. Scope: folios.manage only.
apaleo88

Move Payments Folio

Action

In Make“Move payments from one folio of a reservation to another - moving between different reservations is not supported, and will lead to an error. If one of the folios is closed, this action cannot be performed. The PSP reference, if present, will be removed when moving and only be persisted on the original payment. You must have at least one of these scopes: 'charges.move, folios.manage'.”

Moves payments from one folio to another inside the same reservation, so money sits on the bill it belongs to.

When to use it
A deposit was recorded on the wrong folio of a stay and you want to fix it before checkout.
Watch out
Moving to a different reservation throws an error. The PSP reference stays on the original payment only, and closed folios block the move.
apaleo89

Patch Age Category

Action

In Make“Here is the list of operations that are currently allowed: - Replace name, minimum age and maximum age You must have at least one of these scopes: 'settings.manage, setup.manage'.”

Updates an age category in apaleo: its name and the minimum and maximum ages it covers.

When to use it
Your child pricing changes and the age brackets in apaleo must follow the new grid.
Watch out
Nothing else about the category can be changed here. The connection needs settings.manage or setup.manage, which a read-only app account will not have.
apaleo90

Patch Block

Action

In Make“You can replace From, To, GrossDailyRate and BlockedUnits You must have at least one of these scopes: 'blocks.manage, reservations.manage'.”

Changes a room block, the rooms you hold back for an event or a group: its dates, the gross daily rate or the number of blocked units.

When to use it
An organizer confirms fewer attendees and you shrink the block before those rooms go unsold.
Watch out
Only those four elements can be replaced. Scope: blocks.manage or reservations.manage.
apaleo91

Patch Booking

Action

In Make“Here is the list of operations that are currently allowed: - Add, replace and remove PaymentAccount - Add, replace and remove Comment - Add, replace and remove BookerComment - Copy PaymentAccount, Comment and BookerComment from the booking to any reservation, or the other way around - Replace Booker You must have this scope: 'reservations.manage'.”

Edits a booking as a whole: the payment account, the internal comment, the booker's comment, or the booker themselves.

When to use it
A travel agent sends a corrected card or a note, and you want it on the booking rather than on each stay.
Watch out
It can also copy the payment account and comments between the booking and its reservations, in either direction, so pick the direction carefully. Scope: reservations.manage.
apaleo92

Patch Cancellation Policy

Action

In Make“Here is the list of operations that are currently allowed: - Replace name and description - Replace the period from reference - Replace the reference - Replace the fee details: fixed and percent values You must have at least one of these scopes: 'settings.manage, setup.manage'.”

Rewrites a cancellation policy: name, description, the reference moment and period, and the fixed or percentage fee.

When to use it
Your terms change and every rate plan using this policy must follow.
Watch out
Each rate plan tied to the policy picks up the change, so check which ones use it with Read Cancellation Policy first. Scope: settings.manage or setup.manage.
apaleo93

Patch Capture Policy

Action

In Make“Here is the list of operations that are currently allowed: - Replace captureNoShowFee flag - Replace captureCancellationFee flag - Replace capturePrepayment flag - Replace PostOtaBankTransferOnCheckOut flag - Replace capturePayment configuration You must have at least one of these scopes: 'settings.manage, setup.manage'.”

Switches the flags that decide what apaleo charges automatically: no-show fees, cancellation fees, prepayments and the payment capture setup.

When to use it
You decide to stop charging no-show fees automatically at one property.
Watch out
These settings touch real money on real cards, so run the scenario once on a test property first. Scope: settings.manage or setup.manage.
apaleo94

Patch City Tax

Action

In Make“Here is the list of operations that are currently allowed: - Replace name and description - Replace value and type - Replace or delete the VAT type You must have at least one of these scopes: 'settings.manage, setup.manage'.”

Adjusts a city tax: name, description, value and type, or its VAT type, which you can also delete.

When to use it
The city votes a new tourist tax and apaleo must charge the new amount.
Watch out
Read the current tax with a search or read module first so you do not overwrite the wrong one. Scope: settings.manage or setup.manage.
apaleo95

Patch Company

Action

In Make“Here is the list of operations that are currently allowed: - Replace name, address, tax ID - Add and remove rate plans You must have this scope: 'companies.manage'.”

Keeps a corporate client up to date: name, address and tax ID, plus the rate plans the company can book.

When to use it
Your CRM marks a new negotiated rate for an account and apaleo should offer it to that company.
Watch out
The connection needs companies.manage. Adding a rate plan here does not change the plan itself, only who may use it.
apaleo96

Patch Folio

Action

In Make“Here is the list of operations that are currently allowed: - Replace debitor (for guest folios only) - Add a company (not for house folios) - Replace/remove a company (not for house folios) You must have this scope: 'folios.manage'.”

Changes who a folio is billed to: the debitor on a guest folio, or the company attached to it.

When to use it
A guest says at checkout that the invoice should go to their employer.
Watch out
The debitor can only be replaced on guest folios, and companies cannot be set on house folios. Scope: folios.manage.
apaleo97

Patch Group

Action

In Make“Here is the list of operations that are currently allowed: - Add and replace Name - Add, replace and remove Comment - Add, replace and remove BookerComment - Add, replace and remove PaymentAccount - Add, replace and remove PropertyIds - Replace Booker You must have at least one of these scopes: 'groups.manage, reservations.manage'.”

Edits a group booking: its name, comments, payment account, the properties it spans and the booker.

When to use it
A conference moves part of its attendees to a second hotel and the group must cover both properties.
Watch out
Name can be added or replaced but not removed, unlike the comments. Scope: groups.manage or reservations.manage.
apaleo98

Patch Invoice Address

Action

In Make“Here is the list of operations that are currently allowed: - Replace AddressLine1 - Add, replace or delete AddressLine2 - Replace PostalCode - Replace City - Replace CountryCode You must have at least one of these scopes: 'setup.manage, settings.manage'.”

Corrects the address printed on your invoices: street lines, postal code, city and country code.

When to use it
Your company moves offices and every new invoice must carry the new address.
Watch out
Only the second address line can be deleted; the others are replaced. Scope: setup.manage or settings.manage.
apaleo99

Patch Maintenance

Action

In Make“You can only change maintenances which are in the future or still ongoing today. Here is the list of operations that are currently allowed: - Add, replace and remove Description - Replace From and To. 'From' cannot be changed, if the maintenance started yesterday or before. You must have this scope: 'maintenances.manage'.”

Updates a maintenance slot on a unit: its description and its start and end.

When to use it
The plumber finishes early and the room can go back on sale sooner.
Watch out
Past maintenances cannot be changed, and the start stays fixed once the work began yesterday or earlier. Scope: maintenances.manage.
apaleo100

Patch multiple Rate Plans

Action

In Make“Here is the list of operations that are currently allowed: - Replace Name - Replace Description - Replace MinGuaranteeType - Replace PriceCalculationMode - Replace CancellationPolicy - Replace NoShowPolicy - Replace ChannelCodes - Replace Companies - Add, replace and remove PromoCode - Add, replace and remove Restrictions - Add, replace and remove BookingPeriods - Add, replace and remove IsSubjectToCityTax - Add, replace and remove PricingRule - Add, replace and remove Surcharges - Add, replace and remove AgeCategories - Add, replace and remove IncludedServices - Add/Replace/Remove/Update AccountingConfigs You must have at least one of these scopes: 'rateplans.manage, setup.manage'.”

Updates several rate plans in one call: names, policies, channel codes, restrictions, surcharges, included services and more.

When to use it
You add breakfast to every flexible rate across the property without opening each plan.
Watch out
Every plan in the call receives the same change, so filter with Search Rate Plans before mapping. Scope: rateplans.manage or setup.manage.
apaleo101

Patch multiple units

Action

In Make“Here's a list of allowed operations: - Set unit condition - Set unit description - Set unit name - Set unit unitGroupId - Set unit maxPersons - Add unit attribute - Remove unit attribute You must have at least one of these scopes: 'units.manage, setup.manage'.”

Changes many units (rooms, in apaleo terms) in one call: condition, name, description, unit group, maximum guests and attributes.

When to use it
Housekeeping marks a whole floor as clean and you want apaleo to reflect it at once.
Watch out
Use Patch Unit for a single room. Scope: units.manage or setup.manage.
apaleo102

Patch No Show Policy

Action

In Make“Here is the list of operations that are currently allowed: - Replace name and description - Replace the fee details: fixed and percent values You must have at least one of these scopes: 'settings.manage, setup.manage'.”

Edits a no-show policy: its name and description, and the fixed or percentage fee charged when a guest never arrives.

When to use it
Your management raises the no-show fee and the policy must match the new terms.
Watch out
Only these elements are editable. Scope: settings.manage or setup.manage.
apaleo103

Patch Property

Action

In Make“Here's a list of allowed operations: - Replace Name - Add, replace and remove Description - Replace CompanyName - Add, replace and remove ManagingDirectors - Replace CommercialRegisterEntry - Replace TaxId - Replace Location - Add, replace and remove BankAccount - Replace PaymentTerms - Set IsTemplate You must have at least one of these scopes: 'properties.manage, setup.manage'.”

Maintains a hotel's master data in apaleo: name, legal company name, directors, tax ID, location, bank account and payment terms.

When to use it
The legal entity behind a property changes and invoices must show the new details.
Watch out
It can also flag a property as a template, which is easy to set by mistake when mapping. Scope: properties.manage or setup.manage.
apaleo104

Patch Rates

Action

In Make“Note that the specified PATCH operations are applied to each and every rate for the specified time range. Here is the list of operations that are currently allowed: - Add, replace and remove Price - Add, replace and remove Restrictions You must have this scope: 'rates.manage'.”

Sets prices and restrictions on the rates of a plan for the time range you choose.

When to use it
Your revenue sheet decides a new price for a festival weekend and apaleo should apply it.
Watch out
The change hits every rate in that range, not just one night, so check the dates twice. Scope: rates.manage.
apaleo105

Patch Reservation

Action

In Make“Here is the list of operations that are currently allowed: - Add, replace and remove Comment - Add, replace and remove GuestComment - Add, replace and remove PaymentAccount - Add, replace and remove TravelPurpose - Add, replace and remove AdditionalGuests - Add a company (using company/Id, and only if not already set) - Add, replace and remove Commission - Replace PrimaryGuest - Remove ValidationMessages You must have this scope: 'reservations.manage'.”

Edits one stay: comments, guest comment, payment account, travel purpose, extra guests, commission or the primary guest.

When to use it
A guest fills in your pre-arrival form and their details should land on the reservation.
Watch out
A company can only be added if none is set yet. Scope: reservations.manage.
apaleo106

Patch Service

Action

In Make“Here is the list of operations that are currently allowed: - Replace Name - Replace Description - Replace DefaultGrossPrice - Replace PricingUnit - Replace PostNextDay - Replace Availability - Add/Replace/Remove/Update AccountingConfigs - Replace ChannelCodes You must have at least one of these scopes: 'services.manage, setup.manage'.”

Adjusts an extra you sell, such as parking: name, description, default gross price, pricing unit, availability and channel codes.

When to use it
The breakfast price goes up and every channel should show the new amount.
Watch out
The accounting setup can be changed here too, so involve whoever owns your books. Scope: services.manage or setup.manage.
apaleo107

Patch Sub Account

Action

In Make“Allows to modify the name of the sub-account. You must have at least one of these scopes: 'subledger.manage, setup.manage'.”

Renames a sub-account in apaleo's accounting, and nothing more. Handy when labels in apaleo drift away from those in your finance tool.

When to use it
Your finance team renames its ledger codes and apaleo should use the same labels.
Watch out
Anything beyond the name needs another module or Make an API Call. Scope: subledger.manage or setup.manage.
apaleo108

Patch Time Slice Definition

Action

In Make“Use this call to modify a time slice definition of the property. Here is the list of operations that are currently allowed: - Replace Name - Replace CheckInTime (only possible if the time slice definition is not in-use) - Replace CheckOutTime (only possible if the time slice definition is not in-use) You must have at least one of these scopes: 'settings.manage, setup.manage'.”

Changes a time slice definition of a property: its name and its check-in and check-out times.

When to use it
The hotel moves check-in later and the definition in apaleo must match.
Watch out
Check-in and check-out times can only be changed while the definition is not in use. Scope: settings.manage or setup.manage.
apaleo109

Patch Unit

Action

In Make“Here's a list of allowed operations: - Set unit condition - Set unit description - Set unit name - Set unit unitGroupId - Set unit maxPersons - Add unit attribute - Remove unit attribute You must have at least one of these scopes: 'units.manage, setup.manage'.”

Updates a single room: its condition, name, description, unit group, maximum guests or attributes.

When to use it
A housekeeper reports one room as dirty through a form and apaleo should know.
Watch out
For several rooms at once, Patch multiple units saves operations (one run of one module, what Make counts). Scope: units.manage or setup.manage.
apaleo110

Patch Unit Attribute

Action

In Make“Here's a list of allowed operations: - Replace / Remove Description You must have at least one of these scopes: 'unitattributes.manage, setup.manage'.”

Replaces or removes the description of a unit attribute, such as a sea view label. Guests see the result wherever apaleo shows that feature, so the wording stays consistent without editing each room by hand.

When to use it
Your marketing team rewrites how room features are described.
Watch out
Only the description is editable. Scope: unitattributes.manage or setup.manage.
apaleo111

Patch Unit Group Availability

Action

In Make“You can replace AllowedOverbooking for a unit group You must have this scope: 'availability.manage'.”

Sets how much overbooking apaleo allows on a unit group, a category of rooms. It gives your team a lever on how many extra bookings a category accepts.

When to use it
Your team decides to allow a little overbooking on standard rooms when cancellations run high.
Watch out
This is the only value the module changes. Scope: availability.manage.
apaleo112

Pay Invoice

Action

In Make“Settles the invoice, if the invoice has an amount to be paid (total != 0). You must have this scope: 'invoices.manage'.”

Marks an invoice as settled in apaleo once there is an amount left to pay.

When to use it
Your accounting tool confirms a bank transfer and the invoice should close on the apaleo side.
Watch out
An invoice with a total of zero has nothing to settle. Scope: invoices.manage.
apaleo113

Post Charges Folio

Action

In Make“Use this call for cases when the folio should be closed early. For example, when a guest wants to get the invoice right after the check-in As posting charges before the service is delivered is potentially risky, this operation will fail if there are any unposted charges further in the future than 7 days. Posting open charges is only possible for fully prepaid folios. Requires 'allowed action': PostOpenCharges. You must have this scope: 'folios.manage'.”

Posts the open charges of a folio ahead of time so it can close early, for example when a guest wants the invoice right after check-in.

When to use it
A business guest needs the invoice on day one for an expense report.
Watch out
It works only on fully prepaid folios, fails if open charges sit more than 7 days ahead, and needs the allowed action PostOpenCharges. Scope: folios.manage.
apaleo114

Read Account

Action

In Make“Returns one account, as specified by its number and the property. You must have at least one of these scopes: 'subledger.read, accounting.read'.”

Fetches one accounting account of a property, identified by its number. The account comes back as one bundle you can map into later modules.

When to use it
A report scenario needs the label of an account before writing to your finance sheet.
Watch out
You need both the account number and the property. Scope: subledger.read or accounting.read.
apaleo115

Read Age Category

Action

In Make“Get an age category by id. You must have at least one of these scopes: 'settings.read, setup.read, setup.manage'.”

Returns one age category from its ID, with the ages it covers.

When to use it
You check the child bracket before quoting a family price in your booking tool.
Watch out
You need the category ID, usually from Search Age Categories. Scope: settings.read, setup.read or setup.manage.
apaleo116

Read Arrival Report

Action

In Make“Returns number of arriving guests for a property for a certain month. Only over-night rateplans are considered. Includes statistical information on purpose of travel, and nationality. The data is taken from the primary guest only. The status considered are: in-house, confirmed, and checked out. You must have this scope: 'reports.read'.”

Gives the number of arriving guests at a property for a month, with travel purpose and nationality.

When to use it
Your sales team wants arrival figures in a dashboard.
Watch out
Only overnight rate plans count, only the primary guest's data is used, and only in-house, confirmed and checked-out stays are included. Scope: reports.read.
apaleo117

Read Block

Action

In Make“Retrieves a block, specified by its ID. You must have at least one of these scopes: 'blocks.read, reservations.read, reservations.manage'.”

Retrieves a room block from its ID with its current dates, rate and rooms.

When to use it
Before telling an event organizer how many rooms remain, you check the block.
Watch out
You need the block ID, often from Search Blocks. Scope: blocks.read, reservations.read or reservations.manage.
apaleo118

Read Booking

Action

In Make“Retrieves a booking with all its reservations. You must have at least one of these scopes: 'reservations.read, reservations.manage'.”

Retrieves a booking together with all its reservations in one bundle.

When to use it
A confirmation email should list every room of the booking.
Watch out
The reservations come back grouped, so add an iterator if each stay needs its own action. Scope: reservations.read or reservations.manage.
apaleo119

Read Cancellation Policy

Action

In Make“Get a specific cancellation policy. You must have at least one of these scopes: 'settings.read, setup.read, setup.manage'.”

Returns one cancellation policy with its terms and fees. The terms come back as one bundle, ready to map into an email, a PDF or a message to the guest, without copying anything by hand from apaleo.

When to use it
Your guest emails should quote the exact cancellation terms of the booked rate.
Watch out
You need the policy ID. Scope: settings.read, setup.read or setup.manage.
apaleo120

Read Capture Policy

Action

In Make“Get a specific capture policy. You must have at least one of these scopes: 'settings.read, setup.read, setup.manage'.”

Returns one capture policy, so you see what apaleo charges automatically. Reading it first keeps a record of the current settings, which is handy before any change touches payments or fees.

When to use it
Before editing it with Patch Capture Policy, you log the current setup.
Watch out
You need the policy ID. Scope: settings.read, setup.read or setup.manage.
apaleo121

Read City Tax

Action

In Make“Get a specific city tax. You must have at least one of these scopes: 'settings.read, setup.read, setup.manage'.”

Gives you the full definition of one city tax set up in apaleo, fetched by its ID, so later modules can show or reuse the amount rules without anyone opening the settings screen.

When to use it
A guest message or an internal sheet needs to explain the local tax applied to a stay.
Watch out
Your apaleo app needs settings.read, setup.read or setup.manage, otherwise the call is refused.
apaleo122

Read Company

Action

In Make“Get a company by ID. You must have at least one of these scopes: 'companies.read, companies.manage'.”

Pulls one company record from apaleo by its ID and hands its details to the next module as a bundle (one item passed along the scenario). Handy for corporate bookings where the billing entity matters.

When to use it
A reservation points to a company and you want its data in your CRM or an invoice email.
Watch out
The connection needs companies.read or companies.manage.
apaleo123

Read Current Account

Action

In Make“Retrieves information about the current account. You need to be authorized (no particular scope required)”

Returns the information of the apaleo account your connection is logged into. No ID to type: the module simply reads the account behind the credentials.

When to use it
You want a quick check at the start of a scenario that you are working on the account you expect, not a test one.
Watch out
No particular scope is needed, only a valid authorization.
apaleo124

Read Folio

Action

In Make“Get a folio by ID. You must have at least one of these scopes: 'folios.read, folios.manage'.”

Fetches one folio, the running bill of a stay, by its ID, so you can see what has been charged and paid before sending anything to the guest or to accounting.

When to use it
An instant event tells you a folio changed and you want its current content in the next step.
Watch out
The app requires folios.read or folios.manage.
apaleo125

Read Group

Action

In Make“Retrieves a specific group booking with all its related blocks You must have at least one of these scopes: 'groups.read, reservations.read, reservations.manage'.”

Retrieves one group booking together with all the blocks attached to it. A single call gives you the whole picture of a wedding party or a conference allotment.

When to use it
Your sales team tracks group business outside apaleo and needs the blocks mirrored somewhere they already work.
Watch out
Any of groups.read, reservations.read or reservations.manage works; without them, nothing comes back.
apaleo126

Read Invoice

Action

In Make“Gets invoice data by its ID. Only works for invoices that have already been created using POST /invoices. You must have this scope: 'invoices.read'.”

Loads the data of an existing invoice from its ID. It is the step that lets you forward invoice details to a bookkeeping tool or a shared drive.

When to use it
An invoice has been created and another system should receive its figures.
Watch out
It only works for invoices already created in apaleo, and it needs the invoices.read scope.
apaleo127

Read Invoice Preview

Action

In Make“To see if the invoice creation would be successful, check the warnings. You must have this scope: 'invoices.read'.”

Shows what an invoice would look like before it exists, including warnings that tell you whether creating it would succeed. Think of it as a dry run for billing.

When to use it
You plan to generate invoices from a scenario and want to stop cleanly when a warning appears instead of failing halfway.
Watch out
Read the warnings in the returned bundle; the scope needed is invoices.read.
apaleo128

Read Languages

Action

In Make“Get the language settings You must have at least one of these scopes: 'settings.read, setup.read, setup.manage'.”

Returns the language settings of your apaleo account. Small module, but it tells a scenario which languages the property works with before it picks a message template.

When to use it
Guest communication is multilingual and you want the choice of wording driven by what apaleo is configured for.
Watch out
It asks for settings.read, setup.read or setup.manage.
apaleo129

Read Maintenance

Action

In Make“Get a specific maintenance by ID. You must have at least one of these scopes: 'maintenances.read, maintenances.manage'.”

Gets one maintenance entry by ID, meaning a unit taken out of service, so the housekeeping or technical team can see why a room is blocked and for which stay dates.

When to use it
A maintenance ID arrives from an event and you want to post its details to the team channel.
Watch out
The connection needs maintenances.read or maintenances.manage.
apaleo130

Read No Show Policy

Action

In Make“Get a specific no-show policy. You must have at least one of these scopes: 'settings.read, setup.read, setup.manage'.”

Reads one no-show policy so you know which rule applies when a guest never arrives. Useful before a scenario explains a fee to a guest or to the front desk.

When to use it
A reservation is marked as no-show and you want the matching policy text in the follow-up message.
Watch out
Scopes accepted are settings.read, setup.read or setup.manage.
apaleo131

Read Payment

Action

In Make“Get a payment by its ID You must have at least one of these scopes: 'folios.read, folios.manage'.”

Brings back one payment from its ID with its details, so a scenario can confirm what was actually collected on a folio before reporting it elsewhere.

When to use it
Finance wants each payment copied to a spreadsheet or an accounting tool once it is recorded.
Watch out
You need folios.read or folios.manage on the apaleo app.
apaleo132

Read Property

Action

In Make“Get a property by id. You need to be authorized (no particular scope required)”

Returns one property by ID. For groups running several hotels in one apaleo account, it is how a scenario learns which building a reservation belongs to.

When to use it
You route alerts or reports per hotel and need the property details to label them.
Watch out
Any authorized connection can call it, no specific scope required.
apaleo133

Read Property Settings

Action

In Make“Get base settings for a property. You must have at least one of these scopes: 'settings.read, setup.read, setup.manage'.”

Fetches the base settings of a property. Where Read Property describes the hotel, this one gives the configuration behind it, which later modules can rely on.

When to use it
A scenario must adapt its behaviour to how a given property is set up.
Watch out
The connection needs settings.read, setup.read or setup.manage.
apaleo134

Read Rate Plan

Action

In Make“Get a rate plan by id. To be able to read a corporate rate plan a client must additionaly have 'rateplans.read-corporate' scope assigned. You must have at least one of these scopes: 'rateplans.read, setup.read, setup.manage'.”

Reads a single rate plan by ID, so revenue or distribution teams can check its setup from a scenario before changing prices or publishing it elsewhere.

When to use it
You are about to update rates and want the current plan in hand first.
Watch out
Corporate rate plans also need rateplans.read-corporate, on top of rateplans.read, setup.read or setup.manage.
apaleo135

Read Refund

Action

In Make“Get a refund by its ID You must have at least one of these scopes: 'folios.read, folios.manage'.”

Gets one refund by its ID. With it, a scenario can confirm what money went back to a guest and pass the details to accounting or to the support ticket.

When to use it
A refund was issued and the customer service tool should show it.
Watch out
It requires folios.read or folios.manage.
apaleo136

Read Reservation

Action

In Make“Retrieves a reservation, specified by its ID. You must have at least one of these scopes: 'reservations.read, reservations.manage'.”

Retrieves a reservation from its ID with everything apaleo holds on it. Placed right after Watch apaleo Events, it turns the reservation ID into a complete record that later modules can map.

When to use it
You react to a booking event and need guest, dates and status for the next steps.
Watch out
The scope is reservations.read or reservations.manage.
apaleo137

Read Revenue Report

Action

In Make“You must have this scope: 'reports.read'.”

Runs the apaleo revenue report and returns its figures as data a scenario can reuse. It spares someone the export and copy-paste into a spreadsheet or a dashboard.

When to use it
Management wants revenue numbers pushed to the tool they already read.
Watch out
The only scope accepted is reports.read.
apaleo138

Read Schema

Action

In Make“Returns the schema of subledger, split into global and guest ledger. You must have at least one of these scopes: 'subledger.read, accounting.read'.”

Returns the structure of the subledger, split into global and guest ledger. It reads the shape of the accounts rather than the bookings, which helps before mapping entries to your own chart.

When to use it
You connect apaleo accounting to another finance system and need to match both sides.
Watch out
It needs subledger.read or accounting.read.
apaleo139

Read Service

Action

In Make“Get a specific service. You must have at least one of these scopes: 'services.read, setup.read, setup.manage'.”

Gets one service, such as an extra sold with a stay, by its ID. The scenario then knows what the add-on is before it mentions it to a guest or books it.

When to use it
An upsell flow must describe the extra correctly in its message.
Watch out
Accepted scopes are services.read, setup.read or setup.manage.
apaleo140

Read Sub Account

Action

In Make“Get a sub-account by ID. You must have at least one of these scopes: 'subledger.read, setup.read, setup.manage'.”

Reads one sub-account of the subledger by ID. It helps you label postings with the right account before sending them to your own books.

When to use it
You export entries and each line must carry its apaleo account details.
Watch out
Scopes: subledger.read, setup.read or setup.manage.
apaleo141

Read Time Slice Definition

Action

In Make“Get a specific time slice definition for a property. A time slice definition specifies the pattern for recurring time slots. The time slots define when reservations in the property can start or end. It is used in the rate plans when managing prices for renting out the units. You must have at least one of these scopes: 'settings.read, setup.read, setup.manage'.”

Returns one time slice definition, the pattern that tells apaleo when a stay can start or end in a property. Rate plans rely on it for pricing units.

When to use it
You prepare a rate update and must know the slots your dates have to match.
Watch out
It needs settings.read, setup.read or setup.manage.
apaleo142

Read Unit

Action

In Make“Get a unit by id. You must have at least one of these scopes: 'units.read, setup.read, setup.manage'.”

Fetches one unit, a room or apartment in apaleo terms, by its ID, so a scenario can name it properly in a housekeeping note or a guest message.

When to use it
A reservation gets a unit assigned and the team should know which one.
Watch out
The connection needs units.read, setup.read or setup.manage.
apaleo143

Read Unit Attribute

Action

In Make“Get unit attribute by id You must have at least one of these scopes: 'unitattributes.read, setup.read, setup.manage'.”

Reads one unit attribute by ID, the kind of label that describes a feature of a room. It lets a scenario explain what a guest actually gets.

When to use it
A confirmation email should mention the features attached to the assigned unit.
Watch out
It accepts unitattributes.read, setup.read or setup.manage.
apaleo144

Read Unit Group

Action

In Make“Get a unit group by id. You must have at least one of these scopes: 'unitgroups.read, setup.read, setup.manage'.”

Returns one unit group, the category that bundles similar rooms, by ID. Revenue and distribution flows use it to know which category a price or an availability applies to.

When to use it
You sync room categories with another channel or report per category.
Watch out
Scopes: unitgroups.read, setup.read or setup.manage.
apaleo145

Release Block

Action

In Make“Release a specific block which is in status 'Definite'. This changes the status to 'Tentative'. You must have at least one of these scopes: 'blocks.manage, reservations.manage'.”

Moves a block from Definite back to Tentative. The allotment stays in apaleo, but it is no longer firmly committed, which gives sales room to renegotiate.

When to use it
A group contract is back under discussion and the block should reflect it.
Watch out
It only acts on blocks in status Definite and needs blocks.manage or reservations.manage.
apaleo146

Remove City Tax Reservation

Action

In Make“Use this is you want to remove the city tax from a reservation before the stay. You must have this scope: 'reservations.manage'.”

Takes the city tax off a single reservation. The stay keeps everything else; only the tax line is dropped, for guests who are exempt.

When to use it
Your team confirms an exemption and wants apaleo corrected without manual edits.
Watch out
It is meant for use before the stay, and it needs reservations.manage.
apaleo147

Reopen Folio

Action

In Make“Reopens a closed folio. You can only reopen a folio if no invoice has been created for the folio. Otherwise, use `invoice-actions/{invoiceId}/cancel` endpoint to cancel an invoice and reopen the folio. Requires 'allowed action': Reopen. You must have this scope: 'folios.manage'.”

Opens a closed folio again so charges or payments can be corrected. A scenario can do it right after someone flags a billing mistake.

When to use it
A guest disputes an item after checkout and the folio needs another pass.
Watch out
It fails if an invoice already exists for the folio; cancel that invoice first. It needs folios.manage and the Reopen allowed action.
apaleo148

Set Live Current Account

Action

In Make“Move the current account to live. This changes the account type to 'Live'. You must have this scope: 'account.manage'.”

Switches the current apaleo account to the Live type. This is an account-level change, not a booking one, so it belongs in onboarding scenarios rather than daily flows.

When to use it
Your setup process ends with taking a new account live once checks pass.
Watch out
It needs account.manage; test with care, the change affects the whole account.
apaleo149

Set Reservation to No Show

Action

In Make“Set a specific reservation to No-show which is in status 'Confirmed' and where the arrival date is in the past. This changes the status to 'NoShow', and sets the no-show date and time. You must have this scope: 'reservations.manage'.”

Marks a reservation as NoShow and records the no-show date and time. That status is what lets the no-show policy and any fee follow the right path.

When to use it
Guests did not turn up and the front desk wants the status set from a list rather than one by one.
Watch out
Only Confirmed reservations whose arrival date has passed qualify; scope reservations.manage.
apaleo150

Splt Charge Folio

Action

In Make“You must have at least one of these scopes: 'allowances.post, charges.create, folios.manage'.”

Splits a charge on a folio, so one line can be shared out instead of billed as a whole. Useful when two parties pay for the same item. The module name is spelled Splt in Make, so search for that.

When to use it
A shared dinner or a company that covers only part of an item needs the charge divided.
Watch out
Accepted scopes: allowances.post, charges.create or folios.manage.
apaleo151

Splt Payment Folio

Action

In Make“You must have at least one of these scopes: 'payments.create, refunds.create, folios.manage'.”

Divides a payment recorded on a folio. It is the payment-side twin of Splt Charge Folio and helps when one amount received must be spread differently.

When to use it
A single transfer covers several parts of a stay and your records must show each part.
Watch out
It needs payments.create, refunds.create or folios.manage.
apaleo152

Suspend Current Account

Action

In Make“Suspends the current account. This changes the account type to 'Suspended'. You must have this scope: 'account.manage'.”

Sets the current apaleo account to the Suspended type. It is an administrative switch for the whole account, with nothing to do with individual guests.

When to use it
A partner process must put an account on hold after a decision made elsewhere.
Watch out
It requires account.manage, and a Run once test executes it for real, so check which account the connection points to.
apaleo153

Unassign Units Reservation

Action

In Make“Unassigns units for all time slices of the given reservation. If no units are assigned for the reservation nothing will happen. It will fail for reservations in status 'CheckedOut'. You must have at least one of these scopes: 'reservations.assign-unit, reservations.manage'.”

Removes every unit assigned to a reservation across its time slices, so the booking goes back to having no room attached. If nothing was assigned, it does nothing.

When to use it
You want to reshuffle room allocation and free the units first.
Watch out
It fails for reservations already CheckedOut; scopes reservations.assign-unit or reservations.manage.
apaleo154

Update Current Account

Action

In Make“Completely replaces an account with the new definition passed in. The old data will be lost. You must have this scope: 'account.manage'.”

Replaces the definition of the current account with the one you send. Every field you leave out is lost, so it rewrites rather than tweaks.

When to use it
An admin scenario keeps account details aligned with a master record held elsewhere.
Watch out
Map every field, even unchanged ones, since the old data disappears; scope account.manage.
apaleo155

Update Invoice Address

Action

In Make“If the address does not exist for one of the specified properties, it is created. If it exists, it is completely replaced. You must have at least one of these scopes: 'setup.manage, settings.manage'.”

Writes the invoice address for the properties you list. Where it is missing, apaleo creates it; where it exists, the new one fully replaces it.

When to use it
The company changed its billing address and every hotel should show the new one.
Watch out
Send the complete address each time; scopes setup.manage or settings.manage.
apaleo156

Update Languages

Action

In Make“Use this call to modify the language settings of the account. You must have at least one of these scopes: 'settings.manage, setup.manage'.”

Changes the language settings of your apaleo account. Pair it with Read Languages to check the current state before you modify anything.

When to use it
You open a new market and want the account configured through a controlled scenario.
Watch out
It asks for settings.manage or setup.manage.
apaleo157

Update Night Audit

Action

In Make“The night audit will post all charges for services that were delivered on the past business day in the folio and set all occupied rooms to 'Dirty' You must have at least one of these scopes: 'operations.manage, operations.trigger-night-audit'.”

Launches the night audit: apaleo posts the charges of services delivered on the past business day to their folios and flags occupied rooms as Dirty.

When to use it
You want the audit started by a scenario tied to your own closing routine instead of a click.
Watch out
It changes folios and room states at once; scopes operations.manage or operations.trigger-night-audit.
apaleo158

Update Rate Plan

Action

In Make“Use this call to modify a rate plan. You must have at least one of these scopes: 'rateplans.manage, setup.manage'.”

Modifies an existing rate plan. It changes the plan itself, while prices per date go through Update Rates.

When to use it
A revenue decision in a sheet or a tool should reach the plan setup in apaleo.
Watch out
Read the plan first with Read Rate Plan; scopes rateplans.manage or setup.manage.
apaleo159

Update Rates

Action

In Make“All rates specified in the request will be initialized, or overwritten if they already exist. Make sure that the from and to date and time in the rates match the time slice definition of the rate plan. The easiest way to achieve this is calling the GET /rate-plans/{id}/rates for the time range you want to update and then resend the payload with the set prices and restrictions. You must have this scope: 'rates.manage'.”

Sets prices and restrictions for a rate plan over the dates you send, creating the rates or overwriting the ones already there. It is the pricing workhorse of this app.

When to use it
Prices come from a revenue sheet or tool and must land in apaleo without retyping.
Watch out
Dates and times must match the plan's time slice definition; the safe path is to read the current rates for the range and send them back edited. Scope rates.manage.
apaleo160

Update Unit Group

Action

In Make“Use this call to modify a unit group. You must have at least one of these scopes: 'unitgroups.manage, setup.manage'.”

Edits a unit group, the room category, so its setup matches what you sell. Category names and details stay consistent across channels when one scenario owns the change.

When to use it
A category is renamed or redefined and apaleo should follow.
Watch out
It needs unitgroups.manage or setup.manage.
apaleo161

Update Units Condition

Action

In Make“You must have this scope: 'operations.change-room-state'.”

Changes the housekeeping condition of rooms in apaleo straight from the scenario, so the front desk sees which units are ready without anyone updating the board by hand.

When to use it
A cleaning tool or a form tells Make that a room is done and apaleo should reflect it.
Watch out
The connection needs the operations.change-room-state scope, otherwise the module is refused.
apaleo162

Wash Block

Action

In Make“Wash a specific block which is in status 'Definite'. This releases all unpicked units. You must have at least one of these scopes: 'blocks.manage, reservations.manage'.”

Hands back to general inventory every unit of a confirmed block that nobody has picked up yet, which frees rooms that a group or allotment will not use.

When to use it
A block sits in Definite status and the unused rooms should go back on sale.
Watch out
It only works on a block in Definite status; the connection needs blocks.manage or reservations.manage.
apaleo163

Read Offer Index

Search

In Make“Calculates and returns offers per time slice for a specific rate plan, arrival and departure date. You must have at least one of these scopes: 'offer-index.read, offers.read'.”

Returns the offers of one rate plan split per time slice for an arrival and a departure date, a handy view when a scenario compares prices night by night.

When to use it
The scenario already knows the rate plan and needs its offers slice by slice rather than a flat list.
Watch out
The connection needs offer-index.read or offers.read; for offers across a whole property, Search Offers fits better.
apaleo164

Search Age Categories

Search

In Make“Get the list of age categories. You must have at least one of these scopes: 'settings.read, setup.read, setup.manage'.”

Lists the age categories set up in apaleo, such as children or adults, so the scenario can pick the right category ID before it creates or amends a booking.

When to use it
A later module asks for an age category and the IDs should come from apaleo, not be typed by hand.
Watch out
One of these scopes is required: settings.read, setup.read or setup.manage.
apaleo165

Search Blocks

Search

In Make“Returns a list of all blocks, filtered by the specified parameters. If no parameters are set, returns the entire list. You must have at least one of these scopes: 'blocks.read, reservations.read, reservations.manage'.”

Finds the room blocks held for groups or allotments, filtered by the criteria filled in the module, and hands each block to the next module as its own bundle (one item of data).

When to use it
A scenario must act on several blocks, for example to wash or release the ones that match a filter.
Watch out
With every filter left empty, the module returns the entire list of blocks, which can burn many operations downstream.
apaleo166

Search Bookings

Search

In Make“Returns a list of all bookings, filtered by the specified parameters. If no parameters are set, returns the entire list. You must have at least one of these scopes: 'reservations.read, reservations.manage'.”

Pulls bookings from apaleo, the envelope that holds one or more reservations and the booker's details, filtered by the parameters set in the module.

When to use it
A report or a sync needs the booker side of the stay rather than each reservation line.
Watch out
No filter means the whole list comes back; the connection needs reservations.read or reservations.manage.
apaleo167

Search Cancellation Policies

Search

In Make“Get the list of cancellation policies. You must have at least one of these scopes: 'settings.read, setup.read, setup.manage'.”

Reads the cancellation policies defined in apaleo, so a scenario can show a guest the terms or pick the policy ID a new rate plan should carry.

When to use it
A scenario builds or audits rate plans and has to reference an existing policy by ID.
Watch out
The connection needs settings.read, setup.read or setup.manage; no-show rules live in a separate module.
apaleo168

Search Capture Policies

Search

In Make“Get the list of capture policies. You must have at least one of these scopes: 'settings.read, setup.read, setup.manage'.”

Returns the capture policies of the account, the rules that decide when a guest's payment gets captured, ready to be mapped into rate plan or payment modules.

When to use it
A setup scenario must reuse an existing capture policy instead of creating a duplicate.
Watch out
It only lists the policies; to change one, Patch Capture Policy from another part of the list does the job.
apaleo169

Search Child Accounts

Search

In Make“You must have at least one of these scopes: 'subledger.read, accounting.read'.”

Walks the accounting tree of apaleo and returns the sub-accounts found under a parent account, useful when a finance scenario rebuilds the ledger structure in a spreadsheet.

When to use it
The scenario needs the detail below one account before exporting balances or checking a mapping.
Watch out
Access requires subledger.read or accounting.read, scopes that the apaleo app registration must grant.
apaleo170

Search City Tax

Search

In Make“Get the list of all city taxes. You must have at least one of these scopes: 'settings.read, setup.read, setup.manage'.”

Lists every city tax configured in apaleo, so the scenario knows which tax to add or remove on a reservation without guessing its ID.

When to use it
A module like Add City Tax Reservation comes next and expects the tax ID.
Watch out
The connection needs settings.read, setup.read or setup.manage.
apaleo171

Search Companies

Search

In Make“Get the list of companies. You must have at least one of these scopes: 'companies.read, companies.manage'.”

Finds the corporate customers stored in apaleo, which lets a CRM sync check whether a company already exists before creating it a second time.

When to use it
A new B2B contact lands in another tool and the scenario must match it to an apaleo company.
Watch out
Run it before Create Company to avoid duplicates; the scopes are companies.read or companies.manage.
apaleo172

Search Company Invoices Vat Report

Search

In Make“You must have this scope: 'reports.read'.”

Pulls the VAT report on invoices issued to companies, a ready source for an accountant who wants the figures in a sheet or an email.

When to use it
Tax reporting on corporate stays has to leave apaleo for another tool.
Watch out
The connection must carry the reports.read scope. The doc does not list the report columns, so check them with Run once before mapping.
apaleo173

Search Corporate Codes

Search

In Make“Returns all existing corporate codes that match given criteria. You must have this scope: 'rateplans.read-corporate'.”

Returns the corporate codes that match the criteria set in the module, the codes that unlock negotiated rates for a company's staff.

When to use it
A scenario checks that a code sent by a partner exists before it books a negotiated rate.
Watch out
This module needs the specific rateplans.read-corporate scope, not the regular rate plan scopes.
apaleo174

Search Countries

Search

In Make“Returns a list of ISO country codes that could be used to create properties. You need to be authorized (no particular scope required)”

Gives the ISO country codes apaleo accepts when a property is created, which spares a scenario from sending a country code the system will reject.

When to use it
A Create Property module follows and the country must match what apaleo expects.
Watch out
No particular scope is required, but the connection still has to be authorized.
apaleo175

Search Currencies

Search

In Make“Returns a list of all currencies.”

Returns the list of currencies apaleo knows, a small lookup that keeps amounts and currency codes consistent across the modules of a scenario.

When to use it
A scenario sets up a property or a rate and should validate the currency first.
Watch out
It returns every currency, not a filtered subset: keep only the code you need in the next step.
apaleo176

Search External Accounts

Search

In Make“Returns a list of accounts in one property for a folio. You must have at least one of these scopes: 'subledger.read, accounting.read'.”

Returns the accounts of one property tied to a folio, the invoice record of a guest or company, so finance flows can trace where charges end up.

When to use it
A scenario reconciles a folio with the accounting of the property.
Watch out
It covers one property at a time; the scopes are subledger.read or accounting.read.
apaleo177

Search Folio Logs

Search

In Make“You must have this scope: 'logs.read'.”

Reads the history of changes on folios, which helps explain who moved a charge or closed an invoice record when a figure looks wrong.

When to use it
An audit scenario sends folio changes to a log sheet or a support ticket.
Watch out
The connection needs the logs.read scope, which a standard setup may not grant.
apaleo178

Search Folios

Search

In Make“Allowed actions are only returned, when the list is filtered by reservation ID. You must have at least one of these scopes: 'folios.read, folios.manage'.”

Lists folios, the billing records attached to a reservation or a company, so a scenario can check balances or pick the folio to charge.

When to use it
A checkout flow needs the folio of one reservation before posting charges or closing it.
Watch out
The allowed actions per folio only come back when the list is filtered by reservation ID.
apaleo179

Search Global Accounts

Search

In Make“Returns a list of accounts in one property, having the same global account as parent. You must have at least one of these scopes: 'subledger.read, accounting.read'.”

Returns the accounts of one property that share the same global account as parent, a quick way to read one branch of the ledger.

When to use it
A finance scenario totals everything booked under one global account.
Watch out
One property per call; subledger.read or accounting.read is required.
apaleo180

Search Groups

Search

In Make“Returns a list of all group bookings, filtered by the specified parameters. If no parameters are set, returns the entire list You must have at least one of these scopes: 'groups.read, reservations.read, reservations.manage'.”

Finds group bookings, the stays that bundle many rooms under one organizer, filtered by the parameters filled in the module.

When to use it
A sales scenario follows up with every group arriving under certain conditions.
Watch out
Without filters the entire list comes back; the scopes are groups.read, reservations.read or reservations.manage.
apaleo181

Search Guest Accounts

Search

In Make“Returns a list of accounts in one property for a reservation. You must have at least one of these scopes: 'subledger.read, accounting.read'.”

Returns the accounts of one property linked to a reservation, so a scenario can read what a guest owes on the accounting side.

When to use it
A reconciliation compares the stay of one guest with the ledger.
Watch out
It works per property; the connection needs subledger.read or accounting.read.
apaleo182

Search Invoice Address

Search

In Make“Get the list of all invoice addresses. You must have at least one of these scopes: 'setup.read, setup.manage, settings.read, settings.manage'.”

Lists the invoice addresses stored in the account setup, the details printed on invoices, so a scenario can check or reuse them.

When to use it
A scenario audits the billing identity shown on invoices before an update.
Watch out
One of setup.read, setup.manage, settings.read or settings.manage is needed.
apaleo183

Search Invoices

Search

In Make“Gets the list of all invoices (the metadata only, not the files). You must have this scope: 'invoices.read'.”

Returns the invoices of the account with their metadata, enough to feed an accounting sheet or trigger a follow-up per invoice.

When to use it
A scenario exports invoice data to bookkeeping, then fetches the PDF only where needed.
Watch out
The files are not included; File Invoice Pdf retrieves the document. Scope: invoices.read.
apaleo184

Search Maintenances

Search

In Make“Get a list of maintenances matching your filter. You must have at least one of these scopes: 'maintenances.read, maintenances.manage'.”

Finds the maintenance entries that block or restrict units, matching the filter set in the module, so repairs stay visible outside apaleo.

When to use it
A technical team wants its task tool to mirror the rooms out of order.
Watch out
The connection needs maintenances.read or maintenances.manage.
apaleo185

Search Night Audit Logs

Search

In Make“Returns a log of all night audits Newest log entries are returned first. You must have this scope: 'logs.read'.”

Reads the log of night audits, the closing run that rolls the hotel day forward, with the most recent entries first.

When to use it
A manager wants a message whenever the latest audit shows something to check.
Watch out
The newest entries come first, so limit the results to avoid reading old history; scope logs.read.
apaleo186

Search No Show Policies

Search

In Make“Get the list of no-show policies. You must have at least one of these scopes: 'settings.read, setup.read, setup.manage'.”

Lists the no-show policies of the account, the rules applied when a guest never arrives, to reuse their IDs in rate plan scenarios.

When to use it
A scenario creates a rate plan and must attach an existing no-show policy.
Watch out
Cancellation rules sit in Search Cancellation Policies; this one only covers no-shows.
apaleo187

Search Offers

Search

In Make“Calculates and returns available offers for a specific property, arrival and departure date. You must have at least one of these scopes: 'offers.read, reservations.manage'.”

Calculates what a property can sell for an arrival and a departure date, returning each available offer as a bundle the scenario can price or book.

When to use it
A booking form or chatbot asks for availability and prices across a whole property.
Watch out
The connection needs offers.read or reservations.manage; for a single rate plan, Search Rate Plan Offers is narrower.
apaleo188

Search Offers For Reservation

Search

In Make“Calculates and returns offers for amending a specific reservation. You must have at least one of these scopes: 'offers.read, reservations.manage'.”

Computes the offers available to change an existing reservation, such as new dates, before the scenario amends it.

When to use it
A guest asks to move a stay and the scenario needs a valid offer for the amendment.
Watch out
It answers for one reservation only; to quote a new stay, Search Offers is the right module.
apaleo189

Search Ordered Services Report

Search

In Make“Returns a list of ordered services per day with information about the guest and the reservation this service was ordered for. You must have this scope: 'reports.read'.”

Returns the extra services ordered per day, with the guest and the reservation behind each, a clean feed for the kitchen or the spa.

When to use it
A team needs the list of breakfasts, parkings or extras attached to stays.
Watch out
The report requires the reports.read scope on the apaleo app.
apaleo190

Search Payment Methods

Search

In Make“Returns a list of all supported payment methods.”

Gives the payment methods apaleo supports, a lookup that keeps a payment module from receiving a method it cannot process.

When to use it
A scenario records a payment and must map the method from another tool.
Watch out
It returns every supported method in one go, so map yours in the next step rather than expecting a filter.
apaleo191

Search Payments

Search

In Make“Returns a list of all payments for this folio ordered by creation date, newest first You must have at least one of these scopes: 'folios.read, folios.manage'.”

Lists every payment on one folio, newest first, so a scenario can confirm a guest paid before sending a receipt or closing the folio.

When to use it
A checkout flow checks the latest payment on a folio.
Watch out
It reads one folio at a time; the scopes are folios.read or folios.manage.
apaleo192

Search Promo Codes

Search

In Make“Returns all existing promo codes that match given criteria. You must have this scope: 'rateplans.read-corporate'.”

Returns the promo codes that match the criteria set in the module, so a campaign scenario can check a code before advertising it.

When to use it
A marketing tool shares a code and apaleo must confirm it exists.
Watch out
It needs rateplans.read-corporate, the same scope as corporate codes.
apaleo193

Search Properties

Search

In Make“Get the list of properties. You need to be authorized (no particular scope required)”

Lists the hotels of the account, which gives a multi-property scenario the property IDs most other modules ask for.

When to use it
A scenario loops over every property of a group, or needs one ID to fill a field.
Watch out
No special scope is required, only an authorized connection.
apaleo194

Search Property Performance Report

Search

In Make“The property performance API return you key performance indicator for the selected property like occupancy, ADR and RevPAR. It only considers the originally booked amounts for sold units excluding any additional services or manually posted charges or allowances. The results can be filterd to only show you data for a certain part of the business. For example you can exclude day-use reservations or complimentary rate plans. You must have this scope: 'reports.read'.”

Returns occupancy, ADR and RevPAR for a property, the core figures of hotel revenue, ready to land in a dashboard or a message.

When to use it
A revenue manager wants these indicators outside apaleo, with day-use or complimentary rates filtered out.
Watch out
It counts only the originally booked room amounts, without extra services, manual charges or allowances; scope reports.read.
apaleo195

Search Rate Plan Offers

Search

In Make“Calculates and returns available offers for a specific rate plan, arrival and departure date. You must have at least one of these scopes: 'offers.read, reservations.manage'.”

Calculates the offers of one rate plan for an arrival and a departure date, a focused answer when only one price type matters.

When to use it
A partner sells a single rate and needs its availability.
Watch out
For offers split per time slice, Read Offer Index is the variant; scope offers.read or reservations.manage.
apaleo196

Search Rate Plans

Search

In Make“Get the list of rate plans depending on client scopes. If a client has no additional scopes, only public rate plans are returned. The 'rateplans.read-corporate' scope adds corporate rate plans to the response. You must have at least one of these scopes: 'rateplans.read, setup.read, setup.manage'.”

Lists the rate plans the connection can see, each with its ID, so a scenario can pick the plan to price, update or book.

When to use it
A rate sync must match plan names from a channel tool with apaleo IDs.
Watch out
Without the rateplans.read-corporate scope, only public rate plans come back.
apaleo197

Search Rates

Search

In Make“Returns all rates for a specific rate plan within the specified time range. If a rate has not been initialized, it will still be returned, but anything besides the from and to values will be empty. The time range of a rate is defined by the time slice definition of the rate plan. Time ranges with no initialized rates will not be available for sell. To be able to read rates for a corporate rate plan a client must additionally have the 'rateplans.read-corporate' scope. You must have at least one of these scopes: 'rates.read, rates.manage'.”

Returns the rates of one rate plan over a time range, the prices a scenario can compare, copy to another tool or correct.

When to use it
A scenario checks prices on given dates before Update Rates changes them.
Watch out
A rate never initialized still comes back with empty values, and such periods cannot be sold.
apaleo198

Search Refunds

Search

In Make“Returns a list of all refunds for this folio ordered by creation date, newest first You must have at least one of these scopes: 'folios.read, folios.manage'.”

Lists the refunds recorded on one folio, newest first, so a scenario can confirm money went back before telling the guest.

When to use it
A support flow answers a guest asking whether a refund went through.
Watch out
It reads one folio per call; scopes folios.read or folios.manage.
apaleo199

Search Reservation Logs

Search

In Make“You must have this scope: 'logs.read'.”

Reads the change history of reservations, handy to find out who amended a stay or when a status changed.

When to use it
A support or audit scenario needs the trail behind a disputed reservation.
Watch out
The connection needs logs.read. The doc does not describe the log fields, so inspect them with Run once.
apaleo200

Search Reservations

Search

In Make“Returns a list of all reservations, filtered by the specified parameters. If no parameters are set, returns the entire list. You must have at least one of these scopes: 'reservations.read, reservations.manage'.”

Pulls reservations matching the filters set in the module, each one as a bundle, the usual starting point for guest messages and reports.

When to use it
A scenario must act on every stay that matches a status or a date.
Watch out
Empty filters return the entire list; scopes reservations.read or reservations.manage.
apaleo201

Search Service Availability

Search

In Make“Get the list of available services for a specific property and time period. You must have this scope: 'availability.read'.”

You get the services a property can still sell over a period you choose, one bundle per service, ready to feed a later module.

When to use it
Pick it before offering an extra such as breakfast or parking, so the scenario only proposes what is really open on those dates.
Watch out
The apaleo app behind your connection needs the availability.read scope, otherwise the search returns nothing useful.
apaleo202

Search Service Offers

Search

In Make“You must have at least one of these scopes: 'offers.read, reservations.manage'.”

This search hands back the service offers apaleo can quote, so a scenario can show a guest what extras exist and what they would pay.

When to use it
Reach for it when you build an upsell flow that is not yet tied to a booked stay; for an existing reservation, the next module fits better.
Watch out
It asks for offers.read or reservations.manage on the apaleo side.
apaleo203

Search Service Offers For Reservation

Search

In Make“Calculates and returns service offers for a specific reservation. You must have at least one of these scopes: 'offers.read, reservations.manage'.”

Starting from one reservation, apaleo calculates which service offers apply to that stay and returns them as bundles you can map.

When to use it
Choose it right after a booking arrives through the apaleo trigger, to suggest extras matched to the guest's actual dates.
Watch out
The scope needed is offers.read or reservations.manage; without one of them the module fails.
apaleo204

Search Services

Search

In Make“Get the list of services. You must have at least one of these scopes: 'services.read, setup.read, setup.manage'.”

Here you read the catalogue of services configured in apaleo, the list your team set up, whatever their availability on a given day.

When to use it
Use it to look up the ID of a service before a module that books or edits one, instead of typing IDs by hand.
Watch out
One of services.read, setup.read or setup.manage must be granted to your apaleo app.
apaleo205

Search Services For Reservation

Search

In Make“Returns the services booked for a specific reservation. You must have at least one of these scopes: 'reservations.read, reservations.manage'.”

What a guest already booked on top of the room comes back from this module: the services attached to one reservation.

When to use it
It fits a pre-arrival message or a check of extras before checkout, when you need to know what is on the stay today.
Watch out
Grant reservations.read or reservations.manage, or the list stays out of reach.
apaleo206

Search Service Types

Search

In Make“Returns a list of all supported service types.”

With this search, Make returns every service type apaleo supports, a short reference list rather than your own services.

When to use it
Run it once while designing a scenario, to see the accepted values before you create or filter services elsewhere.
Watch out
It describes types, not the services of a property; for those, Search Services is the right module.
apaleo207

Search Sources

Search

In Make“Returns a list of channels that could be used as a source to create bookings.”

apaleo exposes the channels a booking can come from, and this module lists them so you can tag new bookings correctly.

When to use it
Call it before creating a booking from another tool, so the source you send matches a channel apaleo already knows.
Watch out
The doc names no scope for this search; if the call is refused, check the rights of your apaleo app.
apaleo208

Search Sub Accounts

Search

In Make“Returns a list of all sub-accounts. You must have at least one of these scopes: 'subledger.read, setup.read, setup.manage'.”

Sub-accounts of your apaleo ledger come back as a list, useful when a scenario has to route amounts to the right account.

When to use it
It helps when you prepare an accounting export or a reconciliation and need the account references first.
Watch out
apaleo asks for subledger.read, setup.read or setup.manage on the app.
apaleo209

Search Time Slice Definitions

Search

In Make“Get all time slice definitions for a property. A time slice definition specifies the pattern for recurring time slots. The time slots define when reservations in the property can start or end. They are used in the rate plans when managing prices for renting out the units. You must have at least one of these scopes: 'settings.read, setup.read, setup.manage'.”

You learn the time slots a property allows for a stay to start or end, the pattern that rate plans rely on when prices are set.

When to use it
Look them up before creating or editing a rate plan from Make, so the slot you reference really exists.
Watch out
The scope is settings.read, setup.read or setup.manage; a read-only app is enough.
apaleo210

Search Transactions Export Logs

Search

In Make“Returns the audit log for all exports if accounting data that have been done. You must have this scope: 'logs.read'.”

An audit trail of the accounting exports already done in apaleo is what this search returns, one bundle per export.

When to use it
Pick it to confirm an export ran before a scenario pushes figures to your finance tool, and avoid sending data twice.
Watch out
Only logs.read opens it; the other accounting scopes do not.
apaleo211

Search Unit Attributes

Search

In Make“Get unit attribute list You must have at least one of these scopes: 'unitattributes.read, setup.read, setup.manage'.”

The attributes you defined for rooms and units, such as a view or a feature, come back as a list you can reuse.

When to use it
Use it to fetch the attribute IDs a later module needs when it creates or filters units by feature.
Watch out
Grant unitattributes.read, setup.read or setup.manage, or the search is refused.
apaleo212

Search Unit Availability

Search

In Make“Get the list of available units for a specific property and time period. You must have this scope: 'availability.read'.”

For a property and a date range, apaleo returns the individual units still free, so a scenario knows which room it can offer.

When to use it
It suits a flow that proposes a specific room, for instance after a request lands in a form or a chat tool.
Watch out
Only the availability.read scope works here.
apaleo213

Search Unit Availability For Reservation

Search

In Make“Get the list of available units for a specific reservation and time period. You must have at least one of these scopes: 'availability.read, reservations.manage'.”

Tied to one reservation, this search lists the units free for that stay's period, a shortcut before assigning a room.

When to use it
Chain it before Assign Specific Unit Reservation so the unit you pass is one apaleo will accept.
Watch out
It needs availability.read or reservations.manage.
apaleo214

Search Unit Group Availability

Search

In Make“Get the list of available unit groups for a specific property and time period. You must have this scope: 'availability.read'.”

Instead of single rooms, this module works at the level of room categories and tells you which unit groups stay open over a period.

When to use it
Choose it for a quick view by category, a better fit than unit by unit when you only need to know if a type can be sold.
Watch out
The availability.read scope is required.
apaleo215

Search Unit Groups

Search

In Make“Get the list of unit groups. You must have at least one of these scopes: 'unitgroups.read, setup.read, setup.manage'.”

Every unit group of your apaleo setup is listed, the categories rooms belong to, with the IDs other modules expect.

When to use it
Use it when a scenario must map a category name coming from another app to the matching apaleo group.
Watch out
Grant unitgroups.read, setup.read or setup.manage to the app.
apaleo216

Search Units

Search

In Make“Get the list of units. You must have at least one of these scopes: 'units.read, setup.read, setup.manage'.”

This one returns the units themselves, your rooms or apartments as apaleo knows them, one bundle per unit.

When to use it
It is the base for a housekeeping or maintenance flow that has to loop over rooms and pass each one to another tool.
Watch out
apaleo expects units.read, setup.read or setup.manage.
apaleo217

Search Vat

Search

In Make“Returns a list of all VAT types and percents for a country. Supported: - Belgium (BE) - Botswana (BW) - Cape Verde (CV) - Croatia (HR) - Czech Republic (CZ) - Denmark (DK) - Finland (FI) - France (FR) - without the super-reduced 2.1% VAT - French Polynesia (PF) - Germany (DE) - Morocco (MA) - Netherlands (NL) - Norway (NO) - without the VAT for raw fish supplies - Spain (ES) - South Africa (ZA) - Sweden (SE) - Switzerland (CH) - United Kingdom (GB)”

Asked for a country, apaleo answers with its VAT types and rates, so a scenario can apply the right tax when it prepares a charge.

When to use it
Handy when an invoice or a charge built in Make has to show the correct VAT for the property's country.
Watch out
apaleo only supports a fixed list of countries; check that yours appears in the result before relying on it.
Need help

Need help automating apaleo with Make?

A person reads every message.

FAQ

apaleo and Make: frequent questions

01Is the apaleo Make integration free?
Yes, apaleo is a standard app in Make, so its modules work from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations, one per module run on a bundle. You also need an apaleo developer account, and this page says nothing about apaleo's own pricing.
02What do you need to connect apaleo to Make?
You need an apaleo developer account with the authenticator app set up for multi factor authentication. In that account, register a new app from the Apps menu (Add a new app), fill in the form and save it to get a Client ID and a Client Secret. In Make, add an apaleo module, click Create a connection, paste both values and click Save, then confirm access if apaleo asks. The app you register also defines the scopes, and each module lists the scope it needs, such as reservations.manage or folios.manage.
03Does the apaleo trigger in Make react in real time?
Yes. Watch apaleo Events is an instant trigger: apaleo calls Make through a webhook as soon as an event occurs in your account, so the scenario starts without waiting for the 15 minute default schedule. It is the only trigger among the 218 modules. To set it up, click Create a webhook, then Create a connection. If you would rather work on a schedule, start the scenario with a search module such as Search Reservations and let Make run it at the interval you choose.
04What if an apaleo module you need is missing in Make?
Use Make an API Call. It exists for apaleo and calls any endpoint of the apaleo API from your scenario with the same connection, so the 162 actions and 55 searches are not a ceiling. The apaleo doc gives no numeric limit for these modules. The usual blocker is a missing scope on the app registered in apaleo: each module names the scope it expects, and the connection only does what that app is allowed to do.
05Should you use Make or n8n for apaleo?
It depends on the tool your team already builds in. Make covers apaleo with 218 native modules, including an instant trigger, and adds Make an API Call for the rest of the API. apaleo may also exist as an n8n node, so the fair test is simple: list the reservations, folios and reports your flows need, check that each is covered, and pick the editor your team is comfortable maintaining. The n8n vs Make comparison linked above goes through the criteria.