Platform
Open Hotel Protocols
The open interface layer under Nerve — a documented surface, per-operation scopes, and a playground where both the request and the response are real.
Open Hotel Protocols is the commitment that every operation in the product is described, scoped and callable, rather than a screen with an export button behind it. It is the only one of the three pillars whose subject is not a screen — so the honest way to argue it is with a real request, a real response, and the refusal that comes back when a key reaches past its scopes.
A request, a response, and a refusal
The playground runs real calls in the browser against a short-lived scratch key. One returns 200 with the raw JSON. One returns 403 — because the scratch key does not hold the scope that endpoint requires, and the endpoint names the scope it wanted. An interface you cannot watch refuse you is not an interface you can build on.
Scopes are per operation, not per system
A key holds named scopes and nothing else, and they are visible in the list without opening it. Access is granted at the grain of the operation — read a booking, post a charge, refund a payment — so an integration is exactly as privileged as its job requires.
Build once, against published documentation
The concepts, the reference and the task-shaped guides are all on this site — not behind a partner portal and not behind an NDA. Read the concepts for the model, the reference for the surface, and the guides for the sequence you actually need.
A compliant client discovers what it may call, calls it, and gets a structured answer or a structured refusal. That is the whole contract, and it is what lets a partner build once rather than once per property.
Go deeper
Every screen above is documented, operation by operation, against the shipped product.
Wondering whether this is for a property your size?
← All features