Developer dashboard

API keys & usage

Keys are stored as SHA-256 hashes and displayed exactly once at creation — we cannot recover a lost key, which is what keeps them safe in a database leak. Usage is counted per key per UTC day, and quotas reset at midnight UTC.

Reference OpenAPI Plans

Active keys

…

Requests today

…

Errors today

…

Plan & billing

Plan and quota are tied to the subscription, never to the request that created a key.

Current plan

—

Free tier — 1,000 requests/day. Attribution back to Premium Health Platform is required.

Starter

₹1,499/month

50,000 requests/day · 120/min

Pro

₹6,999/month

500,000 requests/day · 600/min + bulk export

Enterprise (unlimited, custom rate limits) is contract-based — see partner with us.

Create a key

New keys start on the Free plan. Use a test key for staging so production usage stays separable in the metrics.

LabelEnvironment

Your keys

Loading…

Security notes

Revocation is immediate: the next request with a revoked key returns 401 invalid_api_key. Usage history is retained for your records.
Key management is scoped to your account — another account's key id returns 404, so ids cannot be enumerated.
Never ship a key in client-side code or a public repository; call the API from your backend and keep the key in an environment variable.
No health data is stored: usage counters hold only counts and endpoint paths.