Calendinho REST API v1
New integrations must use https://api.calendinho.com/api/v1. The OpenAPI contract at api.calendinho.com/openapi.json is the source of truth for parameters, bodies, authentication, and responses. Swagger UI is available at api.calendinho.com/docs, with ReDoc at api.calendinho.com/redoc.
Owner operations use a bearer token issued to the authenticated session. Selected profile lookup, availability, and booking creation operations are public by design; do not infer that other endpoints omit authentication. Self-service external API keys are not generally available yet.
curl -sS \
-H 'Accept: application/json' \
https://api.calendinho.com/api/v1/public/profiles/YOUR_SLUG
Request limits
API responses expose the structured RateLimit and RateLimit-Policy fields, plus the compatibility fields RateLimit-Limit, RateLimit-Remaining, and RateLimit-Reset. A 429 Too Many Requests response also includes Retry-After; wait that number of seconds and avoid parallel retries. The general policy is 600 requests per minute per source, while sensitive operations can have lower documented limits.
Versioning and deprecation
The stable version is in the /api/v1 path. The legacy /api path remains functional to preserve the current frontend and existing integrations, but returns Deprecation and a Link to this policy. No shutdown date is scheduled. If one is set, Calendinho will publish a Sunset header, a migration guide, and at least 180 days' notice. Breaking changes will use a new path version; optional fields and new endpoints can be added to v1.
Model Context Protocol
MCP-capable agents can discover tools and schemas directly from these servers:
- Authenticated host:
https://api.calendinho.com/mcp/ - Guest:
https://api.calendinho.com/mcp/guest/ - Email agent:
https://api.calendinho.com/mcp/email/
Use only the surface matching the user's authority. The host server requires authentication context. Also read the agent instructions and llms.txt index.
CLI
Calendinho does not yet publish an official CLI to npm, PyPI, or Homebrew. Use the versioned REST API or MCP for automation. Do not treat third-party packages as Calendinho-maintained tools.