← All integrations

Apaleo

29 operations0 webhooks

Open hospitality platform for property management, reservations, and hotel operations.

Supported operations

  • ArchiveWrite

    Archive a live property (sets isArchived to true)

  • CloneWrite

    Clone a property, creating a new property with inventory and rate plans

  • CountRead-only

    Return total count of properties

  • CountriesRead-only

    List ISO country codes that can be used to create properties

  • CreateWrite

    Create a new property

  • ExistsRead-only

    Check if a property exists by id

  • GetRead-only

    Get a property by id

  • ListRead-only

    Get the list of properties

  • ResetWrite

    Delete transactional data for a property in Test status

  • Set LiveWrite

    Move a test property to Live status

FAQ

Install corsair and @corsair-dev/apaleo, add the Apaleo plugin, and connect with OAuth. Then call methods like corsair.apaleo.api.properties.archive() from your app. Corsair stores tokens, and syncs data per tenant.

Yes. Apaleo needs an OAuth app with scopes that match what you automate. Register the app in Apaleo, configure redirect URLs, then connect through Corsair or managed OAuth in Hub.

Yes. One Corsair client can hit Apaleo, GitHub, Notion, Stripe, and the rest. Trigger Apaleo from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for open hospitality platform for property management, reservations, and hotel operations. Common builds include sync jobs, admin tooling, and agents that call Apaleo APIs from your backend. Local DB entities let you query synced Apaleo records without hitting the API on every read.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Apaleo API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/apaleo in the open repo. When Apaleo ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your Apaleo data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Apaleo data on your behalf.