Current status
Beta access is available by request.
The API is real and reachable, but this is not yet a self-service developer platform. Customer dashboards, pricing checkout, public SLA wording and automated key rotation are still coming soon.
Developer access
CalculationTime API beta
A small, trust-first API surface for time, date, solar, astronomy, geospatial and utility calculations. Public docs are open now; protected endpoints require a privately issued beta key.
Trust layer
Contract first, keys private.
Developers can inspect the OpenAPI contract before requesting access. Raw API keys should only appear once during private provisioning and must not be placed in public frontend examples.
Endpoint map
What exists behind the buttons.
| Method | Path | Access | Purpose |
|---|---|---|---|
| GET | /openapi.json | Public | Machine-readable OpenAPI 3.1 contract for the beta API surface. |
| GET | /health | Public | Lightweight health response for the API service. |
| GET | /v1/status | Public | Version, uptime and exposed route-family summary. |
| GET | /v1/time | API key | Protected local-time coordinate endpoint for approved beta testers. |
| GET | /v1/canary | API key | Protected monitoring canary; public uptime history is not claimed yet. |
Publication guardrails
Public wording stays honest.
- Beta keys are issued privately for approved testers.
- Protected examples never include real keys in public page code.
- The OpenAPI contract is public so developers and AI agents can inspect the shape first.
- Reliability wording stays conservative until monitoring history and rate-limit headers are fully in place.
Example shape
Protected requests use `X-API-Key`.
Public examples use placeholders only. Approved testers receive real keys privately.
curl 'https://api.calculationtime.com/v1/time?lat=-33.8688&lon=151.2093&at=2026-07-31T00:00:00Z' \
-H 'X-API-Key: ct_live_REPLACE_WITH_PRIVATE_KEY'