The Shape of an Astrology App
Most astrology apps have two core surfaces: a personal chart built from the user’s birth details, and a daily reading tied to their sign. The Horoscope API covers both. Examples here use the sample birth Aarav Sharma, born 1990-08-15 at 10:30 in Kolkata.
This is an integration walkthrough. See Documentation for exact request fields, plan gates, and schemas.
Building the Birth Profile
When a user enters their birth details once, call the Kundli endpoint to get their chart, then the dasha endpoint for their current planetary period. Cache the result against the user’s stored birth input so you are not recomputing the same chart on every visit.
curl -X POST https://horoscope.devdarsha.com/v1/kundli \
-H "content-type: application/json" \
-H "x-api-key: YOUR_API_KEY" \
-d '{"date":"1990-08-15","time":"10:30","city":"Kolkata"}'Adding a Daily Reading
Rashifal is public, read-only, and keyed by sign and period, so it is ideal for a daily-reading feed. Request the user’s sign to show today’s reading:
curl https://horoscope.devdarsha.com/v1/rashifal/mesha/daily \ -H "x-api-key: YOUR_API_KEY"
Because rashifal is the same for everyone of a given sign, you can fetch each sign once per period and serve it to all matching users.
How to Combine the Endpoints
A dependable pattern:
- On profile creation, compute and cache the Kundli and current dasha.
- On each daily visit, read the cached chart and fetch the day’s rashifal for the user’s sign.
- Let users drill into dasha detail or divisional charts (D1 and D9) on demand.
Quota and Rollout Planning
Compute-heavy endpoints cost more quota than cached reads, so estimate calls per active user and cache aggressively. Test representative births and signs in Playground, confirm your UI handles optional or plan-gated fields, and store the X-Request-ID for support cases before you launch.