Natal chart rendering and reports
Endpoint
Input and output
Date, time, IANA timezone, latitude, and longitude produce positions, signs, angles, houses, aspects, nodes, and metadata.
Render the same response as an SVG chart wheel, a mobile chart, or an accessible text-and-table view. Your product supplies the visual design, storage model, and interpretation. AstroAPI does not return a managed browser widget.
Transit calendars and notifications
Endpoint
Input and output
A natal chart and one caller-supplied transit instant produce both charts and their transit-to-natal aspects.
A backend can evaluate dates selected by a user or by your own schedule, then apply product-specific filters before displaying a calendar or sending a notification. The endpoint does not search a date range for the exact moment an aspect begins, perfects, ends, or changes from applying to separating.
Synastry and chart comparison
Endpoint
Input and output
Two birth-data objects produce two full charts plus cross-chart planetary aspects.
Use the raw geometry for overlays, comparison tables, or an application-owned interpretation model. AstroAPI does not return a relationship score, composite or Davison chart, house-overlay score, or prose compatibility judgment.
Sidereal charts and nakshatra timelines
Chart endpoints
Opt in to sidereal mode across birth-chart, house, aspect, transit, and synastry calculations.
Timeline endpoint
POST /api/astro/nakshatra-timeline is a separate Pro calculation.
Build ayanamsa comparison controls, Moon nakshatra displays, or bounded transition calendars. AstroAPI supports Lahiri, Raman, and Krishnamurti ayanamsas. These are Vedic-oriented building blocks, not a complete Jyotish, Panchanga, dasha, yoga, or muhurta engine.
Editorial and AI-assisted content systems
Calculation-first workflow
Use documented chart or transit JSON as structured source data before applying your own rules, templates, or model.
Optional beta fields
The beta structured horoscope endpoint returns deterministic signals, not generated prose.
Any generated or editorial output remains your product's responsibility. Review it for accuracy, disclose meaningful automation, and never present astrological output as a substitute for medical, legal, financial, or mental-health judgment.
Education, demonstrations, and exploratory analysis
The normalized JSON can support teaching tools, calculation demonstrations, regression comparisons, and exploratory projects. Always identify the selected zodiac, ayanamsa, house system, time standard, and calculation window so another developer can understand what was compared.
Passing AstroAPI's regression fixtures does not amount to independent scientific validation for every body, date, or method. Astrology interpretations are not established scientific predictions.
A responsible server-side pattern
- Collect only the birth and location data your feature actually needs, with a clear privacy notice.
- Send requests from your backend so an AstroAPI key is never exposed in browser or mobile-client code.
- Record which calculation settings produced an output, including zodiac, ayanamsa, house system, and timezone.
- Keep calculations separate from interpretations, rankings, recommendations, and other product-owned claims.
- Design for plan quotas and documented errors rather than silently retrying every failed request.
Consult the privacy notice, terms, and your own qualified advisors for obligations specific to your product and users.