Apaleo, worked by an AI employee
Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your Apaleo account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.
- Scheduling & Booking
- Signs in to your account
- 29 ready-made tools
- Asked in Slack or Teams
An illustration of how the conversation reads, not a transcript from a client account.
What Apaleo is
Apaleo is a cloud-based property management platform handling reservations, billing, and daily operations for hospitality businesses
You sign in with your own Apaleo account, the same way you already do. We never see or hold your password.
One message in, the work done in Apaleo.
- 01
You ask
You message your AI employee in the chat your team already has open, in one sentence, in your own words.
- 02
It works out the step
It decides what the job needs in Apaleo. You do not pick anything from a menu or wire anything together.
- 03
It does the work
Signed in to your own Apaleo account, inside the access you granted it, doing the thing you asked for.
- 04
It reports back
It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.
What it can do in Apaleo
These are the ready-made tools your AI employee already has in Apaleo. It is not limited to them, but it never has to be taught these.
- Archive a propertyUse this endpoint to archive an existing live property this operation set the isarchived flag to true<bryou must have at least one of these scopes: 'properties.manage, setup.manage
- Check if a property existsCheck if a property exists by id.<bryou need to be authorized (no particular scope required)
- Check if a unit attribute existsCheck if a unit attribute exists<bryou must have at least one of these scopes: 'unitattributes.read, setup.read, setup.manage'.
- Check if a unit existsCheck if a unit exists by id.<bryou must have at least one of these scopes: 'units.read, setup.read, setup.manage'.
- Check if a unit group existsCheck if a unit group exists by id.<bryou must have at least one of these scopes: 'unitgroups.read, setup.read, setup.manage'.
- Clones a propertyUse this call to clone a specific property. this operation creates a new property with inventory and rate plans from the specified property.<bryou must have at least one of these s
- Create a unitUse this call to create a new unit.<bryou must have at least one of these scopes: 'units.create, setup.manage'.
- Create a unit attributeUse this call to create a new unit attribute.<bryou must have at least one of these scopes: 'unitattributes.create, setup.manage'.
- Create a unit groupUse this call to create a new unit group.<bryou must have at least one of these scopes: 'unitgroups.create, setup.manage'.
- Create multiple unitsUse this call to create multiple units, following a naming rule.<bryou must have at least one of these scopes: 'units.create, setup.manage'.
- Creates a propertyUse this call to create a new property.<bryou must have at least one of these scopes: 'properties.create, setup.manage'.
- Delete a unitUse this call to delete a unit.<bryou must have at least one of these scopes: 'units.delete, setup.manage'.
- Delete a unit groupUse this call to delete a unit group.<bryou must have at least one of these scopes: 'unitgroups.delete, setup.manage'.
- Deletes unit attributeDeletes unit attribute<bryou must have at least one of these scopes: 'unitattributes.delete, setup.manage'.
- Get a properties listGet the list of properties.<bryou need to be authorized (no particular scope required)
- Get a propertyGet a property by id.<bryou need to be authorized (no particular scope required)
- Get a unitGet a unit by id.<bryou must have at least one of these scopes: 'units.read, setup.read, setup.manage'.
- Get a unit groupGet a unit group by id.<bryou must have at least one of these scopes: 'unitgroups.read, setup.read, setup.manage'.
- Get a units listGet the list of units.<bryou must have at least one of these scopes: 'units.read, setup.read, setup.manage'.
- Get unit attribute by idGet unit attribute by id<bryou must have at least one of these scopes: 'unitattributes.read, setup.read, setup.manage'.
- Get unit attribute listGet unit attribute list<bryou must have at least one of these scopes: 'unitattributes.read, setup.read, setup.manage'.
- List Unit GroupsGet the list of unit groups.<bryou must have at least one of these scopes: 'unitgroups.read, setup.read, setup.manage'.
- Move property to liveUse this endpoint to move an existing test property to live this operation changes the property status to 'live'<bryou must have at least one of these scopes: 'properties.manage, s
- Replace a unit groupUse this call to modify a unit group.<bryou must have at least one of these scopes: 'unitgroups.manage, setup.manage'.
- Reset Property DataThis endpoint deletes transactional data for a property in 'test' status. requires 'properties.manage' or 'setup.manage' scopes.
- Return total count of propertiesReturn total count of properties<bryou need to be authorized (no particular scope required)
- Returns a list of supported countriesReturns a list of iso country codes that could be used to create properties.<bryou need to be authorized (no particular scope required)
- Returns number of unit groupsReturns number of unit groups matching the filter criteria<bryou must have at least one of these scopes: 'unitgroups.read, setup.read, setup.manage'.
- Returns number of unitsReturns number of units matching the filter criteria<bryou must have at least one of these scopes: 'units.read, setup.read, setup.manage'.
You stay the boss of your Apaleo account.
Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.
How we handle your data- It signs in to your own Apaleo account. You are not moving anything into ours.
- You grant access one app at a time, and you can take it back the same way.
- Everything it does in Apaleo is written down, with what it did and when.
- Anything you tell it to check with you first, it checks with you first.
It works in Apaleo and the rest of your software in the same job
A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.
Questions people ask about Apaleo
- Can an AI employee really work inside Apaleo?
- Yes. It signs in to your own Apaleo account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
- Do I have to move anything out of Apaleo?
- No. Nothing moves and nothing is replaced. Your records stay in Apaleo, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
- How does it get into my Apaleo account?
- You sign in with your own Apaleo account, the same way you already do. We never see or hold your password. You approve it before anything connects, and you can take the access back the same way you gave it.
- What can it actually do in Apaleo?
- It has 29 ready-made tools in Apaleo today, among them Archive a property, Check if a property exists and Check if a unit attribute exists. The full list is on this page. It is not limited to those, but it never has to be taught them.
- Can it use Apaleo and the rest of my software in the same job?
- Yes, and that is usually the point. Reading a message in one app, checking a record in Apaleo and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
- Who decides what it is allowed to do in Apaleo?
- You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in Apaleo is written down with what it did and when.