Skip to content
96Astro API

Migration guide

Migrating from VedicAstroAPI

Every VedicAstroAPI endpoint we mapped, the 96Astro API capability that answers it, and how close the match is. List last checked 27 October 2026.

79

Dedicated capability

4

Section of a capability

11

Related, differs

0

No equivalent yet

Step 1

What changes in every request

  • Base URL

    VedicAstroAPI

    See their documentation

    96Astro API

    https://api.96astroapi.com/v1/<family>/<capability>

  • Birth input

    VedicAstroAPI

    See their documentation

    96Astro API

    datetime (local, ISO 8601), timezone (IANA name, e.g. Asia/Kolkata), latitude, longitude; optional ayanamsha and node

  • Auth

    VedicAstroAPI

    See their documentation

    96Astro API

    Authorization: Bearer <key> (or X-API-Key); sandbox keys for testing, live keys for production

  • Send an IANA time zone

    Send the birth place's IANA time zone rather than an offset: we resolve the historical offset and daylight saving for the date, so births before a zone change come out right.

  • Match your method settings

    Vedic results default to the Lahiri ayanamsha and the true node. Pass ayanamsha and node to match the settings your current results were produced with before comparing outputs.

  • Map fields one at a time

    Responses are JSON with the result under data (see requests and responses). Field names differ from VedicAstroAPI's, so map fields one capability at a time and compare a few known charts.

  • Start in the sandbox

    Start with a sandbox key and the quickstart; the API reference lists every field of every capability.

Step 2

Endpoint mapping

79 dedicated capabilities, 4 sections of a larger response, 11 related but different, 0 without an equivalent yet.

Dashas

5

Doshas

3

Extended horoscope

15

Horoscope

11

Matching

10

Panchang

7

Predictions and numerology

7

Tarot

12

Utilities

5

Western

19

Endpoint names are VedicAstroAPI's, as listed on their public pages on 27 October 2026. A match says which of our capabilities computes the same thing; check method settings (ayanamsha, node, house system) before relying on equal numbers.

Missing something? Tell us