API Keys

Create, prefix and secure the key that authenticates every Vedika call.

API keys are created and managed entirely in the dashboard. One key authenticates across the full 700+ operation surface — there is no separate key per feature or endpoint family.

#Create a key

Sign in to the dashboard.
Open API Keys and choose Create Key.
Copy the key into your server environment — not into client-side code.
Send it on every request via x-api-key or Authorization: Bearer.

x-api-key: vk_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Authorization: Bearer vk_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

#Key prefixes

Prefix	Use
`vk_live_`	Production, retail plans (Starter through Business).
`vk_ent_`	Enterprise.
`vk_test_`	Rejected on production — the keyless mock sandbox is used for testing instead.

Tip

There is no test-mode key for the production API. To try requests before you have a paid plan, use the keyless mock sandbox — no key, no wallet charge.

#Keeping keys safe

Keep keys server-side. Never ship a live key in browser or mobile client code.
Rotate periodically from the dashboard, and immediately if a key may have leaked.
One key reaches the entire operation surface — Vedic, Western, KP, AI Query and more — so treat it like a master credential, not a per-feature token.

Coming soon

A programmatic key-management API — creating, rotating and revoking keys by calling the API instead of using the dashboard — is on the roadmap. See Management API. Until it ships, the dashboard is the only supported way to manage keys.