Migrating from Prokerala

• Base URL

  Prokerala

  https://api.prokerala.com/v2/...

  96Astro API

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

• Birth input

  Prokerala

  datetime (ISO 8601 with offset), coordinates "lat,lng", ayanamsa as a number (1 Lahiri, 3 Raman, 5 KP)

  96Astro API

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

• Auth

  Prokerala

  POST /token with client id and secret, then Authorization: Bearer <token>

  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 Prokerala'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.

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