Which Vedic-oriented calculations are supported?
Send "zodiac": "sidereal" to opt in. AstroAPI subtracts the
selected date-aware ayanamsa from tropical longitude and returns the sidereal
result. If the ayanamsa is omitted in sidereal mode, it defaults to
lahiri.
- Ayanamsas
- Lahiri, Raman, Krishnamurti
- Nakshatra geometry
- 27 nakshatras × 4 padas
- Public date window
- 1900-01-01 through 2050-12-31
Sidereal birth charts
Sidereal longitudes, signs, chart angles, houses, aspects, nodes, and Moon nakshatra data.
Sidereal houses
Equal or whole-sign cusps after the selected ayanamsa is applied to the tropical angles.
Sidereal transits
A natal chart, one requested transit chart, and their cross-chart aspects.
Sidereal synastry
Two charts in the same sidereal frame plus raw cross-chart aspect geometry.
Nakshatra timelines Pro
Gap-free nakshatra and pada residence windows across a caller-supplied UTC interval.
System selection
How tropical defaults, sidereal opt-in, ayanamsa choice, and separate products relate.
What does the nakshatra timeline return?
The Pro timeline endpoint divides the sidereal zodiac into 108 nakshatra-pada segments and returns contiguous residence intervals. Supported bodies are the Sun, Moon, Mercury, Venus, Mars, Jupiter, Saturn, Rahu, and Ketu. A requested interval must be positive, no longer than 180 days, and within the public calculation window.
Timeline output is geometry only. Rahu uses the engine's mean north node, and Ketu is its opposite south node. This endpoint does not calculate dashas or make predictions.
What is outside the current Jyotish scope?
Sidereal longitude and nakshatra geometry are inputs to many different traditions; they do not encode an entire interpretive or calendrical system. AstroAPI currently provides none of the following:
- Vimshottari or other dashas and predictive timing frameworks
- Yogas, shadbala, ashtakavarga, or complete dignity and strength systems
- Tithi, yoga, karana, vara, Panchanga, or muhurta calculations
- Varga or divisional charts such as Navamsa
- Vedic sunrise/sunset day boundaries or regional calendar rules
- Interpretive, religious, remedial, or certainty-based predictions
Developers building those features must define, implement, test, and disclose their own rules instead of presenting AstroAPI's coordinate output as a complete Jyotish answer.
Appropriate product uses
- Sidereal chart renderers with an explicit, user-selected ayanamsa
- Nakshatra and pada displays derived from returned geometry
- Transition calendars for supported bodies and bounded intervals
- Educational comparison tools that show how ayanamsa selection changes longitude
- Application-owned Jyotish logic built on a declared, tested coordinate layer
For application architecture and responsible handling of birth inputs, see AstroAPI use cases. For calculation formulas and known approximations, see methodology.