---
title: "Transits against a birth chart"
method: POST
path: "/gochara"
tags: ["Transits"]
---

# Transits against a birth chart

`POST /gochara`

## Request

- Base URL: `https://jagannatha-hora-359167915530.europe-west1.run.app`
- URL: `https://jagannatha-hora-359167915530.europe-west1.run.app/gochara`
- Auth: none declared

Where the planets are at a target date and time, read against a birth chart: each planet's sign, house from the lagna and Moon, nakshatra, Ashtakavarga support and the panchanga and muhurta windows of the day.

Rate limit: 60 requests a minute per IP.

## Request body

- object
  - `date` string, required: Birth date, YYYY-MM-DD. Years 1800 to 2100.
  - `time` string, required: Birth time, HH:MM:SS on a 24-hour clock.
  - `place` string: Place name, echoed in the response. Coordinates decide the calculation.
  - `latitude` number, required: Decimal degrees, north positive. Places beyond about 66.5° north or south (inside the polar circles) are rejected with 422.
  - `longitude` number, required: Decimal degrees, -180 to 180, east positive.
  - `timezone` number, required: UTC offset in hours at birth, -12 to 14 (5.5 for India). By default the API works out the historically correct offset, including daylight saving, from the coordinates and date; see timezone_mode.
  - `elevation` number: Metres above sea level.
  - `ayanamsa_mode` 'LAHIRI' | 'TRUE_CITRA' | 'TRUE_LAHIRI' | 'KP' | 'FAGAN' | 'RAMAN' | 'USHASHASHI' | 'YUKTESHWAR' | 'SURYASIDDHANTA' | 'SURYASIDDHANTA_MSUN' | 'ARYABHATA' | 'ARYABHATA_MSUN' | 'SS_CITRA' | 'TRUE_REVATI' | 'SS_REVATI' | 'TRUE_PUSHYA' | 'TRUE_MULA' | 'KP-SENTHIL' | 'SENTHIL': Ayanamsa (sidereal zodiac) to use. Case-insensitive. A value the API does not recognise as one of the listed modes is refused with HTTP 422 and a message listing them; it is never replaced by LAHIRI.
  - `node_type` 'mean' | 'true': Rahu and Ketu as the mean or the true lunar node.
  - `timezone_mode` 'auto' | 'file': auto works out the historical offset from the coordinates and date, falling back to timezone where no zone is known. file uses timezone exactly as sent. The response reports the offset used.
  - `target_date` string, required: The date to read transits for, YYYY-MM-DD.
  - `target_time` string: Time on the target date, HH:MM:SS. Defaults to local noon.
  - `event_place` string: Name of the place the transit is read for. Defaults to the birth place.
  - `event_latitude` number: Latitude of the event place. Defaults to the birth latitude.
  - `event_longitude` number: Longitude of the event place. Defaults to the birth longitude.
  - `event_timezone` number: UTC offset of the event place, in hours. The API works out the offset from the event coordinates where it can; this value, or the birth offset, is the fallback.
  - `event_elevation` number: Elevation of the event place, in metres.
  - `include` string[]: Optional sections: "ashtakavarga", "gochara_phala", "transit_charts". All three are included by default; pass [] for none, or a subset.

## Response `200`

Success

- object
  - `birth_details` object: The birth inputs as used. Keys: date, time, place, latitude, longitude, timezone.
  - `gochara` object: The transit snapshot. Keys: target, natal_ref, panchanga, muhurta, planets, person_strength, transit_charts.

## Other responses

- `400`: The input cannot be used for this calculation. The detail says why.
- `422`: A field is missing or out of range. The detail says which.
- `429`: Rate limit exceeded.

---

[API](https://skmtc.dev/jagannathahora/apis/vedic-astrology-calculation-api.md) · [All operations](https://skmtc.dev/jagannathahora/apis/vedic-astrology-calculation-api/llms.txt) · [OpenAPI document](https://skmtc.dev/jagannathahora/apis/vedic-astrology-calculation-api/revisions/bb90e41e2ba1?raw)