POST/api/astro/krishnamurti/1 credit

Krishnamurti paddhati

Krishnamurti Paddhati is the South Indian school that reads a chart from house cusps rather than whole signs. This endpoint builds a KP framework: Placidus cusps, each house running from its own cusp to the next house's cusp, and every body assigned to whichever of those spans its longitude falls in. Use ascendant, houses, house_rashis, planet_houses and planet_longs to read the chart. Two of them, ascendant and planet_longs, need the notation field: send 'astrological' for sign-and-degree objects, or 'degree' for raw decimal degrees. adjust_houses is different in kind. It is a mutator: it moves the whole framework so the first house begins at the longitude you give in new_start, keeps each house's original width, and recomputes the house signs and planet placements. It returns null itself, and because keys are executed in the order you list them, it has to appear first in the keys array for the other keys in the same call to reflect the shift. This is how a KP practitioner rectifies a birth time by nudging the ascendant.

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

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.
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.
new_start	number (double)	required
notation	string	required	`degreeastrological` Required by the 'ascendant', 'houses' and 'planet_longs' keys. 'astrological' converts longitudes to sign+degree form; any other value (conventionally 'degree', the engine default) returns raw decimal degrees. No exception is raised for other values.
timezone_as_float	number (double)	required	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
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. min -89.9 · max 89.9
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. min -180 · max 180

Available keys (6)

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
adjust_houses	new_start	Re-anchors the twelve houses so the first begins at the longitude given in new_start (degrees 0-360), keeping each house's original width from the Placidus calculation, then recomputes the house signs and the planets' house placements. It returns null itself — the point is the side effect, so list it before ascendant, houses, house_rashis, planet_houses or planet_longs in the same keys array, since keys are executed in the order you send them.
ascendant	notation	The KP ascendant, which here is the starting longitude of the first house — the first Placidus cusp, or whatever adjust_houses last set it to. With notation 'astrological' it returns {degree, sign, minutes, seconds}, sign being a two-letter abbreviation such as 'Ar' or 'Cp'; with any other value, including the conventional 'degree', it returns a single decimal number of degrees.
house_rashis	—	The sign in which each of the twelve houses begins, as a list of twelve two-letter abbreviations ('Ar' through 'Pi') in house order. Taken from the start of each adjusted house, so with unequal cusps consecutive houses can share a sign or a sign can be skipped entirely.
houses	notation	The KP-adjusted houses, keyed `1` to `12`, each `{start, mid, end}`. This is not the same shape as the `houses` key on /api/astro/house/, which returns a `cusp` rather than a `mid`; here `mid` is the midpoint of the adjusted range, not a computed cusp. `notation` controls the units, as elsewhere.
planet_houses	—	Which house each body falls in, as an object keyed sun, moon, mercury, venus, mars, jupiter, saturn, uranus, neptune, pluto, northtruenode, northmeannode, southtruenode and southmeannode, with integer house numbers 1-12. Both the true and mean node are given, and each south node is its north node plus 180 degrees.
planet_longs	notation	The sidereal longitude of the same fourteen bodies, keyed the same way as planet_houses. With notation 'astrological' each value is {degree, sign, minutes, seconds}; otherwise each is a plain decimal number of degrees from 0 to 360.

Example request

curl -X POST https://yogataraapi.prahlad.app/api/astro/krishnamurti/ \
  -H "X-API-Key: $OCCULT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"keys":["adjust_houses"],"latitude":26.1046,"longitude":74.319,"timezone_as_float":5.5,"new_start":50,"notation":"degree","date_time":"2026-09-01T06:00:00+05:30"}'

Response

{
  "data": {
    "adjust_houses": null
  },
  "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.