PriceLabs publishes a self-serve Customer API and an official MCP server, and pricing is still only half of any tool worth building. A revenue dashboard, a discount-approval workflow, an owner report: each one joins PriceLabs data against reservations and occupancy that live in a PMS, and neither API can see the other. The RapidEye API puts both legs behind one key and one schema, with the listing-to-listing mapping between systems handled for you.
How PriceLabs access works
According to PriceLabs, you generate an API key yourself from Account Settings, then API Details, then Get PriceLabs API Key, and authenticate by sending it in the X-API-Key header, which PriceLabs notes is case sensitive. The Customer API lets you receive prices from PriceLabs and edit settings for listings actively syncing prices to a channel or PMS. Full endpoint specifications live in their Swagger documentation, reachable from the same settings page.
PriceLabs also ships an official MCP connector. Per PriceLabs, PriceLabs MCP lets you find listings, analyze performance, and execute pricing actions from chat, and it "currently works with Claude and Grok, with support for more AI assistants coming soon." That is a good way to ask ad-hoc revenue questions in chat. Our PriceLabs MCP setup guide walks through connecting it.
Why build on the RapidEye API
One key, one schema, every platform in your stack.
Real operator tools are never about one system. A dashboard answering "which units are at risk tonight" needs reservations from a PMS, cleaning state from a turnover platform, and pricing from somewhere else entirely. Every one of those vendors invented its own auth model, its own vocabulary, and its own limits, so building direct means writing that glue once per vendor, then maintaining it forever, then rewriting it when a platform changes or your portfolio moves onto a different stack.
Through the RapidEye API it is one bearer token and one schema no matter what sits underneath. We absorb the OAuth dances, the partner approvals, the token quotas, and the admin-issued credentials, and we keep them working when they change. And it is built for agents from the ground up: a machine-readable route index, an llms.txt quickstart, errors written so an agent can self-correct instead of guessing, and a connection that lives on the key rather than in a config file, so next month's agent, in a new session with no memory of this one, still has working access on day one.
Quick FAQ
How do you get a PriceLabs API key?
Yes. PriceLabs publishes a Customer API that lets you retrieve prices and edit settings for listings that are actively syncing prices to a channel or PMS. You generate the key yourself from Account Settings, then API Details, then Get PriceLabs API Key, and authenticate by sending it in the X-API-Key header, which is case sensitive.
Should I use the RapidEye gateway for PriceLabs?
Not for a PriceLabs-only task. PriceLabs access is self-serve and their own MCP covers the chat use case, The gateway is worth the hop when a tool needs PriceLabs data joined with another system, because no single platform's API can answer a question that spans two, and because one key across every platform means one auth model to reason about.
Sources
- Customer API, PriceLabs Help Center, 2026https://help.pricelabs.co/portal/en/kb/articles/pricelabs-api
- PriceLabs MCP and Customer API, AI Connectors and Developer Tools, PriceLabs, 2026https://hello.pricelabs.co/mcp-api-integration/
- Building an API integration with PriceLabs, PriceLabs Help Center, 2026https://help.pricelabs.co/portal/en/kb/articles/building-an-integration-with-pricelabs