Migrating to AstroAsk
Field-by-field guides for moving from another astrology API to AstroAsk, plus an installable AI skill that applies the mapping for you.
Every astrology API computes from roughly the same ephemeris, so the numbers transfer. What differs is shape — auth, request format, field names, string-vs-number types, prose-vs-structured verdicts. These guides map one to the other so you don't re-derive anything, and they're honest about where results legitimately differ and what AstroAsk doesn't have.
Guides
- Migrate from DivineAPI — form-data → JSON, split date fields → ISO timestamp, string numbers → typed values, prose koota descriptions → recomputable scores. Most integrations take 1–3 days.
More guides (Prokerala, AstrologyAPI.com, VedicRishi) are in progress. If you're migrating from one of these today, email us — we'll prioritize the mapping you need.
Let an AI do it
Each guide carries a copy-paste migration prompt for ChatGPT, Claude, Cursor, or Claude Code. Paste it along with your existing integration code and the AI applies the field mapping, rewrites the calls, and adds a verification step that runs both APIs on the same birth data to confirm the results match.
What every migration has in common
| Typical competitor | AstroAsk | |
|---|---|---|
| Auth | token in body and/or header | header only — Authorization: Bearer ak_… |
| Body | form-data, date split into 5–6 fields | one JSON object, one ISO local timestamp |
| Numbers | often strings ("38.786", "false") | typed (38.7835…, false) |
| Verdicts | pre-written prose | scores, classifications, and the conditions that triggered them |
| Pricing | credits vary by endpoint | one request = one unit, every endpoint |
| Trial | varies | 5,000 requests / 14 days, no card — get a key |
Migration checklist (any source)
- Get a trial key.
- Move auth to the header; drop any key from request bodies.
- Write one
toAstroAsk(birth)helper that builds{ date, lat, lng, timezone }from your existing birth-data shape. Reuse it everywhere. - Switch to
application/json. - Re-point endpoints using the guide's mapping table.
- Fix response reads per the field tables — especially string→number/boolean and 1-based→0-based sign indices.
- Run both APIs in parallel on 20–50 real charts; sign / nakshatra / house should match, longitude deltas should be tiny. Read the guide's "why numbers differ" section for the expected ones.
- Ship.
Western astrology primer
The concepts behind the Western endpoints — tropical zodiac, aspects, synastry, transits and progressions.
Migrate from DivineAPI
A field-by-field guide to moving a DivineAPI integration to AstroAsk — auth, request format, endpoint mapping, response fields, and the honest differences. Most integrations take 1–3 days.