Single endpoint.
Full 75-year Persian cycle with L1 major periods and L2 sub-periods. Sect detected from the chart, not a manual flag.
Most apps that use Firdaria also use
Numbers we measure in production
Designed for developers, not desktop UIs
Abu Ma'shar's 9th-century technique, served as JSON
Firdaria (also spelled alfridaria, fardar, or firdar) is a Persian time-lord system that splits a life into planetary periods. Abu Ma'shar described it in the 9th century, Bonatti referenced it in the 13th, and Vivian Robson summarized it for English-language astrologers in the 20th. Day charts run a 75-year cycle starting with the Sun. Night charts start with the Moon and use a different planet order. Each major period (L1) is divided into seven sub-periods (L2) ruled in Chaldean order. Our API returns the full L1 + L2 cascade from one request, picks the right sect from the birth data, and includes the node periods that most implementations skip. If you are building a medieval astrology app, a chatbot that quotes traditional sources, or a timing dashboard, this is the fastest way to add Firdaria without reimplementing the math.
Firdaria divides a person's life into planetary periods called L1, then splits each L1 into seven L2 sub-periods.
Day charts start with the Sun: Sun 10 years, Venus 8, Mercury 13, Moon 9, Saturn 11, Jupiter 12, Mars 7, then the Mean Node and South Node share 3 + 2 years.
Add those up and you get 75 years.
Night charts start with the Moon and run a different order: Moon 9, Saturn 11, Jupiter 12, Mars 7, Sun 10, Venus 8, Mercury 13, then the nodes.
The total is the same.
Each L1 period is split into seven equal L2 chunks ruled in Chaldean order (Saturn, Jupiter, Mars, Sun, Venus, Mercury, Moon) starting from whichever planet rules the L1.
Nodes do not get an L2 split.
That is the tradition, not a bug.
Sect is the day/night distinction in traditional astrology.
If the Sun is above the horizon at birth, the chart is diurnal.
If below, nocturnal.
Firdaria uses sect to pick which sequence runs.
A day chart that mistakenly uses the night order returns wrong rulers for every period in the life.
Our API checks the Sun's house position from the birth data and routes to the correct sequence automatically.
You do not pass a day_chart flag.
The endpoint does the check, returns sect: "diurnal" or sect: "nocturnal" in the response, and you can show it in your UI.
If you want to override (twilight births, polar latitudes), the underlying logic is exposed in the response so you can reason about it.
An L1 entry contains the planet ruler, years (an integer from 2 to 13), start_date and end_date as ISO strings, a node_period boolean, and an l2_periods array.
The l2_periods array holds seven entries for non-node periods and is empty for node periods.
Each L2 entry has planet, start_date, end_date.
The split is even: an L1 of 12 years gives seven L2 periods of roughly 1.71 years each.
We use 365.2422 days per year (the tropical year length) so the math lines up with how astrologers normally count Firdaria periods.
If you call the endpoint with an as_of_date, the response also includes an active object that tells you which L1 and which L2 are running on that date.
That is useful for chat apps that answer "what period am I in right now?".
Profections move the ascendant one house per year through a 12-year cycle.
Simple, repeats often, light on context.
Zodiacal releasing runs through fixed sign-based periods of L1, L2, L3, L4.
Much heavier, and the periods loop on a fixed length (e.g., 8 years for the Lot of Spirit Aries).
Vedic Vimshottari Dasha covers 120 years using nine periods anchored to the Moon's nakshatra at birth.
Firdaria sits between profections and ZR: longer than profections, simpler than ZR, sect-sensitive in a way Vimshottari is not.
Many traditional astrologers run profections + Firdaria + ZR together.
Our /timing/timeline endpoint aggregates all four (profections, ZR, decennials, Firdaria) into one merged timeline so your front end does not have to stitch four calls.
Firdaria works well for annual reports, life-phase overviews, and chatbot context.
The L1 period gives a multi-year theme ("the Mars years") that is easy to write copy around.
The L2 sub-period gives a tighter window of a few months to two years, good for predictive prompts.
Pair Firdaria with transit hits to flag specific events inside a known period.
For example: "You are in your Mars L1 / Saturn L2 sub-period, and Mars is square your natal Sun next month." That combo reads naturally in a coaching tool and gives an LLM enough structure to ground its response.
Firdaria is also a good fit for educational apps because the rules are short and learnable, unlike ZR which needs a chapter of background.
Firdaria itself is not hard math.
It is timedelta arithmetic on planet-year constants.
The hard part is the surrounding system: sect detection, polar-latitude edge cases, node handling that matches tradition, ISO date output that does not drift across years, and consistent behavior at year boundaries.
Our service has been hardened against those.
It also ships next to 100+ other endpoints, so if you later need natal charts, transits, profections, or solar returns, you do not pay a second integration tax.
Free tier gives 50 requests per month, paid plans start at $11/month.
You can be live in an afternoon.
Tools serving traditional astrologers who already work with Firdaria, profections, and ZR. Single API, four time-lord systems.
Firdaria has Persian-Indian crossover appeal. Pair it with Vimshottari Dasha for apps targeting both audiences.
Feed L1 + L2 + active-period context into the prompt. The bot answers "what's my current period?" without hallucinating dates.
Firdaria's rules are short and teachable. Use the API as the calculation backend for courses on Abu Ma'shar and Bonatti.
Generate PDF or web reports that show the active L1 + L2 with date ranges. Customers get a clear yearly narrative.
Combine Firdaria with profections and transits in one view. Practitioners stop tab-hopping between desktop apps.
| Endpoint | POST /api/v3/timing/firdaria |
| Average Response | ~220ms |
| P95 Response | <400ms |
| Cycle Length | 75 years (day and night) |
| L1 Periods Returned | 9 (7 planets + 2 nodes) |
| L2 Sub-Periods | 7 per non-node L1 (Chaldean order) |
| Sect Detection | Automatic from sun house position |
| Year Length | 365.2422 days (tropical year) |
| Ephemeris | Swiss Ephemeris (swisseph) |
| Date Format | ISO 8601 (YYYY-MM-DD) |
| Active Period Lookup | Optional as_of_date parameter |
| Timeline Aggregation | Combined output via /timing/timeline |
| Rate Limit (Free) | 50 requests/month |
| Rate Limit (Business) | 220,000 requests/month |
| Feature | Astrology API | Others |
|---|---|---|
| L1 + L2 in one call | Yes | L1 only |
| Sect auto-detection | Yes, from chart | Manual day/night flag |
| Node periods included | Yes (Mean + South) | Skipped |
| Response time | ~220ms | 1-3 seconds |
| Combined timeline endpoint | Yes (4 techniques) | Not available |
| Active period on date | Yes (as_of_date param) | Compute client-side |
| Free tier | 50 requests/month | Paid only |
| Ephemeris backend | Swiss Ephemeris | Proprietary / unclear |
12-year cycle, ruler of the year, lighter than Firdaria.
Vedic 120-year time-lord cycle. Useful crossover for Persian audiences.
Hellenistic L1-L4 sign-based periods. Coming soon.
Hellenistic 10-year planetary periods. Coming soon.
Sect, triplicity rulers, almuten — the foundation Firdaria sits on.
One endpoint that returns profections, Firdaria, ZR, and decennials merged on a single timeline.
Start free, scale as you grow. No hidden fees, no surprises.
For small apps and personal projects
For growing apps and medium traffic
For enterprise-scale applications
All plans include comprehensive documentation and SDKs
Questions? Talk to our team
Questions developers actually ask