API Keys

API keys authenticate server-to-server requests to Cosmic Ephemeris. They are required for all /api/astro/* endpoints.

Create an API key

Create up to five active keys. Give each integration only the endpoints it needs and choose an expiration when practical.

!

Keep every key in a server-side environment variable or secret manager. Revoke a key immediately if it is exposed.

Environment controls

Set account-wide capabilities and an optional aggregate standard-unit budget for every key in each environment. Existing keys remain enabled until you change a policy.

Loading environment controls…

Your API keys

Loading active keys…

How API keys work

API keys authenticate requests to /api/astro/*.
Project labels organize integrations. Environment controls can stop standard calculations, Nakshatra Timeline, or batch jobs for all keys in one environment.
A team key is owned, governed, and billed by its workspace owner.
An optional per-key monthly budget stops standard calls before the account-wide allowance is exhausted.
Usage limits and billing are enforced server-side.
A secure browser session is used only for this dashboard.

Best practices

Store keys in environment variables or a secrets manager.
Use endpoint-specific scope for integrations that do not need full access.
Use separate keys for production, staging, and automation so one can be revoked without interrupting the others.
Rotate keys regularly and after any suspected compromise.