curl -X POST https://yogataraapi.prahlad.app/api/planetary_details/ \
-H "X-API-Key: $OCCULT_API_KEY" \
-H "Content-Type: application/json" \
-d '{"start_date":"2024-11-21T08:33:35.539Z","end_date":"2024-11-22T08:33:35.539Z","longitude":76.125,"planet_name":"mercury","sign":"Taurus"}'A single call that runs nine separate ephemeris scans over a date range and returns them together. It is the endpoint to reach for when you want everything that happens to the planets between two dates rather than a snapshot: sign and nakshatra changes, retrograde spells, declination alignments and out-of-bounds excursions. `start_date` and `end_date` bound the window, `planet_name` and `sign` narrow the three planet-specific sections, and `longitude` is the ecliptic degree tested by the position search. Supplying `geo_latitude` and `geo_longitude` adds an extra section for ascendant ingress and is otherwise omitted. Note that the window is scanned in full, so a multi-year range is considerably slower than a few days. The response holds, under keys with spaces in their names, `sign transitions`, `planet at position` (when the named planet sits at the given longitude in the given sign), `planet ingress exit` (entry and exit times for the named planet in the named sign only), `planet nakshatra ingress exit` (keyed by all twenty-seven nakshatras, each a list of `{start_date, end_date}` windows), `planet sankranti times` (keyed by every supported body, including the Uranian points and planetary moons), `planet retrogression dates` (keyed by planet, each a list of `{start, end}`), `planet krantisamya dates` (a list of `{Planet_1, Planet_2, DateTime, Alignment}` where Alignment is North-North, South-South or Opposite, that is, equal or mirrored declination), `abhijit nakshatra periods` and `planet oob range` (the spells when the body is beyond the Sun's maximum declination). Empty lists mean nothing of that kind happened inside your window.
| Field | Type | Required | Notes |
|---|---|---|---|
| end_date | string (date-time) | required | |
| longitude | number (double) | required | Longitude of the place, in decimal degrees. Positive is east, negative is west. Example: 75.7873 for Jaipur, -74.0060 for New York. Note the sign: a missing minus puts New York in China. min -180 · max 180 |
| planet_name | string | required | sunmoonmercuryvenusmarsjupitersaturnuranusneptuneplutotruenodemeannodeOne of: sun, moon, mercury, venus, mars, jupiter, saturn, uranus, neptune, pluto, truenode, meannode. Lowercase. Other swisseph body names are accepted by validation but have no data and will fail. |
| sign | string | required | AriesTaurusGeminiCancerLeoVirgoLibraScorpioSagittariusCapricornAquariusPiscesCASE-SENSITIVE - Title-case English sign names exactly as spelled; 'aries' fails. Also used at to filter the ingress/exit result down to the requested sign. |
| start_date | string (date-time) | required | |
| geo_latitude | number (double) | optional | Observer geographic latitude (-90 to 90). Required for ascendant entry data. min -90 · max 90 |
| geo_longitude | number (double) | optional | Observer geographic longitude (-180 to 180). Required for ascendant entry data. min -180 · max 180 |