Manage Commerce7 tasting room and tour reservations through the API
domain: commerce7.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
In App Dev Center, add the Reservation permission (Read or Full) to your app and generate App ID/Secret.
Authenticate with Basic Auth (App ID/Secret) and the `tenant` header, then call the reservation endpoint under https://api.commerce7.com/v1/reservation.
List existing reservations with GET requests, using the standard pagination limit parameter (max 50 per page).
Create or update bookings by POSTing/PUTing reservation records tied to a reservation type/experience configured in the admin's Reservations settings.
Read back the reservation to confirm booking status before treating a slot as held, since availability rules are enforced by Commerce7's reservation settings.
Reconcile reservation-linked orders using the documented ability to connect a reservation to an order in the admin.
Known gotchas
Reservation experiences, time slots, and capacity rules are configured in the Commerce7 admin UI, not created from scratch via the API — the API operates against experiences that already exist.
Reservation is a distinct permissioned endpoint; an app with only Order or Customer access cannot touch reservation data until Reservation permission is explicitly added.
As with all Commerce7 endpoints, requests are capped at 100/minute per tenant, which matters for bulk reservation imports or sync jobs.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?