Gochar (Natal Transits) API

Transits over the natal Moon and houses

POST/v1/transits/natal

2 credits · Secret key (test or live) · getNatalTransits

Request body

birth Birth required
- date string (date) required
  e.g. "1990-08-13"
- time string
  pattern ^([01]\d|2[0-3]):[0-5]\d(:[0-5]\d)?$ · e.g. "06:30"
- time_accuracy string
  With "unknown", lagna- and house-dependent fields are omitted and listed in warnings — never filled with a noon default.
  one of exact, approximate, unknown · default "exact"
- place Coordinates or object or object required
  Coordinates, a place_id from /v1/places/search, or a free-text query. A vague query returns 422 place_ambiguous with candidates; the API never guesses.
  
  One of:
  1. Coordinates
    Fields
    - latitude number required
      ≥ -90 · ≤ 90
    - longitude number required
      ≥ -180 · ≤ 180
    No other fields are accepted.
  2. object
    Fields
    - place_id string required
    No other fields are accepted.
  3. object
    Fields
    - query string required
      at least 2 characters · at most 120 characters
    No other fields are accepted.
- timezone string
  "auto" (from coordinates AND date), an IANA name, or a fixed offset like "+05:30".
  default "auto"
No other fields are accepted.
at string (date-time)
options Options
- ayanamsa string
  Each system is its Swiss Ephemeris definition (a constant offset from Lahiri). Applies to chart operations; KP operations always use KP-New and the personal muhurat stays Lahiri. meta.ayanamsa names the system used.
  one of lahiri, raman, krishnamurti, yukteshwar, fagan_bradley · default "lahiri"
- house_system string
  one of whole_sign · default "whole_sign"
- node string
  The Rahu/Ketu the chart uses: the true (osculating) node, as Swiss Ephemeris and Drik Panchang define it, or the mean node. meta.node names the one used. POST /v1/planets/positions always returns both.
  one of true, mean · default "true"
- lang string
  one of en, hi · default "en"
- view string
  compact drops labels and prose — for LLM callers.
  one of full, compact · default "full"
- tone string
  descriptive: the prose fields (tithi.note, tara descriptions, the timing summary and insights, natal-transit descriptions, transit-event notes) carry reviewed descriptive sentences, attributed to the tradition and with no instructions, in options.lang. Ids, scores and every other value are unchanged. Applies to getPanchang, getFavourableDays, getPersonalTiming, getDashaTransitConfluence, getNatalTransits and listPlanetaryEvents (and those inside a bundle); elsewhere it changes nothing.
  one of default, descriptive · default "default"
- dasha_year number
  Days in a Vimshottari year: 365.25 (Julian, the default), 365.2422 (tropical) or 360 (savana). Applies to /v1/dasha/vimshottari and /v1/dasha/vimshottari/current; data.basis.year_days names the one used.
  one of 365.25, 365.2422, 360 · default 365.25
No other fields are accepted.

No other fields are accepted.

Response

JSON { data, meta, warnings }, where data is:

at string (date-time) required
transits array of object required
- planet string required
- sign string required
- house_from_moon integer required
  The sign it transits, counted from the natal Moon's sign (gochar); impact is judged from it.
  ≥ 1 · ≤ 12
- natal_house integer
  The same sign counted from the natal lagna (whole sign). Omitted without a birth time.
  ≥ 1 · ≤ 12
- retrograde boolean required
- impact string required
  one of favourable, challenging, neutral
- description string required
- description_id string required
  A stable id for description: the same sentence always has the same id (D3, 2026-10-29).

Errors: 400, 401, 403, 404, 422, 429, 500. See error codes.

Example request

curl -X POST 'https://api.astrologics.in/v1/transits/natal' \
  -H 'Authorization: Bearer al_test_YOUR_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"birth":{"date":"1990-08-13","time":"06:30","place":{"latitude":28.6139,"longitude":77.209}},"at":"2026-10-02T06:00:00Z"}'

Node.js

const res = await fetch("https://api.astrologics.in/v1/transits/natal", {
  method: "POST",
  headers: { Authorization: "Bearer al_test_YOUR_KEY", "Content-Type": "application/json" },
  body: JSON.stringify({
    "birth": {
      "date": "1990-08-13",
      "time": "06:30",
      "place": {
        "latitude": 28.6139,
        "longitude": 77.209
      }
    },
    "at": "2026-10-02T06:00:00Z"
  }),
});
console.log(JSON.stringify(await res.json(), null, 2));

Python

import json
import urllib.error
import urllib.request

body = {
    "birth": {
        "date": "1990-08-13",
        "time": "06:30",
        "place": {
            "latitude": 28.6139,
            "longitude": 77.209,
        },
    },
    "at": "2026-10-02T06:00:00Z",
}

