# ZimmerStack Connect API > ZimmerStack Connect API v1: connect a property management system or a booking engine to a hotel that runs ZimmerStack. Push room counts, prices and stay rules to every connected OTA; receive OTA bookings, and the bookings of the hotel's own website, by signed webhook; hand a website's own bookings to the ZimmerStack PMS. A write through this API reaches real OTAs within a minute. An AI coding agent should read https://docs.zimmerstack.com/agents.md first: it holds the rules on keys, pacing and writes that keep a hotel's prices safe. ## For AI agents - [AGENTS.md](https://docs.zimmerstack.com/agents.md): the rules for a coding agent, short enough to keep in a repository as AGENTS.md or CLAUDE.md - [The full reference in one file](https://docs.zimmerstack.com/llms-full.txt): every route, field, sample, limit and error code, with the rate-grid code - [OpenAPI 3.1 contract](https://api.zimmerstack.com/api/v1/public/connect-api/contract): generated from the schemas that validate every request - [Webhook contract](https://api.zimmerstack.com/api/v1/public/webhooks/contract): the booking events and their full shape - [The Node package](https://docs.zimmerstack.com/sdk): `npm install @zimmerstack/connect`, the client that keeps the pacing, retry and idempotency rules by itself ## Docs - [Overview](https://docs.zimmerstack.com): What the Connect API is and how the three flows fit together. - [Quickstart](https://docs.zimmerstack.com/quickstart): A key, one request, and the answer that tells you it landed. - [Node package](https://docs.zimmerstack.com/sdk): npm install @zimmerstack/connect: the API from your server, with pacing, safe retries and types built in. - [Authentication & keys](https://docs.zimmerstack.com/authentication): Hotel and company keys, scopes, the address allowlist, rotation. - [Build a rate grid](https://docs.zimmerstack.com/rate-grid): Draw rates, room counts and stay rules on your own screen, and save a change. - [Prices per channel](https://docs.zimmerstack.com/per-ota): A different price on each OTA: read a channel's modifier, set it, send prices again. - [Move a hotel to ZimmerStack](https://docs.zimmerstack.com/switching): From another channel manager, OTA by OTA: who does each step, and no duplicate or missed booking. - [Bookings from the hotel's own website](https://docs.zimmerstack.com/website-bookings): The hotel sells on its own website through our booking engine: how those bookings reach your PMS, and the rule to keep before you push room counts. - [Build with an AI agent](https://docs.zimmerstack.com/ai): AGENTS.md, llms.txt and the whole reference in one file for your coding agent. - [Channel manager](https://docs.zimmerstack.com/channel-manager): Push availability, rates and restrictions from your PMS. - [Meal plans](https://docs.zimmerstack.com/meal-plans): One rate plan per board basis, the meal inside the rate, matched to the OTA rate. - [Bookings](https://docs.zimmerstack.com/bookings): Hand bookings from your own booking engine to the PMS. - [Webhooks](https://docs.zimmerstack.com/webhooks): Receive every OTA booking, change and cancellation, and the hotel's own website bookings. - [Sandbox](https://docs.zimmerstack.com/sandbox): Test keys, a property no channel sees, simulated OTA and website bookings. - [Errors](https://docs.zimmerstack.com/errors): Every refusal code, what it means and what to do. - [Rate limits](https://docs.zimmerstack.com/limits): The budgets, the headers, how to pace, where you stand. - [Security](https://docs.zimmerstack.com/security): What protects your property, and what you must do. - [Postman & samples](https://docs.zimmerstack.com/postman): The generated collection and the sample scripts. - [Changelog](https://docs.zimmerstack.com/changelog): What changed, when. ## Optional - [Postman collection](https://api.zimmerstack.com/api/v1/public/connect-api/postman): generated from the same contract