Docs · Hotelminder

Hotelminder developer documentation

These docs are for advisor-side and boutique-group tooling built on top of the Hotelminder API — the layer that orchestrates modules on a live SiteMinder connection. Everything assumes at least one green property in your Hotelminder dashboard.

Hotelminder API reference

REST endpoints under /hm_v1 for advisor-side tooling and boutique group orchestration. OAuth2, module activation, basket, pilot pack.

Read the doc

Webhooks

Event types under the hm.* namespace, HMAC-SHA256 signing, retry policy with exponential backoff up to 8h.

Read the doc

Rate limits

Per-key and per-property quotas sized for boutique scale — 500 req/min per property, 10 concurrent, X-Hotelminder-RateLimit-* headers.

Read the doc

Error codes

The hm_* error taxonomy with remediation notes. Boutique-shaped guardrails included.

Read the doc

Base URL and versioning

All Hotelminder API endpoints are served from https://api.mindermod.org/hm_v1. The API is path-versioned. When a breaking change lands, a new major version (/hm_v2) ships alongside the current one and both remain live for at least twelve months. Non-breaking additions land in /hm_v1 in place and are announced on the changelog.

Authentication

Every request carries an Authorization: Bearer <hm_access_token> header. Tokens are issued via the OAuth2 flow described in the API reference — one hm_client_id per integration, one scope per module. Rotation is manual and surgical, mirroring the SiteMinder key hygiene we ask boutique properties to follow.

Support for developers

Developer questions land at support@mindermod.org. Every reported bug is triaged internally within one working day by an on-call advisor. There is no public issue tracker.