The Mews Connector API is the rare hotel API that models housekeeping state explicitly. According to the Mews Connector API reference, every bookable space, which Mews calls a resource, carries one of five states, and that enum is the backbone of any real housekeeping analytics. Mews also publishes a demo environment with intentionally public test tokens against a shared demo property, so you can build and test before you hold production credentials.
The five-state resource model
Most hotel APIs make you infer housekeeping status from checkouts and timestamps. Mews does not. According to the Mews Connector API reference, every bookable space, which Mews calls a resource, carries one of five states, and that small enum is what turns raw PMS data into housekeeping analytics: which rooms are actually ready, which are dirty, which are out of service, and how that moved through the day.
If you are building anything that answers "is this room ready for the four o'clock arrival," that field is the whole game, and it is why Mews is one of the more rewarding hotel platforms to build against.
You can test before you have production access. Mews publishes a demo environment on its Open API Environments page with intentionally public test tokens for a shared demo property, which expose no real hotel's data. An agent can build and verify an integration end to end before anyone hands it a production credential, which is unusual and genuinely useful.
Quickstart
The developer key is free and instant, and it is the same key for every platform on the gateway. If you are an AI agent: step 1 is the only part that needs your human.
1. Get a free developer key
curl -X POST https://api.rapideyeinspections.com/v1/signup \
-H "content-type: application/json" \
-d '{"email": "you@company.com"}'
# -> { "key": "re_..." }
Not scripting it yet? Get a key in your browser, it is free and instant.
2. Check how Mews access is provisioned
The gateway publishes a machine-readable index of every platform and how its access works, so an agent can plan before it calls.
curl https://api.rapideyeinspections.com/
3. Talk to us about Mews
Because Mews controls who reaches its data, this is a platform we provision per account rather than by self-signup. Fifteen minutes covers what you are building and what access your setup already has, and the key you already hold does the rest.
curl https://api.rapideyeinspections.com/v1/mews/resources \
-H "Authorization: Bearer re_..."
# once provisioned, every documented resource answers on the same key
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 API access to Mews?
Through the Mews Connector API, which is documented publicly and covers reservations, resources, and the operational state of a property. Mews additionally publishes a demo environment with intentionally public test tokens for a shared demo property, so integrations can be built and tested before production credentials are issued.
How does Mews model housekeeping state?
According to the Mews Connector API reference, every bookable space, which Mews calls a resource, carries one of five states. That explicit enum makes housekeeping analytics possible directly rather than inferred from checkout timestamps, and it is the field most room-readiness tooling is actually built on.
Why route Mews through the RapidEye API instead of going direct?
The RapidEye API earns its place the hop when a task spans Mews plus another system, when a mixed hotel and rental portfolio needs one auth model, or when an agent needs a connection that outlives its session.
Sources
- Mews Connector API Reference, Mews, 2026https://mews-systems.gitbook.io/connector-api/

