Vedika API reference

Endpoints by system

Counted from the served OpenAPI spec. Pick a system to read about it, or open it in the explorer to see every endpoint.

687 endpoints · 12 systems · 566 with a keyless sandbox

Base URL

https://api.vedika.io

https://api.vedika.io/sandbox

The sandbox mirrors the live routes without the /v2/astrology prefix, for example /sandbox/birth-chart. It needs no key, costs nothing and returns fixed sample data, so use it to test your integration and a key for real charts.

Authentication

Send your API key in the Authorization header as a Bearer token. The X-API-Key header is also accepted when no Bearer credential is present. Create and rotate keys in the dashboard.

Authorization: Bearer vk_live_your_key

A missing, malformed, expired or revoked key gets 401 with a body that names the problem, and a WWW-Authenticate header. Do not retry a 401; fix the key. Keep keys on your server and never ship them in a browser or mobile app.

A complete example

A Vedic birth chart for a Mumbai birth. Send the same body to https://api.vedika.io/sandbox/birth-chart without the header to try it for free.

curl https://api.vedika.io/v2/astrology/birth-chart \
  -H "Authorization: Bearer $VEDIKA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "datetime": "1990-05-15T10:30:00",
    "latitude": 19.07,
    "longitude": 72.87,
    "timezone": "+05:30",
    "ayanamsa": "lahiri"
  }'

Add an X-Idempotency-Key header with a unique value per request so a retry after a timeout is never charged twice.

Responses

Successful calls return JSON with four parts: success, the result in data, request details in meta, and what the call cost in billing. This is a real sandbox response to the example above, shortened; the sandbox marks itself with "mode": "sandbox" and charges nothing.

{
  "success": true,
  "data": {
    "ascendant": {
      "sign": "Pisces",
      "signLord": "Jupiter",
      "degree": 13.56,
      "fullDegree": 343.56
    },
    "moonSign": "Sagittarius",
    "sunSign": "Sagittarius",
    "planets": "[ ... nine grahas with sign, house, degree, nakshatra ... ]"
  },
  "meta": {
    "contentMode": "fixture",
    "engine": "vedika-intelligence",
    "fixtureId": "demo-birth-1995-new-delhi",
    "inputUsage": "ignored",
    "mode": "sandbox",
    "sample": true,
    "version": "2.1.0"
  },
  "billing": {
    "balanceAfter": 100,
    "balanceBefore": 100,
    "category": "astrology",
    "charged": 0,
    "currency": "USD",
    "endpoint": "/sandbox/birth-chart"
  }
}

Every response also carries X-Request-Id. Quote it when you contact support and we can find the exact call.

Errors

Errors use the HTTP status code and a JSON body with status, code and message. Branch on the status first and on code second.

{
  "status": "error",
  "code": "UNAUTHORIZED",
  "message": "Authentication required. Pass your API key as `Authorization: Bearer vk_live_...`."
}

Rate limits

Each plan has a per-minute and a per-day request limit. The figures for every plan are on the rate limits page. Every response reports where you stand:

• X-RateLimit-Limit: requests allowed in the current window
• X-RateLimit-Remaining: requests left in it
• X-RateLimit-Reset: when the window resets

When you hit the limit you get 429 with Retry-After. A 429 is about speed, not money: a call your wallet cannot cover returns 402 instead, so read the body code before deciding to wait or to top up.

Next steps