/api/astro/return/to-degree/1 creditReturn to a degree
When a body reaches an arbitrary ecliptic degree rather than its natal one. What demi- and quarter-returns are built from: a demi-solar return is the Sun opposite its natal place, so pass the natal longitude plus 180. It also answers plain ingress questions — when does Jupiter next reach 0 Aries — without needing a birth chart at all. Retrograde bodies cross a degree up to three times, and all the passes are returned.
https://yogataraapi.prahlad.app/api/astro/return/to-degree/Authentication
Send your key in the X-API-Key header. Keys are server-side credentials — never put one in browser JavaScript or a mobile app.
X-API-Key: yt_live_a1b2c3d4_…
Content-Type: application/jsonRequest fields
| Field | Type | Required | Notes |
|---|---|---|---|
| date_time | string (date-time) | required | The moment to calculate for, ISO 8601. ALWAYS include an offset or a trailing Z - a value with no zone is read as Asia/Kolkata (UTC+05:30), not UTC, and can return the previous day's result with a 200. '2026-09-01T06:00:00Z' and '2026-09-01 06:00:00' are different instants and give different answers. |
| target_longitude | number (double) | required | Ecliptic longitude to return to, 0-360 from 0 Aries. min 0 · max 360 |
| body | string | optional | jupitermarsmercurymoonneptuneplutosaturnsunuranusvenus |
| count | integer | optional | How many consecutive returns to report, at most 24. min 1 · max 24 |
| keys | array | optional | Which calculations to return, as a list of names. See the key table for this endpoint; an unrecognised name rejects the whole request. One call costs one credit however many keys you ask for, so request everything you need at once rather than making several calls. |
| latitude | number (double) | optional | Latitude of the place, in decimal degrees. Positive is north, negative is south. Example: 26.9124 for Jaipur, 40.7128 for New York. Minutes and seconds are not accepted - convert first. |
| longitude | number (double) | optional | 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. |
| search_from | string (date-time) | optional | Start looking here instead of at the birth moment. |
| timezone_as_float | number (double) | optional | UTC offset of the place, in hours, as a decimal. Example: 5.5 for India (UTC+05:30), -5 for New York in winter, 5.75 for Nepal. This is NOT validated against date_time - if the two disagree you get a successful response for the wrong moment, so derive both from the same source. Use the offset in force on that date, not today's: a summer birth in a country with daylight saving needs the summer offset. min -12 · max 14 |
Example request
curl -X POST https://yogataraapi.prahlad.app/api/astro/return/to-degree/ \
-H "X-API-Key: $OCCULT_API_KEY" \
-H "Content-Type: application/json" \
-d '{"date_time":"1990-05-10T19:55:00+05:30","timezone_as_float":5.5,"body":"sun","target_longitude":229.667,"search_from":"2026-01-01T00:00:00+00:00","count":1}'Response
{
"data": {
"body": "sun",
"natal_longitude": 229.667,
"sign": "Scorpio",
"sign_index": 8,
"degree_in_sign": 19.667,
"natal_datetime_utc": "1990-05-10T14:25:00Z",
"count": 1,
"returns": [
{
"exact": "2026-11-12T01:20:13Z",
"pass_count": 1,
"passes": [
{
"body": "sun",
"datetime_utc": "2026-11-12T01:20:13Z",
"julian_day_ut": 2461356.55570795,
"longitude": 229.667,
"error_arcseconds": 0,
"retrograde": false,
"sign": "Scorpio",
"sign_index": 8,
"degree_in_sign": 19.667
}
]
}
],
"target_longitude": 229.667
},
"status": 200,
"is_error": false,
"message": "successful"
}Captured from a real call using the exact request above. Results sit under data.
Errors
Metering errors return { "error": "…", "message": "<code>", "is_error": true }. Show error to people and branch on message. See the error reference.