Open REST API

API Usage

Call Jagannatha Hora's Vedic calculation engine directly from your own app. Open access, no API keys required.

Send birth date, time, and location to the endpoint you need. Responses come back as structured JSON — birth charts, dashas, transits, matching, and more.

Also see MCP server setup for AI assistants.

Open, No Key Required

The Jagannatha Hora calculation API is open — no signup, no API key, no auth header. Send birth details in the request body and read structured JSON in the response.

Nothing is gated. Every calculation the engine can do — birth chart, dashas, divisional charts, transits, matching, muhurta, strengths, yogas, doshas — is available through this API.

Base URL

Prepend this base URL to any of the endpoints listed below. All requests are HTTPS; responses are JSON.

https://jagannatha-hora-359167915530.europe-west1.run.app

Everything the engine calculates

No paid tier, no private-plan gating. Every calculation the Jagannatha Hora engine produces — from ascendant to D-60 — is exposed through the same endpoints.

No API key, no daily caps

No sign-up, no request counters, no quota emails. Ten endpoints carry a per-minute cap per IP; the rest are uncapped. Nothing accumulates against you day to day.

Same engine the site uses

The API returns exactly what the Jagannatha Hora web app renders. What you see on jagannathahora.com is what you get in JSON.

Available Endpoints

POST/horoscope

Full horoscope from birth details

POST/marriage-match

Kuta and Guna Milan compatibility

POST/gochara

Planetary transits for a date

POST/planet-ingress

When a planet enters a sign

GET/muhurta/events

Muhurta events in a window

GET/location/autocomplete

City and timezone lookup

Sample Request

Generate a full horoscope with a single POST — no auth header.

Terminal

curl -X POST "https://jagannatha-hora-359167915530.europe-west1.run.app/horoscope" \
  -H "Content-Type: application/json" \
  -d '{
    "date": "1990-01-01",
    "time": "06:30:00",
    "latitude": 12.9716,
    "longitude": 77.5946,
    "timezone": 5.5,
    "place": "Bengaluru"
  }'

What Comes Back

A single horoscope call returns the full chart context. Each section below is included in the JSON response.

Birth details echo (validated inputs)

Ascendant, nakshatra, and pada

All grahas with sign, house, nakshatra, and degree

Panchanga (tithi, nakshatra, yoga, karana)

All 16 divisional charts (D-1 through D-60)

Vimshottari, Yogini, and Ashtottari dashas

Shad Bala, Bhava Bala, Ashtakavarga

Yogas, doshas, longevity, Sade Sati windows

Arudhas, sphutas, upagrahas, sahams

Marriage compatibility (Ashtakoota + Porutham)

Rate Limits & Fair Play

Limits are per client IP, and exceeding one returns a 429. Ten endpoints declare one: /horoscope, /muhurta and /gochara/range at 30/min, /horoscope/pdf at 10/min, and /saturn-timeline, /gochara, /planet-ingress, /panchang, /gochar and /gochar/events at 60/min. Everything else — including /marriage-match and /muhurta/events — is currently uncapped. Counts are held in each server instance's memory rather than shared, so the effective ceiling is per instance and can be higher in practice. There is no API key and no daily or monthly cap. A few small asks in return:

Cache results locally when you can — the same birth details always produce the same chart.

Batch requests when your workflow allows it.

Send only the fields the endpoint documents; the schema is the contract.

Reach out before large-scale scraping — we would rather help you than get surprised.