opencals.com valid

Opencals Developer Docs

Documentation for the Opencals Storefront API — REST booking API, TypeScript SDK, and open-source booking website templates for building custom booking experiences.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-25T15:35:08.181Z. Cached copy · Source on opencals.com

# Opencals Developer Docs

> Documentation for the Opencals Storefront API — REST booking API, TypeScript SDK, and open-source booking website templates for building custom booking experiences.

- [Introduction](https://opencals.com/docs/introduction.md): The Opencals Storefront API is booking infrastructure for builders — a REST API for services, real-time availability, carts, checkout, and payments, so you can build a fully custom booking experience on any stack.
- [Quickstart](https://opencals.com/docs/quickstart.md): What the Opencals Storefront API is, how to get an API key, and how to make your first request.
- [Authentication](https://opencals.com/docs/authentication.md): How authentication works in the Opencals Storefront API: public and private API keys, forwarding the buyer IP, customer JWT tokens, refresh flows, and error responses.
- [Build a booking page](https://opencals.com/docs/guides/build-a-booking-page.md): Step-by-step tutorial: use the Opencals Storefront API with Next.js and the TypeScript SDK to list services, pick a time slot, manage a cart, and complete checkout.
- [Storefront SDK](https://opencals.com/docs/guides/storefront-sdk.md): Install and use @opencals/storefront-sdk — the type-safe TypeScript client for the Opencals booking API, generated from the OpenAPI spec with Zod schemas and helpers included.
- [Customer email links (magic links)](https://opencals.com/docs/guides/customer-email-links.md): Set up passwordless email links for customer actions: view/reschedule/cancel appointments, leave feedback, verify email, and reset passwords. No additional code — just configure one setting and implement one route.
- [Webhooks](https://opencals.com/docs/guides/webhooks.md): The planned Opencals webhook event catalog for booking automations — and how to keep a headless booking site in sync today with polling and revalidation.
- [API Reference](https://opencals.com/docs/api-reference/introduction.md): Base URL, authentication, and conventions for the Opencals Storefront API — plus an interactive playground for every endpoint.
- [Customer sign in with credentials](https://opencals.com/docs/api-reference/auth/customer-sign-in-with-credentials.md): Authenticate a storefront customer using email and password
- [Customer OAuth sign in](https://opencals.com/docs/api-reference/auth/customer-oauth-sign-in.md): Authenticate or register a storefront customer using an OAuth provider (e.g. Google)
- [Register a new customer](https://opencals.com/docs/api-reference/auth/register-a-new-customer.md): Create a new customer account on the storefront and send a verification email
- [Request customer email verification](https://opencals.com/docs/api-reference/auth/request-customer-email-verification.md): Send a verification email to the customer for account activation within the store context
- [Verify customer email](https://opencals.com/docs/api-reference/auth/verify-customer-email.md): Confirm customer email ownership using the verification
…

Related sites

Explore similar publishers →

Category suggestions: other listed sites in Developer tools. These share a category. See the whole category →

Machine-readable: GET /v1/resolve?q=opencals.com · GET /v1/domain/opencals.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for opencals.com:
1. POST https://agentwebmap.com/v1/sites/opencals.com/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://opencals.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/opencals.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/opencals.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.