Overview
Content platforms — portals, apps, and widgets — publish horoscope readings by sign on a schedule. The rashifal endpoint returns a reading for a given sign and period, so you can build daily, weekly, and monthly pages without any per-user birth data.
This is a publishing workflow. See Documentation for the full list of signs, periods, and plan gates.
The Rashifal Endpoint
Rashifal is a GET route keyed by sign and period, for example daily for a given sign:
curl https://horoscope.devdarsha.com/v1/rashifal/mesha/daily \ -H "x-api-key: YOUR_API_KEY"
Swap the sign and the period segment to build weekly and monthly variants. Because the content is the same for everyone of a sign, one fetch per sign per period covers your whole audience.
A Predictable Content Workflow
A dependable publishing loop:
- At the start of each period, fetch all signs once for daily, weekly, and monthly as needed.
- Store the readings in your CMS or cache with the period they belong to.
- Serve them from your own edge or cache so reader traffic never hits the API directly.
- Refresh on the period boundary — daily overnight, weekly and monthly on their cycle.
Widgets and Regional Pages
The same cached readings can power a sign-picker widget, a “your sign today” block, or per-sign landing pages for search. Keep the sign and period visible so readers always know which reading they are viewing.
Present readings as horoscope content for readers to enjoy and interpret. Keep surrounding copy factual and free of assurances about outcomes.
Caching and Quota Planning
Since a small number of fetches per period serves unlimited readers, rashifal is quota-friendly when cached well. Estimate calls as signs × periods per cycle, confirm your UI handles a missing reading gracefully, and store the X-Request-ID for support cases.