What Apaleo scopes does Lyro need?

It varies by action, and Apaleo is explicit about it. Reading properties needs no particular scope, while unit reads require units.read, setup.read, or setup.manage, creating a unit requires units.create or setup.manage, and deleting one requires units.delete or setup.manage. Unit groups and unit attributes have their own equivalents, so a narrowly scoped credential limits Lyro to exactly what you granted.

Can Lyro reset a property's data safely?

Only on a test property. Reset Property Data deletes transactional data for a property in Test status and requires properties.manage or setup.manage, so a live property cannot be wiped this way. Move Property to Live is the one-way step that takes a test property into production.

Does this integration handle reservations and guest billing?

No. The actions here cover property and unit setup - properties, units, unit groups, unit attributes, and their existence checks and counts. Booking, folios, and guest billing stay in Apaleo, and Lyro uses this connection to keep the inventory those bookings depend on correct.

How does Lyro answer a how-many question without listing everything?

There are dedicated count actions. Return Total Count of Properties, Returns Number of Units, and Returns Number of Unit Groups each return a count against the filter criteria, which is faster than paging a full list. Returns a List of Supported Countries gives the ISO codes that a new property can be created with.

Apaleo Integration - Lyro AI Agent

What your agent can do with Apaleo

Every action runs live through MCP. Nothing to build, nothing to maintain.

Reset property data
Lyro deletes transactional data for a Test property to reset your sandbox. Your team cleans up testing data without manual database access.
Clones a property
Lyro clones a specific property in Apaleo to duplicate settings and structure. Your team reuses property templates instead of building from scratch.

See all 29 actions

How businesses use Apaleo + Lyro

Each card is one request a support team gets, and the Apaleo actions Lyro runs to close it.

Report on what the portfolio actually contains
Lyro lists the properties on the account, the units within them, and the unit groups those units belong to, so a question about inventory is answered from the current setup rather than a spreadsheet.
Get Properties ListGet Units ListList Unit Groups
Stand up a property and its rooms
Lyro creates the property, adds a single unit where one is missing, and generates a whole floor of units at once following the naming rule you give it.
Create PropertyCreate UnitCreate Multiple Units
Keep unit groups and attributes consistent
Lyro creates the unit group that room types are organised into, modifies an existing group when the configuration changes, and defines the unit attributes used to describe what a room has.
Create Unit GroupReplace Unit GroupCreate Unit Attribute
Move a property through its lifecycle
Lyro clones an existing property with its inventory and rate plans as the basis for a new one, switches a test property to live status, and archives a property that is no longer trading.
Clone PropertyMove Property to LiveArchive Property

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Apaleo actions it has and picks the ones a request needs.

01
Connect Apaleo
Authorize the Apaleo account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
02
Tell your agent what you need
Describe the job the way you would hand it to a teammate. Lyro maps it to the Apaleo actions that close it and chains as many as the request needs.
03
Watch it work
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started free

Apaleo · Lyro

Everything else about Apaleo

Setup, permissions, and the limits of what Lyro can do inside Apaleo.

It varies by action, and Apaleo is explicit about it. Reading properties needs no particular scope, while unit reads require units.read, setup.read, or setup.manage, creating a unit requires units.create or setup.manage, and deleting one requires units.delete or setup.manage. Unit groups and unit attributes have their own equivalents, so a narrowly scoped credential limits Lyro to exactly what you granted.

Every action available in Apaleo

All 29 actions your agent can call on Apaleo, straight from the live MCP connection.

