A Documented Astrology Calculation Layer

What AstroAPI provides

The public endpoints accept explicit chart inputs and return JSON for supported bodies, signs, angles, houses, aspects, nodes, synastry, natal-to-transit comparisons, and selected sidereal calculations. Tropical is the default; sidereal mode is an explicit option.

Product principles

1. Document the contract. Public reference pages describe required inputs, response shapes, authentication, errors, and endpoint limits.
2. Name the method. Ephemeris source, coordinate frame, zodiac selection, house formulas, node behavior, and date boundaries are declared.
3. Separate data from meaning. Calculation output and product-owned interpretation are different layers.
4. Keep API keys server-side. The service is designed for trusted backends, not keys embedded in browser or mobile-client code.
5. Publish limitations. Planned or unsupported features are not presented as current capabilities.

Who it is for

AstroAPI is intended for developers and product teams that want to build their own astrology interface on top of machine-readable calculations. It can serve web or mobile application backends, chart-rendering services, educational tools, and other systems that can send authenticated HTTPS requests and handle JSON responses.

It is not an astrology practice, a scientific prediction service, or a substitute for medical, legal, financial, or mental-health advice. A customer application remains responsible for its own content, user promises, privacy practices, and regulatory obligations.

How to evaluate AstroAPI

Start with the calculation methodology, then open the reference for the endpoint you intend to use. Compare declared inputs and definitions—not just labels—when checking output against another system. Different ephemerides, frames, ayanamsas, node definitions, house formulas, and orb policies can produce different results.

Product, support, and policy resources