Get started

Your first integration.

Choose the right environment, request the least access you need, then make a bounded read.

1. Choose an environment

Pre-production is restricted to approved testers. Its bookings, content and credentials are isolated; its TEST emails can still reach real booking recipients. Production credentials only work in production.

API base URLs

Production   https://aroharetreat.com/api/external/v1
Preprod      https://aroha-retreat-preprod.web.app/api/external/v1

2. Create a scoped token

Sign in with Google and create an mcp-readonly token for assistant use. Choose own records, or authorized staff records if your existing role permits them. Credentials expire in 24 hours by default, at most 7 days, and can be revoked at any time.

Only a one-way secret hash is stored. Copy the credential once into your host's secret store or a private file. Do not put tokens in source control, URLs, screenshots or chat.

3. Read your capabilities

Shell · token supplied by your secret manager

curl --fail-with-body \
  -H "Authorization: Bearer $AROHA_API_TOKEN" \
  https://aroha-retreat-preprod.web.app/api/external/v1/runtime

The response identifies the environment, contract version and allowed read operation IDs. A scope never grants another guest's records or a higher host role.

4. Recover safely

Pages default to 25, maximum 50. Follow the opaque cursor only when you need another page. Mutations require a retained Idempotency-Key; versioned changes also require the resource's exact ETag in If-Match. After a timeout, retry the same operation and key instead of creating a new booking.

The Connect page issues read-only MCP tokens. Broader integration-token scopes are available only through the authenticated management API and remain limited by your existing permissions. Remote OAuth and service principals are not part of this release.