Skip to content
Western Astrology API

Natal, transit, synastry, and progression APIs

Serve Western astrology apps alongside Vedic products with a unified developer hub, standard response envelopes, and Swiss Ephemeris astronomy.

Western astrology APIs alongside Vedic on one platform

Global astrology apps often need tropical natal charts, transits, synastry, and progressions — separate from sidereal Jyotish math but frequently requested by the same user base. Navamsha exposes Western families with Swiss Ephemeris astronomy while keeping Vedic logic in its own layer, so you do not maintain two ephemeris stacks.

Western endpoints use the tropical zodiac without ayanamsa offset. Metadata on responses clarifies house system and zodiac type, which prevents accidental mixing of sidereal Kundali JSON with tropical transit overlays in hybrid products.

Relationship, coaching, and horoscope features

Synastry and composite routes support relationship astrology products — aspect grids, inter-chart overlays, and coaching workflows that compare two natal charts. Transit endpoints power daily horoscope experiences by overlaying current sky positions on stored natal longitudes.

Solar return and progression endpoints suit year-ahead report generators without bundling PDF report credits from legacy vendors. Latency on natal and transit routes targets sub-50ms averages for interactive mobile experiences.

One key, multiple traditions

Use a single Navamsha API key for Vedic and Western features — unified dashboard metering, one OpenAPI import for codegen, and consistent error envelopes. Products that start Vedic-only often add Western modules later; keeping astronomy on one vendor reduces migration risk.

Import the Postman collection from www.navamsha.in/developers, set base_url to api.navamsha.in, and prototype both traditions before committing UI. Golden validation remains essential: tropical reference software differs from sidereal references, so maintain separate fixture sets per tradition.

Example endpoints

GET/api/v1/western/natal

Natal chart calculation

1 credit / call
GET/api/v1/western/transit

Transit overlays

1 credit / call
POST/api/v1/western/synastry

Synastry aspects

2 credit / call

What you can build

Global horoscope apps

Serve tropical natal and transit charts alongside Vedic features under one API key and unified billing.

Relationship astrology

Synastry aspect grids and composite midpoints for dating, coaching, and wellness products targeting Western audiences.

Coaching dashboards

Solar return and progression endpoints power year-ahead reports without maintaining separate ephemeris libraries.

How it works

  1. 1

    Western endpoints use tropical zodiac positions — no ayanamsa offset — with Swiss Ephemeris astronomy.

  2. 2

    Natal charts compute ascendant, planetary placements, and house cusps for the selected house system.

  3. 3

    Transit endpoints overlay current sky positions against a natal chart for daily horoscope and coaching apps.

  4. 4

    Synastry and composite endpoints compare two charts for relationship astrology products.

Sample request / response

Request

curl -G "https://api.navamsha.in/api/v1/western/natal" \
  -H "X-API-Key: YOUR_API_KEY" \
  --data-urlencode "year=1990" \
  --data-urlencode "month=7" \
  --data-urlencode "date=4" \
  --data-urlencode "hours=10" \
  --data-urlencode "minutes=30" \
  --data-urlencode "latitude=40.7128" \
  --data-urlencode "longitude=-74.0060" \
  --data-urlencode "timezone=-4"

Response (abbreviated)

{
  "ascendant": { "sign": "Virgo", "degree": 18.32 },
  "planets": [
    { "name": "Sun", "sign": "Cancer", "house": 11, "degree": 12.05 },
    { "name": "Moon", "sign": "Pisces", "house": 7, "degree": 24.18 }
  ],
  "metadata": { "zodiac": "tropical", "house_system": "placidus" }
}

Built for

    Global horoscope apps

    Relationship astrology

    Coaching and wellness products

FAQ

What is the Western astrology API used for?

Natal charts, transits, synastry, composite charts, progressions, and solar returns for global horoscope and relationship astrology products.

What ayanamsa does Navamsha use for Western charts?

Western endpoints use tropical zodiac positions (no ayanamsa offset). Vedic and Western families share Swiss Ephemeris astronomy with separate Jyotish/Western logic layers.

Is there a free tier?

Yes — 10,000 free calls/month. Most Western natal and transit endpoints cost 1 credit per call during launch.

How fast are Western API responses?

Natal and transit routes are optimized for sub-50ms average latency — suitable for real-time app experiences.

Can I use Western and Vedic APIs with the same key?

Yes — one API key covers all families. Vedic routes use sidereal/Lahiri; Western routes use tropical zodiac.

Which house systems are supported?

Placidus and whole-sign are common defaults. Check Swagger for the full list per endpoint.

Are outer planets included?

Uranus, Neptune, and Pluto are available in extended Western endpoints. Confirm inclusion in the OpenAPI schema.