POSThttps://yogataraapi.prahlad.app/api/astro/effect_house_lord_different_house/

House lord placements

Request bodyJSON

Paste an API key above to send.

Code snippet

curl -X POST https://yogataraapi.prahlad.app/api/astro/effect_house_lord_different_house/ \
  -H "X-API-Key: $OCCULT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"keys":["get_effect_house_lord_different_house"],"house":"lagnesha","h2":"lagna"}'

The lord of a house carries that house's affairs into whichever house it sits in, and the 144 possible pairings — twelve lords in twelve houses — are one of the oldest interpretive tables in Vedic astrology. The lord of the 2nd in the 11th says something about money that the lord of the 2nd in the 12th does not. This endpoint is that table, looked up directly. It performs no calculation and takes no birth data: you tell it which lord and which house, and it returns the classical reading. Get the placements themselves from /api/astro/chart/ or /api/astro/chart_analysis/ and use this to caption them. `house` is the lord, named in the '-esha' form: lagnesha for the 1st lord through vyayesha for the 12th. `h2` is the house it occupies, named as a bare bhava: lagna, dhana, sahaja, sukha, mantra, ari, dara, randhra, bhagya, karma, labha, vyaya. Watch the sixth, which is 'shashthesha' as a lord but 'ari' as a house. Casing does not matter, and an unrecognised name returns HTTP 200 with an explanatory string.

Request fields

Field Type Required Notes

string

Field	Type	Required	Notes
h2	string	required	`lagnadhanasahajasukhamantraaridararandhrabhagyakarmalabhavyaya` The HOUSE that lord occupies (bare bhava name): lagna = 1st... vyaya = 12th. Note the 6th is 'ari' here (not 'shashtha'. An unknown value returns 200 with "Invalid key: <x>".
house	string	required	`lagneshadhaneshasahajeshasukheshamantreshashashtheshadaresharandhreshabhagyeshakarmeshalabheshavyayesha` The HOUSE LORD (the '-esha' form): lagnesha = 1st lord... vyayesha = 12th lord. Lowercased by so casing does not matter. An unknown value returns HTTP 200 with the string "Invalid key: <x>" rather than an error status.
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. `get_effect_house_lord_different_house` Array of strings; only one key exists.

required

lagnadhanasahajasukhamantraaridararandhrabhagyakarmalabhavyaya

The HOUSE that lord occupies (bare bhava name): lagna = 1st... vyaya = 12th. Note the 6th is 'ari' here (not 'shashtha'. An unknown value returns 200 with "Invalid key: <x>".

house

string

required

lagneshadhaneshasahajeshasukheshamantreshashashtheshadaresharandhreshabhagyeshakarmeshalabheshavyayesha

The HOUSE LORD (the '-esha' form): lagnesha = 1st lord... vyayesha = 12th lord. Lowercased by so casing does not matter. An unknown value returns HTTP 200 with the string "Invalid key: <x>" rather than an error status.

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.

get_effect_house_lord_different_house

Array of strings; only one key exists.

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
	get_effect_house_lord_different_house	house, h2	The classical results of placing the house lord named in `house` in the house named in `h2`, as a list of short English statements. An unrecognised value for either field returns the string "Invalid key: <value>" with a 200 status rather than an error.

Full reference for this endpoint