iGMS publishes a documented public API, but has no MCP server and no Zapier app, despite what several third-party blogs claim. Zapier and Make support exists only as a feature request marked In Review on the iGMS feedback board as of July 2026. So the no-code paths people write about are not available; the API is, and it is the only real route into iGMS data today.
What iGMS actually ships
This page exists mostly to correct the record. Search for iGMS automation and you will find blog posts describing Zapier workflows in confident detail. As of July 2026, there is no iGMS app on Zapier. Zapier and Make support appears only as a feature request marked In Review on the iGMS feedback board.
What does exist is a documented public API with access tokens, covering reservations, properties, and messaging. It is enough to build real tooling on, and a small read-only integration is a short project once you hold a token.
There is also no iGMS MCP server, official or community-built, so agent access means wrapping the API yourself or using a layer that already has.
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_..." }
2. Check how iGMS 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 iGMS
Because iGMS 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/igms/reservations \
-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.
Sources
- iGMS API Documentation, iGMShttps://igms.com/