POST/api/astro/naadi_marriage_prediction/1 credit

Naadi marriage yogas

A short set of marriage indications from the Naadi tradition, following Satyanarayana Naik's presentation of Rao's system. Rather than weighing the seventh house, it looks only at which planets aspect the marriage significator — Venus for one gender, Mars for the other — reading Jupiter or Saturn as promising the marriage, Jupiter alone as early and Saturn alone as late, and Ketu or Rahu as obstruction or delay. Pass the birth date and time, the place, timezone and gender: 0 uses Venus as the significator, 1 uses Mars. The single key check_marriage_yogas returns four numbered results, each a boolean and an explanatory string. This is a narrow, four-rule reading and is best used as one input among several. For marriage timing use the dasha and transit endpoints, and for compatibility between two charts use the matching endpoints.

https://yogataraapi.prahlad.app/api/astro/naadi_marriage_prediction/

Test Request

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/json

Request 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.
gender	integer	required
keys	array	required	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)	required	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. min -90 · max 90
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
timezone	number (double)	required	UTC offset of the place, in hours, as a decimal. Example: 5.5 for India (UTC+05:30). Identical in meaning to timezone_as_float, which other endpoints call the same thing by a different name.

Available keys (1)

Ask for exactly the calculations you want by listing them in keys. An unknown key rejects the whole request, and you are charged 1 credit however many you ask for — so batch them.

Key	Extra fields needed	Description
check_marriage_yogas	gender	Four marriage indications read from whether Jupiter, Saturn, Ketu or Rahu aspect the marriage significator — Venus when gender is 0, Mars when it is 1. Returns an object keyed yoga_1 to yoga_4, each a [boolean, string] pair: yoga_1 whether marriage is indicated at all, yoga_2 whether it is early, late or neither, yoga_3 Ketu's aspect (obstacles and disputes with the spouse) and yoga_4 Rahu's (delay, or dislike of the spouse). The string is empty when yoga_3 or yoga_4 does not apply.

Example request

curl -X POST https://yogataraapi.prahlad.app/api/astro/naadi_marriage_prediction/ \
  -H "X-API-Key: $OCCULT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"keys":["check_marriage_yogas"],"date_time":"2025-07-09T10:28:22.014Z","latitude":26.9124,"longitude":75.7873,"timezone":0,"gender":0}'

Response

{
  "data": {
    "check_marriage_yogas": {
      "yoga_1": [
        false,
        "Obstacles in marriage, if married, disputes with spouse"
      ],
      "yoga_2": [
        false,
        "Neither Early/Late Marriage"
      ],
      "yoga_3": [
        false,
        ""
      ],
      "yoga_4": [
        false,
        ""
      ]
    }
  },
  "status": 200,
  "is_error": false,
  "message": "successful"
}

Captured from a real call using the exact request above. Results sit under data, keyed by what you requested.

Errors

Metering errors return { "error": "…", "message": "<code>", "is_error": true }. Show error to people and branch on message. See the error reference.