req = urllib.request.Request(
    "https://api.astrologics.in/v1/transits/natal",
    method="POST",
    headers={"Authorization": "Bearer al_test_YOUR_KEY", "Content-Type": "application/json"},
    data=json.dumps(body).encode(),
)
try:
    with urllib.request.urlopen(req) as res:
        print(json.dumps(json.load(res), indent=2, ensure_ascii=False))
except urllib.error.HTTPError as err:
    print(err.code, err.read().decode())

PHP

<?php
$ch = curl_init('https://api.astrologics.in/v1/transits/natal');
curl_setopt_array($ch, [
    CURLOPT_CUSTOMREQUEST => 'POST',
    CURLOPT_HTTPHEADER => ['Authorization: Bearer al_test_YOUR_KEY', 'Content-Type: application/json'],
    CURLOPT_POSTFIELDS => '{"birth":{"date":"1990-08-13","time":"06:30","place":{"latitude":28.6139,"longitude":77.209}},"at":"2026-10-02T06:00:00Z"}',
    CURLOPT_RETURNTRANSFER => true,
]);
echo curl_exec($ch), PHP_EOL;

Example response

200 OK · 3,338 characters

{
  "data": {
    "at": "2026-10-02T06:00:00.000Z",
    "transits": [
      {
        "planet": "jupiter",
        "sign": "cancer",
        "house_from_moon": 4,
        "natal_house": 12,
        "retrograde": false,
        "impact": "challenging",
        "description": "Jupiter in 4th - over-expansion or misplaced optimism; review commitments",
        "description_id": "jupiter_in_4th_over_expansion_or_misplaced_optimism_review_commitments"
      },
      {
        "planet": "saturn",
        "sign": "pisces",
        "house_from_moon": 12,
        "natal_house": 8,
        "retrograde": true,
        "impact": "challenging",
        "description": "Saturn in 12th - delays, responsibilities and discipline demanded",
        "description_id": "saturn_in_12th_delays_responsibilities_and_discipline_demanded"
      },
      {
        "planet": "rahu_north_node",
        "sign": "aquarius",
        "house_from_moon": 11,
        "natal_house": 7,
        "retrograde": true,
        "impact": "favourable",
        "description": "Rahu in 11th - ambition and unconventional growth paths open",
        "description_id": "rahu_in_11th_ambition_and_unconventional_growth_paths_open"
      },
      {
        "planet": "ketu_south_node",
        "sign": "leo",
        "house_from_moon": 5,
        "natal_house": 1,
        "retrograde": true,
        "impact": "challenging",
        "description": "Ketu in 5th - sudden losses and disillusionment possible",
        "description_id": "ketu_in_5th_sudden_losses_and_disillusionment_possible"
      },
      {
        "planet": "mars",
        "sign": "cancer",
        "house_from_moon": 4,
        "natal_house": 12,
        "retrograde": false,
        "impact": "challenging",
        "description": "Mars in 4th - conflicts, accidents and impulsiveness; slow down",
        "description_id": "mars_in_4th_conflicts_accidents_and_impulsiveness_slow_down"
      },
      {
        "planet": "sun",
        "sign": "virgo",
        "house_from_moon": 6,
        "natal_house": 2,
        "retrograde": false,
        "impact": "favourable",
        "description": "Sun in 6th - authority, recognition and career focus",
        "description_id": "sun_in_6th_authority_recognition_and_career_focus"
      },
      {
        "planet": "venus",
        "sign": "libra",
        "house_from_moon": 7,
        "natal_house": 3,
        "retrograde": false,
        "impact": "challenging",
        "description": "Venus in 7th - relationship friction and financial imprudence",
        "description_id": "venus_in_7th_relationship_friction_and_financial_imprudence"
      },
      {
        "planet": "moon",
        "sign": "taurus",
        "house_from_moon": 2,
        "natal_house": 10,
        "retrograde": false,
        "impact": "neutral",
        "description": "Moon in 2nd - routine emotional fluctuations",
        "description_id": "moon_in_2nd_routine_emotional_fluctuations"
      }
    ]
  },
  "meta": {
    "request_id": "req_example",
    "api_version": "v1",
    "engine_version": "2026.10.10",
    "mode": "live",
    "credits_charged": 2,
    "ayanamsa": "lahiri",
    "house_system": "whole_sign",
    "node": "true",
    "timezone_used": {
      "name": "Asia/Kolkata",
      "utc_offset": "+05:30",
      "source": "auto"
    }
  },
  "warnings": []
}

Try it

Test key (optional)

Leave empty to use the shared demo key (limited). Test keys only: never charged. Kept in this browser tab and sent through this site to the API. Create one

Body (JSON)

{
  "birth": {
    "date": "1990-08-13",
    "time": "06:30",
    "place": {
      "latitude": 28.6139,
      "longitude": 77.209
    }
  },
  "at": "2026-10-02T06:00:00Z"
}

Gochar (Natal Transits) API

Request body

Response

Example request

Example response

More in Transits