# BookingGood

> BookingGood website integration documentation for clubs, developers and language models. Club partners normally use iframe widgets; developers can build custom experiences with the Partner API.

## Documentation

- [For club partners](/partners#embedding): Start with an iframe widget on the club's existing website. Includes the admin embed builder, setup and parent-origin registration for sign-in.
- [API reference](/developers): Human-readable guide, operations, schemas and callback contract. Technical documentation is in English.
- [Integration guide](/developers/guide.md): Plain Markdown workflows, authentication, safe retries, baseline recovery and signed callbacks.
- [OpenAPI 3.1 contract](/developers/openapi.json): Authoritative request/response schemas, errors, scopes, webhooks and public signature test vectors.
- [Complete documentation](/llms-full.txt): Club website embedding instructions, API guide and complete OpenAPI contract in one text resource.

## Essential constraints

For a club website using BookingGood's existing booking flow, prefer the iframe. It needs no Partner API credentials; secure embedded sign-in requires the club's exact parent origins to be registered. Use the API when developing a custom booking flow. API base path: /api/partner/v1. HTTPS Bearer credentials are club/environment bound and belong on the integration backend. Access requires administrator provisioning; documentation does not imply the API is enabled on this host. PENDING is not customer confirmation. Persist and retry exact mutation requests; only operationFinal: true settles a refusal. Callbacks never replace change-feed recovery. Payments, accounts, passes, courses, shared resources and recurring creation are outside this API.