Archive a property
Use this endpoint to archive an existing live property This operation set the IsArchived flag to true You must have at least one of these scopes: 'properties.manage, setup.manage'.
Check if a property exists
Check if a property exists by id. You need to be authorized (no particular scope required).
Check if a unit attribute exists
Check if a unit attribute exists You must have at least one of these scopes: 'unitattributes.read, setup.read, setup.manage'.
Check if a unit exists
Check if a unit exists by id. You must have at least one of these scopes: 'units.read, setup.read, setup.manage'.
Check if a unit group exists
Check if a unit group exists by id. You must have at least one of these scopes: 'unitgroups.read, setup.read, setup.manage'.
Clones a property
Use this call to clone a specific property.
Create a unit
Use this call to create a new unit. You must have at least one of these scopes: 'units.create, setup.manage'.
Create a unit attribute
Use this call to create a new unit attribute. You must have at least one of these scopes: 'unitattributes.create, setup.manage'.
Create a unit group
Use this call to create a new unit group. You must have at least one of these scopes: 'unitgroups.create, setup.manage'.
Create multiple units
Use this call to create multiple units, following a naming rule. You must have at least one of these scopes: 'units.create, setup.manage'.
Creates a property
Use this call to create a new property. You must have at least one of these scopes: 'properties.create, setup.manage'.
Delete a unit
Use this call to delete a unit. You must have at least one of these scopes: 'units.delete, setup.manage'.
Delete a unit group
Use this call to delete a unit group. You must have at least one of these scopes: 'unitgroups.delete, setup.manage'.
Deletes unit attribute
Deletes unit attribute You must have at least one of these scopes: 'unitattributes.delete, setup.manage'.
Get a properties list
Get the list of properties. You need to be authorized (no particular scope required).
Get a property
Get a property by id. You need to be authorized (no particular scope required).
Get a unit
Get a unit by id. You must have at least one of these scopes: 'units.read, setup.read, setup.manage'.
Get a unit group
Get a unit group by id. You must have at least one of these scopes: 'unitgroups.read, setup.read, setup.manage'.
Get a units list
Get the list of units. You must have at least one of these scopes: 'units.read, setup.read, setup.manage'.
Get unit attribute by ID
Get unit attribute by id You must have at least one of these scopes: 'unitattributes.read, setup.read, setup.manage'.
Get unit attribute list
Get unit attribute list You must have at least one of these scopes: 'unitattributes.read, setup.read, setup.manage'.
List unit groups
Get the list of unit groups. You must have at least one of these scopes: 'unitgroups.read, setup.read, setup.manage'.
Move property to live
Use this endpoint to move an existing test property to live This operation changes the property status to 'Live' You must have at least one of these scopes: 'properties.manage, setup.manage'.
Replace a unit group
Use this call to modify a unit group. You must have at least one of these scopes: 'unitgroups.manage, setup.manage'.
Reset property data
This endpoint deletes transactional data for a property in 'Test' status.
Returns a list of supported countries
Returns a list of ISO country codes that could be used to create properties. You need to be authorized (no particular scope required).
Returns number of unit groups
Returns number of unit groups matching the filter criteria You must have at least one of these scopes: 'unitgroups.read, setup.read, setup.manage'.
Returns number of units
Returns number of units matching the filter criteria You must have at least one of these scopes: 'units.read, setup.read, setup.manage'.
Return total count of properties
Return total count of properties You need to be authorized (no particular scope required).

The tools Apaleo sits next to

Same connection, same setup. Pick the next one your team already uses.

Browse every integration

Apaleo MCP integration

What your agent can do with Apaleo

Reset property data

Clones a property

How businesses use Apaleo + Lyro

Report on what the portfolio actually contains

Stand up a property and its rooms

Keep unit groups and attributes consistent

Move a property through its lifecycle

Get started in 3 steps

Connect Apaleo

Tell your agent what you need

Watch it work

Everything else about Apaleo

Every action available in Apaleo

Archive a property

Check if a property exists

Check if a unit attribute exists

Check if a unit exists

Check if a unit group exists

Clones a property

Create a unit

Create a unit attribute

Create a unit group

Create multiple units

Creates a property

Delete a unit

Delete a unit group

Deletes unit attribute

Get a properties list

Get a property

Get a unit

Get a unit group

Get a units list

Get unit attribute by ID

Get unit attribute list

List unit groups

Move property to live

Replace a unit group

Reset property data

Returns a list of supported countries

Returns number of unit groups

Returns number of units

Return total count of properties

The tools Apaleo sits next to

Appointo

Booqable

Calendly

Eventee

Lodgify

Scheduleonce

Ready to connect Apaleo?