A PMS marketplace listing is one of the few places a hotel goes looking for software with the intent to connect it. The hotelier is already logged into the PMS, already trusts it, and is browsing for a tool that works with it. For a hotel tech vendor, that is warm demand you do not have to create. The catch is that every PMS runs its own gate, with its own registration, certification and costs, and a listing on its own rarely produces leads.

This guide sets out the steps to get listed in a PMS marketplace and then turn the listing into pipeline. It uses only what the marketplaces publish in their own partner documentation: Mews, Cloudbeds, Apaleo and Oracle OPERA Cloud through OHIP, with a note on others. If you are still deciding whether to integrate at all, read build or partner on a hotel tech integration first.

What the main PMS marketplaces ask for

Sources for the table: Hospitality Upgrade on Mews, the Cloudbeds API page, Apaleo's certification guide, Oracle's OHIP FAQs and Oracle's marketplace blog.

The steps at a glance

1. Choose the marketplace where your buyers already are

2. Read the partner terms and costs before you build

3. Register as a partner before writing integration code

4. Build to the certification checklist, not just the API reference

5. Write the listing and onboarding guide before you submit

6. Pass certification and line up a pilot property

7. Turn the listing into leads

8. Keep the integration certified

Step 1: Choose the marketplace where your buyers already are

Start with your pipeline, not the PMS with the biggest logo. Pull your last year of deals and lost deals and count which PMS each property ran. The PMS that appears most in deals you lost for "no integration" is usually your first marketplace. Then check fit with your segment: Cloudbeds says it serves 20,000+ properties, Mews' boilerplate says it powers 15,000 customers across 85 countries, and OPERA Cloud is where most chain and enterprise hotels sit. A boutique group tool and a chain revenue tool will rarely pick the same first PMS. Our comparison of hotel tech marketplaces covers how hoteliers use each one.

Step 2: Read the partner terms and costs before you build

The costs differ more than most vendors expect, so budget before you commit engineering time.

• Mews: the Connector API is described as completely open and self-service, free of charge for integration partners and Mews customers.

• Cloudbeds: the API licence agreement says certification will be at your expense, and that you cannot proceed to the next development phase until certification is complete.

• Apaleo: its certification FAQ says there are no additional costs for certification or store listing.

• Oracle OHIP: the FAQ says OHIP is available only through a paid pay-as-you-go subscription, sandbox calls are billed, there is no free tier for startups, and the owner of the application key pays all API costs. Calls above the 10,000 included each month are billed at approximately USD 20 per 10,000.

For a wider view, the icecreek PMS Integration Tier Map compiles public access terms for European PMS platforms, including Oracle Partner Network membership at 500 USD a year and a 160 EUR certification call for the SIHOT Connectivity Program. Treat it as a secondary source and confirm the figures with each PMS. If integration costs feed into your own pricing, see the Hotel Software Pricing Index for how other vendors package add-ons.

Step 3: Register as a partner before writing integration code

Registration puts you in the PMS's partner database and often decides what access you get. Mews asks that you complete the Marketplace registration form before building, even though its demo sandbox is public. Cloudbeds routes partners through an application before certification. Apaleo's listing guide starts with a developer account and registering a Connect client, because only apps registered with OAuth Authorization Code Grant can have a store listing. For Oracle, a current Oracle Partner Network membership at base level is required before you can post a solution on the marketplace.

Step 4: Build to the certification checklist, not just the API reference

Certification is where most delays come from, and the checklists are published. Apaleo lists its prerequisites plainly: OAuth 2.0 Authorization Code Grant, only the scopes the app genuinely needs, graceful error handling including 404s, correct token refresh after the 3,600 second expiry, webhooks instead of polling, pageSize=200, and end-to-end testing. Mews says certification confirms your API requests are accurate against its specification, judged against the API operations you declare and the flow in its use case guides, and that keeping requests within limits is your responsibility. Build against those lists from day one and certification becomes a review, not a rebuild.

Step 5: Write the listing and onboarding guide before you submit

Apaleo warns that once you submit for certification you cannot edit your listing until the app is published, and its listing editor covers name, description, screenshots, pricing and support links. It also requires an onboarding guide for your product as a certification prerequisite. Write the listing for the hotelier browsing inside their PMS: what the integration does in their daily work, what data flows each way, what it costs, and how long setup takes. Lead with the job, not your company history. The same rules apply as on a good comparison page: specific, scannable, honest about limits.

Step 6: Pass certification and line up a pilot property

Apaleo's certification call asks you to share your screen and walk through three flows: onboarding a new account from scratch, day-to-day operations, and offboarding, while the team monitors your API usage. A pilot customer is recommended but not required. Mews' process, as described in its 1,000-integration announcement, runs from registration to a certification call and finishes with a pilot at a live Mews property. Line up the pilot hotel early, ideally an existing customer already on that PMS, and agree what success looks like. Our guide to running a pilot that converts applies here too.

Step 7: Turn the listing into leads

A listing is shelf space. Leads come from what you do around it. Cloudbeds says certified partners get co-marketing support, early access to new APIs and a dedicated partner success contact. Oracle lists automated lead generation tools and access to Oracle Hospitality's sales teams and global reseller network among its go-to-market catalysts. Ask for these explicitly; they are rarely handed out unprompted.

• Publish an integration page on your own site for each PMS, so hoteliers searching "your product plus PMS name" find you.

• Email every existing customer and open opportunity on that PMS to announce the certified connection.

• Brief the PMS's account managers and onboarding team on which hotels your tool suits, so they can refer you.

• Collect reviews from early users and point them to the listing and to Hotel Tech Report.

• Track marketplace connections as a lead source in your CRM, separate from referrals.

For the joint campaigns that follow a listing, see partner co-marketing with PMS vendors. This is the reach stage of the hotel tech GTM system, and it works because integrations sell hotel software more than feature lists do.

Step 8: Keep the integration certified

Certification is not a one-off. Cloudbeds' terms say significant modifications to your application are subject to re-certification. Apaleo asks partners to tell it about significant changes to use case or requested scopes and to submit a recertification form. Oracle's FAQ says that if a production integration has a major incident and you do not respond to its contact, it will disable the integration. Keep the partner contact details current, assign an owner for each PMS relationship, and review your listing every quarter so pricing and screenshots stay accurate.

If marketplace listings are live but leads are thin, the free GTM leak audit will show whether the gap is the listing, the follow-up or the sales process behind it.

Frequently Asked Questions