{"forms":{"analyzeKarmicLessons":{"fields":[{"description":"Full birth name to analyze for missing numbers. A name in any script is converted to Latin letters before it is counted, Cyrillic and Greek as the passport spelling and accents folded to the base letter, and the calculation lists the letters counted. For a script that does not write its vowels, send the Latin spelling the person uses.","example":"John William Smith","key":"fullName","kind":"text","name":"fullName","required":true}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/numerology/karmic-lessons","title":"Analyze Karmic Lessons"},"analyzeNumberSequence":{"fields":[{"description":"Number sequence to analyze (1-8 digits). Can be any number the user has encountered: clock times (1111), addresses (717), receipts (888), license plates (4444), or any repeating pattern.","example":"1234","inQuery":true,"key":"number","kind":"text","name":"number","required":true},{"description":"Where the number was seen. When supplied, the response adds a contextNote tailoring the reading to the sighting: clock (a glanced time), receipt (a purchase), license-plate (in transit), phone (a call or notification), address (a home or place), price (a total or amount).","enum":["clock","receipt","license-plate","phone","address","price"],"example":"clock","fold":true,"inQuery":true,"key":"context","kind":"tiles","name":"context","required":false}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":false,"path":"/angel-numbers/lookup","title":"Analyze any number sequence"},"calculateAnnualForecast":{"fields":[{"description":"Birth date in YYYY-MM-DD format. Sets the year, month and day pillars. The year pillar turns at Beginning of Spring rather than on 1 January, and the month pillar turns at each of the twelve minor solar terms rather than at a calendar month boundary.","example":"1990-06-15","key":"date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Sets the hour pillar, which is one of the four and carries the whole picture of later life and offspring. Each Earthly Branch covers two hours, so a birth within a few minutes of an odd hour can land in either. All four pillars are read in the local clock of the birth, and the day boundary is applied in that same clock; only the lunisolar calendar date itself is a world constant, fixed at UTC plus 8 so one instant has one Chinese date everywhere.","example":"14:30:00","key":"time","kind":"time","name":"time","required":true},{"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error.","example":"America/New_York","key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":true,"role":"location"},{"default":0,"description":"Birth latitude in decimal degrees. Accepted for consistency with the other birth-data endpoints and does not affect any part of a BaZi chart. Defaults to 0.","example":0,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":false,"role":"location"},{"description":"Birth longitude in decimal degrees. Positive is East, negative is West. Required when hourClock is \"local-mean\" or \"solar\", which shift the hour branch to the sun over the birth place; omitting it in either case returns 400. Ignored when hourClock is \"clock\".","example":116.4,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":false,"role":"location"},{"default":"split-zi","description":"Which instant starts the sexagenary DAY, which only matters for a birth between 23:00 and 23:59. \"midnight\" is the classical position of the Ming compendium San Ming Tong Hui: the day turns at 00:00 and 23:00 to 23:59 is the late zi hour of the day that is ending, so the hour stem is taken from that day. \"early-zi\" turns the whole day at 23:00, the practice in Hong Kong, Taiwan and much of South East Asia. \"split-zi\" is the compromise most software implements and the default here: the day still turns at 00:00, but the hour stem is taken from the next day. The three give three different answers for a late-evening birth and identical answers for every other birth.","enum":["split-zi","midnight","early-zi"],"example":"split-zi","fold":true,"key":"dayBoundary","kind":"tiles","name":"dayBoundary","required":false},{"default":"li-chun","description":"Which instant starts the sexagenary YEAR. \"li-chun\" is Beginning of Spring, around 4 February, and is the classical rule every BaZi text uses, so it is the default on this endpoint. \"lunar-new-year\" is the folk rule people mean when they say which animal they are, and it falls between late January and late February. The two disagree for any birth in the weeks between them: 14 February 2026 is a Wood Snake year under lunar-new-year and a Fire Horse year under li-chun.","enum":["li-chun","lunar-new-year"],"example":"li-chun","fold":true,"key":"yearBoundary","kind":"tiles","name":"yearBoundary","required":false},{"default":"clock","description":"Which clock the day boundary and the hour branch are read from, so a correction that carries a birth across midnight moves the day pillar with the hour. \"clock\" is civil time exactly as a birth certificate records it, which is what most calculators use and the default here. \"local-mean\" shifts to the mean sun over the birth longitude, a correction of up to 59 minutes at the edge of a wide time zone. \"solar\" adds the equation of time on top of that, up to a further 16 minutes. Both non-civil options need \"longitude\" in the request and return 400 without it.","enum":["clock","local-mean","solar"],"example":"clock","fold":true,"key":"hourClock","kind":"tiles","name":"hourClock","required":false},{"description":"Gregorian year to read against the natal chart. The annual pillar for that year is resolved under the same year boundary the request selected, so a li-chun reading and a lunar-new-year reading of the same calendar year can differ.","example":2026,"key":"year","kind":"number","max":2649,"min":1551,"name":"year","required":true}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/chinese-astrology/bazi/annual-forecast","title":"Calculate BaZi annual forecast"},"calculateArabicLots":{"fields":[{"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15","key":"date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00","key":"time","kind":"time","name":"time","required":true},{"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","example":40.7128,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","example":-74.006,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time.","example":"America/New_York","key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":true,"role":"location"},{"default":"true","description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"example":"true","fold":true,"key":"nodeType","kind":"tiles","name":"nodeType","required":false},{"default":"placidus","description":"House system used to place the Sun, which determines the chart sect (day when the Sun is above the horizon, night when below) and therefore which lot formula applies. Placidus (default), Whole Sign, Equal, or Koch.","enum":["placidus","whole-sign","equal","koch"],"example":"placidus","fold":true,"key":"houseSystem","kind":"tiles","name":"houseSystem","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/astrology/arabic-lots","title":"Arabic lots calculator"},"calculateArudhaPadas":{"fields":[{"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04","key":"date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00","key":"time","kind":"time","name":"time","required":true},{"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","example":28.6139,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","example":77.209,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"default":5.5,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time. Defaults to 5.5.","example":5.5,"key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"role":"location"},{"default":"lahiri","description":"Sidereal frame (ayanamsa) the chart is cast in. \"lahiri\" is Lahiri/Chitrapaksha, the traditional Vedic standard used by most software, and is the default. \"raman\" is the B.V. Raman ayanamsa from Hindu Predictive Astrology, about 1.45 degrees below Lahiri. \"kp-newcomb\" and \"kp-old\" are the two Krishnamurti Paddhati frames. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"example":"lahiri","fold":true,"key":"ayanamsa","kind":"tiles","name":"ayanamsa","required":false},{"description":"Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.","example":24,"fold":true,"key":"ayanamsaValue","kind":"number","name":"ayanamsaValue","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/vedic-astrology/arudha","title":"Get the twelve Arudha padas"},"calculateAshtakavarga":{"fields":[{"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04","key":"date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00","key":"time","kind":"time","name":"time","required":true},{"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","example":28.6139,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","example":77.209,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"default":5.5,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time. Defaults to 5.5.","example":5.5,"key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"role":"location"},{"default":"lahiri","description":"Sidereal frame (ayanamsa) the chart is cast in. \"lahiri\" is Lahiri/Chitrapaksha, the traditional Vedic standard used by most software, and is the default. \"raman\" is the B.V. Raman ayanamsa from Hindu Predictive Astrology, about 1.45 degrees below Lahiri. \"kp-newcomb\" and \"kp-old\" are the two Krishnamurti Paddhati frames. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"example":"lahiri","fold":true,"key":"ayanamsa","kind":"tiles","name":"ayanamsa","required":false},{"description":"Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.","example":24,"fold":true,"key":"ayanamsaValue","kind":"number","name":"ayanamsaValue","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":false,"method":"POST","opensOnLoad":false,"path":"/vedic-astrology/ashtakavarga","title":"Get Ashtakavarga (planetary strength) analysis"},"calculateAspects":{"fields":[{"description":"Date in YYYY-MM-DD format","example":"1990-07-15","key":"date","kind":"date","name":"date","required":true},{"description":"Time in HH:MM:SS format (24-hour)","example":"14:30:00","key":"time","kind":"time","name":"time","required":true},{"city":true,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time.","example":"America/New_York","key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":true},{"description":"Optional: specific bodies to calculate aspects for (defaults to all 14: the 10 classical planets, the lunar nodes, Chiron, and Black Moon Lilith)","example":["Sun","Moon","Mercury","Venus","Mars"],"fold":true,"key":"planets","kind":"array","name":"planets","required":false},{"description":"Optional: specific aspect types to find (defaults to all 9)","example":["CONJUNCTION","OPPOSITION","TRINE","SQUARE"],"fold":true,"key":"aspectTypes","kind":"array","name":"aspectTypes","required":false}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/astrology/aspects","title":"Calculate planetary aspects"},"calculateAyadi":{"fields":[{"description":"Length of the building or room, in the unit given. Under the Manasara family this is the measure the aya and rksha formulas multiply; under the perimeter family it only feeds the perimeter.","example":11,"key":"length","kind":"number","min":0,"name":"length","required":true},{"description":"Breadth of the building or room, in the unit given. Under the Manasara family this is the measure the vyaya and yoni formulas multiply.","example":11,"key":"breadth","kind":"number","min":0,"name":"breadth","required":true},{"description":"Perimeter of the plan, if it is not simply twice the length plus twice the breadth. The perimeter family runs every formula on this one measure, so it is the number that decides all six remainders there.","example":11,"fold":true,"key":"perimeter","kind":"number","min":0,"name":"perimeter","required":false},{"description":"Circumference or height, if the Manasara vara and tithi formulas should read something other than the perimeter. Defaults to the perimeter, which is what a rectangular plan supplies.","example":11,"fold":true,"key":"circumference","kind":"number","min":0,"name":"circumference","required":false},{"default":"hasta","description":"Unit the Ayadi dimensions are given in. Every remainder is unit sensitive, so this is an input and never assumed: the same building measured in cubits and in feet gives different remainders. hasta is the classical cubit and needs no conversion; feet and metres are converted using hastaInches and rounded to whole cubits, and the rounded figures are returned. Defaults to hasta.","enum":["hasta","feet","metres"],"example":"hasta","fold":true,"key":"unit","kind":"tiles","name":"unit","required":false},{"default":18,"description":"Length of one hasta, the classical cubit, in inches. Defaults to 18, which is 24 angula at three quarters of an inch each and is the value three independent sources agree on. Raise it if your lineage measures the cubit differently; the value used is echoed on the response so a stored reading can be reproduced years later. Only used when unit is feet or metres.","example":18,"fold":true,"key":"hastaInches","kind":"number","min":0,"name":"hastaInches","required":false},{"default":"manasara","description":"Which family of Ayadi formulas to apply. manasara takes length, breadth and circumference separately and is double sourced. perimeter-texts runs every formula on the perimeter alone and is the family the usual worked example is printed for. utpala supplies a yoni formula from the length times the breadth and nothing else, so the other five vargas fall back to the perimeter family and the response says so. Defaults to manasara.","enum":["manasara","perimeter-texts","utpala"],"example":"manasara","fold":true,"key":"ayadiText","kind":"tiles","name":"ayadiText","required":false},{"default":"p9-10","description":"Which vyaya formula the perimeter family uses. The printed table gives two joined by the word or and states no rule for choosing. p9-10 multiplies by nine and divides by ten, which is the only divisor consistent with the ten member vyaya group, so its remainder can be placed in that group and it is the default. p3-14 multiplies by three and divides by fourteen, and its remainder maps to no group any source enumerates. Ignored when ayadiText is manasara, which has one vyaya formula.","enum":["p9-10","p3-14"],"example":"p9-10","fold":true,"key":"vyayaFormula","kind":"tiles","name":"vyayaFormula","required":false}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/vastu/ayadi","title":"Calculate Ayadi shadvarga"},"calculateAyurvedicConstitution":{"fields":[{"description":"Birth date in YYYY-MM-DD format. It sets the sidereal positions the whole reading is built from, so an approximate date gives an approximate constitution.","example":"1990-07-04","key":"date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. The rising sign turns roughly every two hours and carries the heaviest weight of the three factors, so time is the input a reading is most sensitive to.","example":"10:12:00","key":"time","kind":"time","name":"time","required":true},{"description":"Birth latitude in decimal degrees. It sets the local sidereal time behind the rising sign, and it feeds the strength of each graha through the sunrise at that place.","example":28.6139,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Birth longitude in decimal degrees. It sets the local sidereal time behind the rising sign, together with the latitude.","example":77.209,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"default":5.5,"description":"Timezone as an IANA name such as \"Asia/Kolkata\", or as decimal hours from UTC such as 5.5. An IANA name is resolved to the offset in force on the birth date, so a summer-time birth is placed correctly. Defaults to 5.5.","example":5.5,"key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"role":"location"},{"default":"lahiri","description":"Sidereal frame the chart is cast in. \"lahiri\" is the traditional Vedic standard used by most software and is the default. \"raman\" sits about 1.45 degrees below it. \"kp-newcomb\" and \"kp-old\" are the two Krishnamurti Paddhati frames. \"custom\" takes your own value in degrees via ayanamsaValue. The frame rotates the whole zodiac, so a graha within 1.45 degrees of a boundary can change rashi when you switch, which moves both sign factors of the reading.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"example":"lahiri","fold":true,"key":"ayanamsa","kind":"tiles","name":"ayanamsa","required":false},{"description":"Custom sidereal frame value in degrees. Required when ayanamsa is \"custom\" and ignored otherwise. Use it to reconcile exactly against a specific reference program.","example":24,"fold":true,"key":"ayanamsaValue","kind":"number","name":"ayanamsaValue","required":false},{"default":"satyacharya","description":"Which classical sign table the rising sign and the Moon sign are read through. \"satyacharya\" is the twelve-sign extract appended to Brihat Jataka 18.20, carried in two independent public-domain translations that agree on all twelve rows, and is the default. \"bphs\" is the Brihat Parasara Hora Sastra rule by elemental triplicity. The two agree exactly on three signs of twelve, overlap in part on seven, and share no humour at all on Scorpio or Sagittarius, so the choice can change the reading outright and is echoed in the response.","enum":["satyacharya","bphs"],"example":"satyacharya","fold":true,"key":"signDoshaScheme","kind":"tiles","name":"signDoshaScheme","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/ayurveda/constitution","title":"Ayurvedic constitution from a birth chart"},"calculateBaziCompatibility":{"fields":[{"description":"Birth date in YYYY-MM-DD format. Sets the year, month and day pillars. The year pillar turns at Beginning of Spring rather than on 1 January, and the month pillar turns at each of the twelve minor solar terms rather than at a calendar month boundary.","example":"1990-06-15","group":"personA","key":"personA.date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Sets the hour pillar, which is one of the four and carries the whole picture of later life and offspring. Each Earthly Branch covers two hours, so a birth within a few minutes of an odd hour can land in either. All four pillars are read in the local clock of the birth, and the day boundary is applied in that same clock; only the lunisolar calendar date itself is a world constant, fixed at UTC plus 8 so one instant has one Chinese date everywhere.","example":"14:30:00","group":"personA","key":"personA.time","kind":"time","name":"time","required":true},{"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error.","example":"America/New_York","group":"personA","key":"personA.timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":true,"role":"location"},{"default":0,"description":"Birth latitude in decimal degrees. Accepted for consistency with the other birth-data endpoints and does not affect any part of a BaZi chart. Defaults to 0.","example":0,"group":"personA","key":"personA.latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":false,"role":"location"},{"description":"Birth longitude in decimal degrees. Positive is East, negative is West. Required when hourClock is \"local-mean\" or \"solar\", which shift the hour branch to the sun over the birth place; omitting it in either case returns 400. Ignored when hourClock is \"clock\".","example":116.4,"group":"personA","key":"personA.longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":false,"role":"location"},{"default":"split-zi","description":"Which instant starts the sexagenary DAY, which only matters for a birth between 23:00 and 23:59. \"midnight\" is the classical position of the Ming compendium San Ming Tong Hui: the day turns at 00:00 and 23:00 to 23:59 is the late zi hour of the day that is ending, so the hour stem is taken from that day. \"early-zi\" turns the whole day at 23:00, the practice in Hong Kong, Taiwan and much of South East Asia. \"split-zi\" is the compromise most software implements and the default here: the day still turns at 00:00, but the hour stem is taken from the next day. The three give three different answers for a late-evening birth and identical answers for every other birth.","enum":["split-zi","midnight","early-zi"],"example":"split-zi","group":"personA","key":"personA.dayBoundary","kind":"tiles","name":"dayBoundary","required":false},{"default":"li-chun","description":"Which instant starts the sexagenary YEAR. \"li-chun\" is Beginning of Spring, around 4 February, and is the classical rule every BaZi text uses, so it is the default on this endpoint. \"lunar-new-year\" is the folk rule people mean when they say which animal they are, and it falls between late January and late February. The two disagree for any birth in the weeks between them: 14 February 2026 is a Wood Snake year under lunar-new-year and a Fire Horse year under li-chun.","enum":["li-chun","lunar-new-year"],"example":"li-chun","group":"personA","key":"personA.yearBoundary","kind":"tiles","name":"yearBoundary","required":false},{"default":"clock","description":"Which clock the day boundary and the hour branch are read from, so a correction that carries a birth across midnight moves the day pillar with the hour. \"clock\" is civil time exactly as a birth certificate records it, which is what most calculators use and the default here. \"local-mean\" shifts to the mean sun over the birth longitude, a correction of up to 59 minutes at the edge of a wide time zone. \"solar\" adds the equation of time on top of that, up to a further 16 minutes. Both non-civil options need \"longitude\" in the request and return 400 without it.","enum":["clock","local-mean","solar"],"example":"clock","group":"personA","key":"personA.hourClock","kind":"tiles","name":"hourClock","required":false},{"description":"Birth date in YYYY-MM-DD format. Sets the year, month and day pillars. The year pillar turns at Beginning of Spring rather than on 1 January, and the month pillar turns at each of the twelve minor solar terms rather than at a calendar month boundary.","example":"1990-06-15","group":"personB","key":"personB.date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Sets the hour pillar, which is one of the four and carries the whole picture of later life and offspring. Each Earthly Branch covers two hours, so a birth within a few minutes of an odd hour can land in either. All four pillars are read in the local clock of the birth, and the day boundary is applied in that same clock; only the lunisolar calendar date itself is a world constant, fixed at UTC plus 8 so one instant has one Chinese date everywhere.","example":"14:30:00","group":"personB","key":"personB.time","kind":"time","name":"time","required":true},{"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error.","example":"America/New_York","group":"personB","key":"personB.timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":true,"role":"location"},{"default":0,"description":"Birth latitude in decimal degrees. Accepted for consistency with the other birth-data endpoints and does not affect any part of a BaZi chart. Defaults to 0.","example":0,"group":"personB","key":"personB.latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":false,"role":"location"},{"description":"Birth longitude in decimal degrees. Positive is East, negative is West. Required when hourClock is \"local-mean\" or \"solar\", which shift the hour branch to the sun over the birth place; omitting it in either case returns 400. Ignored when hourClock is \"clock\".","example":116.4,"group":"personB","key":"personB.longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":false,"role":"location"},{"default":"split-zi","description":"Which instant starts the sexagenary DAY, which only matters for a birth between 23:00 and 23:59. \"midnight\" is the classical position of the Ming compendium San Ming Tong Hui: the day turns at 00:00 and 23:00 to 23:59 is the late zi hour of the day that is ending, so the hour stem is taken from that day. \"early-zi\" turns the whole day at 23:00, the practice in Hong Kong, Taiwan and much of South East Asia. \"split-zi\" is the compromise most software implements and the default here: the day still turns at 00:00, but the hour stem is taken from the next day. The three give three different answers for a late-evening birth and identical answers for every other birth.","enum":["split-zi","midnight","early-zi"],"example":"split-zi","group":"personB","key":"personB.dayBoundary","kind":"tiles","name":"dayBoundary","required":false},{"default":"li-chun","description":"Which instant starts the sexagenary YEAR. \"li-chun\" is Beginning of Spring, around 4 February, and is the classical rule every BaZi text uses, so it is the default on this endpoint. \"lunar-new-year\" is the folk rule people mean when they say which animal they are, and it falls between late January and late February. The two disagree for any birth in the weeks between them: 14 February 2026 is a Wood Snake year under lunar-new-year and a Fire Horse year under li-chun.","enum":["li-chun","lunar-new-year"],"example":"li-chun","group":"personB","key":"personB.yearBoundary","kind":"tiles","name":"yearBoundary","required":false},{"default":"clock","description":"Which clock the day boundary and the hour branch are read from, so a correction that carries a birth across midnight moves the day pillar with the hour. \"clock\" is civil time exactly as a birth certificate records it, which is what most calculators use and the default here. \"local-mean\" shifts to the mean sun over the birth longitude, a correction of up to 59 minutes at the edge of a wide time zone. \"solar\" adds the equation of time on top of that, up to a further 16 minutes. Both non-civil options need \"longitude\" in the request and return 400 without it.","enum":["clock","local-mean","solar"],"example":"clock","group":"personB","key":"personB.hourClock","kind":"tiles","name":"hourClock","required":false}],"groups":[{"key":"personA","label":"Person A","location":{"fields":["personA.latitude","personA.longitude","personA.timezone"],"required":true}},{"key":"personB","label":"Person B","location":{"fields":["personB.latitude","personB.longitude","personB.timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/chinese-astrology/bazi/compatibility","title":"Calculate BaZi compatibility"},"calculateBhavChalit":{"fields":[{"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04","key":"date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00","key":"time","kind":"time","name":"time","required":true},{"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","example":28.6139,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","example":77.209,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"default":5.5,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time. Defaults to 5.5.","example":5.5,"key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"role":"location"},{"default":"lahiri","description":"Sidereal frame (ayanamsa) the chart is cast in. \"lahiri\" is Lahiri/Chitrapaksha, the traditional Vedic standard used by most software, and is the default. \"raman\" is the B.V. Raman ayanamsa from Hindu Predictive Astrology, about 1.45 degrees below Lahiri. \"kp-newcomb\" and \"kp-old\" are the two Krishnamurti Paddhati frames. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"example":"lahiri","fold":true,"key":"ayanamsa","kind":"tiles","name":"ayanamsa","required":false},{"description":"Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.","example":24,"fold":true,"key":"ayanamsaValue","kind":"number","name":"ayanamsaValue","required":false},{"default":"general","description":"Which signification vocabulary the houseThemes map returns. \"general\" gives the classical bhava significations (self, wealth, siblings, home, and so on). \"finance\" gives the money reading of the same twelve bhavas, so house 2 returns income and savings, 5 speculation and risk appetite, 8 sudden money and leverage, 11 gains and profits, and 12 expenses and capital outflow. Use \"finance\" for wealth, income, business and market timing questions in Krishnamurti Paddhati, where the significator house groups 2, 6, 10, 11 for earned income and 5, 8, 11 for speculation are read against a running dasha. Defaults to \"general\".","enum":["general","finance"],"example":"general","fold":true,"inQuery":true,"key":"focus","kind":"tiles","name":"focus","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/vedic-astrology/bhav-chalit","title":"Get the Bhav Chalit (Chalit Kundli) cusp-based house chart"},"calculateBhavaBala":{"fields":[{"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04","key":"date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00","key":"time","kind":"time","name":"time","required":true},{"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","example":28.6139,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","example":77.209,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"default":5.5,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time. Defaults to 5.5.","example":5.5,"key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"role":"location"},{"default":"lahiri","description":"Sidereal frame (ayanamsa) the chart is cast in. \"lahiri\" is Lahiri/Chitrapaksha, the traditional Vedic standard used by most software, and is the default. \"raman\" is the B.V. Raman ayanamsa from Hindu Predictive Astrology, about 1.45 degrees below Lahiri. \"kp-newcomb\" and \"kp-old\" are the two Krishnamurti Paddhati frames. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"example":"lahiri","fold":true,"key":"ayanamsa","kind":"tiles","name":"ayanamsa","required":false},{"description":"Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.","example":24,"fold":true,"key":"ayanamsaValue","kind":"number","name":"ayanamsaValue","required":false},{"default":"general","description":"Which signification vocabulary the houseThemes map returns. \"general\" gives the classical bhava significations (self, wealth, siblings, home, and so on). \"finance\" gives the money reading of the same twelve bhavas, so house 2 returns income and savings, 5 speculation and risk appetite, 8 sudden money and leverage, 11 gains and profits, and 12 expenses and capital outflow. Use \"finance\" for wealth, income, business and market timing questions in Krishnamurti Paddhati, where the significator house groups 2, 6, 10, 11 for earned income and 5, 8, 11 for speculation are read against a running dasha. Defaults to \"general\".","enum":["general","finance"],"example":"general","fold":true,"inQuery":true,"key":"focus","kind":"tiles","name":"focus","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/vedic-astrology/bhava-bala","title":"Get Bhava Bala (house strength) for all twelve houses"},"calculateBioCompatibility":{"fields":[{"description":"Birth date of person 1 in YYYY-MM-DD format.","example":"1990-07-15","group":"person1","key":"person1.birthDate","kind":"date","name":"birthDate","required":true},{"description":"Birth date of person 2 in YYYY-MM-DD format.","example":"1992-03-22","group":"person2","key":"person2.birthDate","kind":"date","name":"birthDate","required":true},{"description":"Date to evaluate compatibility on in YYYY-MM-DD format. Defaults to today (UTC). Compatibility varies by day since biorhythm cycles are continuous.","example":"2026-04-10","key":"targetDate","kind":"date","moment":true,"name":"targetDate","required":false}],"groups":[{"key":"person1","label":"Person 1"},{"key":"person2","label":"Person 2"},{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/biorhythm/compatibility","title":"Calculate compatibility"},"calculateBirthDay":{"fields":[{"description":"Day of birth (1-31)","example":23,"key":"day","kind":"number","max":31,"min":1,"name":"day","required":true}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/numerology/birth-day","title":"Calculate Birth Day number"},"calculateBridgeNumbers":{"fields":[{"description":"Full birth name as it appears on the birth certificate, first, middle and last names separated by spaces. Used to calculate the Expression, Soul Urge and Personality numbers. A name in any script is converted to Latin letters before it is counted, Cyrillic and Greek as the passport spelling and accents folded to the base letter, and the calculation lists the letters counted. For a script that does not write its vowels, send the Latin spelling the person uses.","example":"John William Smith","key":"fullName","kind":"text","name":"fullName","required":true},{"description":"Birth year between 100 and 2100. Used to calculate the Life Path number via Pythagorean reduction.","example":1990,"key":"year","kind":"number","max":2100,"min":100,"name":"year","required":true},{"description":"Birth month (1 to 12)","example":7,"key":"month","kind":"number","max":12,"min":1,"name":"month","required":true},{"description":"Birth day (1 to 31)","example":15,"key":"day","kind":"number","max":31,"min":1,"name":"day","required":true}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/numerology/bridge","title":"Calculate Bridge Numbers"},"calculateBusinessName":{"fields":[{"description":"The business or brand name to evaluate. A name in any script is converted to Latin letters before it is counted, Cyrillic and Greek as the passport spelling and accents folded to the base letter, and the calculation lists the letters counted. For a script that does not write its vowels, send the Latin spelling the person uses.","example":"Ford","key":"name","kind":"text","name":"name","required":true}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/numerology/business-name","title":"Calculate business name numerology"},"calculateCenters":{"fields":[{"description":"Birth date in YYYY-MM-DD format. The anchor for both the Personality activations at birth and the Design activations 88 degrees of solar arc earlier.","example":"1990-07-15","key":"date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Precision matters: the profile lines and gate boundaries shift with the exact minute of birth.","example":"13:00:00","key":"time","kind":"time","name":"time","required":true},{"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error.","example":"America/New_York","key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":true,"role":"location"},{"default":0,"description":"Birth latitude in decimal degrees. Optional and does not affect the bodygraph, which depends only on ecliptic longitudes. Defaults to 0.","example":0,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":false,"role":"location"},{"default":0,"description":"Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.","example":0,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":false,"role":"location"},{"default":"true","description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node activations. True is what professional Human Design software uses (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against, so leave it unset for a standard chart. It matters only when a node sits on a gate boundary, where the choice moves a node gate. Because a gate can be half of a channel, that can change the completed channels and, with them, whether a center reads defined or open, plus the definition, authority, profile or type. A chart where only one center disagrees is the usual shape, since the type and profile often survive unchanged. If another calculator disagrees on any of those, it is almost certainly using the mean node: pass \"mean\" to match it. Defaults to \"true\".","enum":["mean","true"],"example":"true","fold":true,"key":"nodeType","kind":"tiles","name":"nodeType","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/human-design/centers","title":"Calculate the nine Human Design centers"},"calculateChaldean":{"fields":[{"description":"The name to analyze. Chaldean tradition uses the name a person is most known by, not necessarily the full legal birth name. It needs at least one vowel (A, E, I, O, U) and one consonant, since the Soul Urge is read from the vowels and the Personality from the consonants; Y counts as a consonant. A name in any script is converted to Latin letters before it is counted, Cyrillic and Greek as the passport spelling and accents folded to the base letter, and the calculation lists the letters counted. For a script that does not write its vowels, send the Latin spelling the person uses.","example":"Helen","key":"name","kind":"text","name":"name","required":true}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/numerology/chaldean","title":"Calculate Chaldean numerology"},"calculateChannels":{"fields":[{"description":"Birth date in YYYY-MM-DD format. The anchor for both the Personality activations at birth and the Design activations 88 degrees of solar arc earlier.","example":"1990-07-15","key":"date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Precision matters: the profile lines and gate boundaries shift with the exact minute of birth.","example":"13:00:00","key":"time","kind":"time","name":"time","required":true},{"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error.","example":"America/New_York","key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":true,"role":"location"},{"default":0,"description":"Birth latitude in decimal degrees. Optional and does not affect the bodygraph, which depends only on ecliptic longitudes. Defaults to 0.","example":0,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":false,"role":"location"},{"default":0,"description":"Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.","example":0,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":false,"role":"location"},{"default":"true","description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node activations. True is what professional Human Design software uses (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against, so leave it unset for a standard chart. It matters only when a node sits on a gate boundary, where the choice moves a node gate. Because a gate can be half of a channel, that can change the completed channels and, with them, whether a center reads defined or open, plus the definition, authority, profile or type. A chart where only one center disagrees is the usual shape, since the type and profile often survive unchanged. If another calculator disagrees on any of those, it is almost certainly using the mean node: pass \"mean\" to match it. Defaults to \"true\".","enum":["mean","true"],"example":"true","fold":true,"key":"nodeType","kind":"tiles","name":"nodeType","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/human-design/channels","title":"Calculate the defined Human Design channels"},"calculateCharaKarakas":{"fields":[{"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04","key":"date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00","key":"time","kind":"time","name":"time","required":true},{"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","example":28.6139,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","example":77.209,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"default":5.5,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time. Defaults to 5.5.","example":5.5,"key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"role":"location"},{"default":"lahiri","description":"Sidereal frame (ayanamsa) the chart is cast in. \"lahiri\" is Lahiri/Chitrapaksha, the traditional Vedic standard used by most software, and is the default. \"raman\" is the B.V. Raman ayanamsa from Hindu Predictive Astrology, about 1.45 degrees below Lahiri. \"kp-newcomb\" and \"kp-old\" are the two Krishnamurti Paddhati frames. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"example":"lahiri","fold":true,"key":"ayanamsa","kind":"tiles","name":"ayanamsa","required":false},{"description":"Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.","example":24,"fold":true,"key":"ayanamsaValue","kind":"number","name":"ayanamsaValue","required":false},{"default":"eight","description":"Which Chara Karaka scheme to rank. \"eight\" includes Rahu, counting its degree in reverse because it moves retrograde, and returns eight offices including Pitrikaraka. \"seven\" ranks only the seven classical grahas and drops Pitrikaraka. Ketu is excluded from both, since it always mirrors the Rahu degree exactly. The two schemes can produce a different Atmakaraka for the same chart, so select the one your reference software uses. Defaults to \"eight\".","enum":["seven","eight"],"example":"eight","fold":true,"key":"scheme","kind":"tiles","name":"scheme","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/vedic-astrology/chara-karakas","title":"Get Chara Karakas including Atmakaraka"},"calculateCompatibility":{"fields":[{"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15","group":"person1","key":"person1.date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00","group":"person1","key":"person1.time","kind":"time","name":"time","required":true},{"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","example":40.7128,"group":"person1","key":"person1.latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","example":-74.006,"group":"person1","key":"person1.longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time.","example":"America/New_York","group":"person1","key":"person1.timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":true,"role":"location"},{"default":"true","description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"example":"true","group":"person1","key":"person1.nodeType","kind":"tiles","name":"nodeType","required":false},{"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15","group":"person2","key":"person2.date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00","group":"person2","key":"person2.time","kind":"time","name":"time","required":true},{"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","example":40.7128,"group":"person2","key":"person2.latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","example":-74.006,"group":"person2","key":"person2.longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time.","example":"America/New_York","group":"person2","key":"person2.timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":true,"role":"location"},{"default":"true","description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"example":"true","group":"person2","key":"person2.nodeType","kind":"tiles","name":"nodeType","required":false}],"groups":[{"key":"person1","label":"Person 1","location":{"fields":["person1.latitude","person1.longitude","person1.timezone"],"required":true}},{"key":"person2","label":"Person 2","location":{"fields":["person2.latitude","person2.longitude","person2.timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/astrology/compatibility-score","title":"Compatibility score"},"calculateConnection":{"fields":[{"description":"Birth date in YYYY-MM-DD format. The anchor for both the Personality activations at birth and the Design activations 88 degrees of solar arc earlier.","example":"1990-07-15","group":"personA","key":"personA.date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Precision matters: the profile lines and gate boundaries shift with the exact minute of birth.","example":"13:00:00","group":"personA","key":"personA.time","kind":"time","name":"time","required":true},{"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error.","example":"America/New_York","group":"personA","key":"personA.timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":true,"role":"location"},{"default":0,"description":"Birth latitude in decimal degrees. Optional and does not affect the bodygraph, which depends only on ecliptic longitudes. Defaults to 0.","example":0,"group":"personA","key":"personA.latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":false,"role":"location"},{"default":0,"description":"Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.","example":0,"group":"personA","key":"personA.longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":false,"role":"location"},{"default":"true","description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node activations. True is what professional Human Design software uses (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against, so leave it unset for a standard chart. It matters only when a node sits on a gate boundary, where the choice moves a node gate. Because a gate can be half of a channel, that can change the completed channels and, with them, whether a center reads defined or open, plus the definition, authority, profile or type. A chart where only one center disagrees is the usual shape, since the type and profile often survive unchanged. If another calculator disagrees on any of those, it is almost certainly using the mean node: pass \"mean\" to match it. Defaults to \"true\".","enum":["mean","true"],"example":"true","group":"personA","key":"personA.nodeType","kind":"tiles","name":"nodeType","required":false},{"description":"Birth date in YYYY-MM-DD format. The anchor for both the Personality activations at birth and the Design activations 88 degrees of solar arc earlier.","example":"1990-07-15","group":"personB","key":"personB.date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Precision matters: the profile lines and gate boundaries shift with the exact minute of birth.","example":"13:00:00","group":"personB","key":"personB.time","kind":"time","name":"time","required":true},{"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error.","example":"America/New_York","group":"personB","key":"personB.timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":true,"role":"location"},{"default":0,"description":"Birth latitude in decimal degrees. Optional and does not affect the bodygraph, which depends only on ecliptic longitudes. Defaults to 0.","example":0,"group":"personB","key":"personB.latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":false,"role":"location"},{"default":0,"description":"Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.","example":0,"group":"personB","key":"personB.longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":false,"role":"location"},{"default":"true","description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node activations. True is what professional Human Design software uses (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against, so leave it unset for a standard chart. It matters only when a node sits on a gate boundary, where the choice moves a node gate. Because a gate can be half of a channel, that can change the completed channels and, with them, whether a center reads defined or open, plus the definition, authority, profile or type. A chart where only one center disagrees is the usual shape, since the type and profile often survive unchanged. If another calculator disagrees on any of those, it is almost certainly using the mean node: pass \"mean\" to match it. Defaults to \"true\".","enum":["mean","true"],"example":"true","group":"personB","key":"personB.nodeType","kind":"tiles","name":"nodeType","required":false}],"groups":[{"key":"personA","label":"Person A","location":{"fields":["personA.latitude","personA.longitude","personA.timezone"],"required":true}},{"key":"personB","label":"Person B","location":{"fields":["personB.latitude","personB.longitude","personB.timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/human-design/connection","title":"Calculate Human Design connection chart"},"calculateDashakoot":{"fields":[{"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04","group":"person1","key":"person1.date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00","group":"person1","key":"person1.time","kind":"time","name":"time","required":true},{"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","example":28.6139,"group":"person1","key":"person1.latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","example":77.209,"group":"person1","key":"person1.longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"default":5.5,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time. Defaults to 5.5.","example":5.5,"group":"person1","key":"person1.timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"role":"location"},{"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04","group":"person2","key":"person2.date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00","group":"person2","key":"person2.time","kind":"time","name":"time","required":true},{"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","example":28.6139,"group":"person2","key":"person2.latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","example":77.209,"group":"person2","key":"person2.longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"default":5.5,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time. Defaults to 5.5.","example":5.5,"group":"person2","key":"person2.timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"role":"location"},{"default":"lahiri","description":"Sidereal frame (ayanamsa) the chart is cast in. \"lahiri\" is Lahiri/Chitrapaksha, the traditional Vedic standard used by most software, and is the default. \"raman\" is the B.V. Raman ayanamsa from Hindu Predictive Astrology, about 1.45 degrees below Lahiri. \"kp-newcomb\" and \"kp-old\" are the two Krishnamurti Paddhati frames. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"example":"lahiri","fold":true,"key":"ayanamsa","kind":"tiles","name":"ayanamsa","required":false},{"description":"Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.","example":24,"fold":true,"key":"ayanamsaValue","kind":"number","name":"ayanamsaValue","required":false}],"groups":[{"key":"person1","label":"Person 1","location":{"fields":["person1.latitude","person1.longitude","person1.timezone"],"required":true}},{"key":"person2","label":"Person 2","location":{"fields":["person2.latitude","person2.longitude","person2.timezone"],"required":true}},{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/vedic-astrology/compatibility/dashakoot","title":"Calculate ten porutham match"},"calculateDayMasterStrength":{"fields":[{"description":"Birth date in YYYY-MM-DD format. Sets the year, month and day pillars. The year pillar turns at Beginning of Spring rather than on 1 January, and the month pillar turns at each of the twelve minor solar terms rather than at a calendar month boundary.","example":"1990-06-15","key":"date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Sets the hour pillar, which is one of the four and carries the whole picture of later life and offspring. Each Earthly Branch covers two hours, so a birth within a few minutes of an odd hour can land in either. All four pillars are read in the local clock of the birth, and the day boundary is applied in that same clock; only the lunisolar calendar date itself is a world constant, fixed at UTC plus 8 so one instant has one Chinese date everywhere.","example":"14:30:00","key":"time","kind":"time","name":"time","required":true},{"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error.","example":"America/New_York","key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":true,"role":"location"},{"default":0,"description":"Birth latitude in decimal degrees. Accepted for consistency with the other birth-data endpoints and does not affect any part of a BaZi chart. Defaults to 0.","example":0,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":false,"role":"location"},{"description":"Birth longitude in decimal degrees. Positive is East, negative is West. Required when hourClock is \"local-mean\" or \"solar\", which shift the hour branch to the sun over the birth place; omitting it in either case returns 400. Ignored when hourClock is \"clock\".","example":116.4,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":false,"role":"location"},{"default":"split-zi","description":"Which instant starts the sexagenary DAY, which only matters for a birth between 23:00 and 23:59. \"midnight\" is the classical position of the Ming compendium San Ming Tong Hui: the day turns at 00:00 and 23:00 to 23:59 is the late zi hour of the day that is ending, so the hour stem is taken from that day. \"early-zi\" turns the whole day at 23:00, the practice in Hong Kong, Taiwan and much of South East Asia. \"split-zi\" is the compromise most software implements and the default here: the day still turns at 00:00, but the hour stem is taken from the next day. The three give three different answers for a late-evening birth and identical answers for every other birth.","enum":["split-zi","midnight","early-zi"],"example":"split-zi","fold":true,"key":"dayBoundary","kind":"tiles","name":"dayBoundary","required":false},{"default":"li-chun","description":"Which instant starts the sexagenary YEAR. \"li-chun\" is Beginning of Spring, around 4 February, and is the classical rule every BaZi text uses, so it is the default on this endpoint. \"lunar-new-year\" is the folk rule people mean when they say which animal they are, and it falls between late January and late February. The two disagree for any birth in the weeks between them: 14 February 2026 is a Wood Snake year under lunar-new-year and a Fire Horse year under li-chun.","enum":["li-chun","lunar-new-year"],"example":"li-chun","fold":true,"key":"yearBoundary","kind":"tiles","name":"yearBoundary","required":false},{"default":"clock","description":"Which clock the day boundary and the hour branch are read from, so a correction that carries a birth across midnight moves the day pillar with the hour. \"clock\" is civil time exactly as a birth certificate records it, which is what most calculators use and the default here. \"local-mean\" shifts to the mean sun over the birth longitude, a correction of up to 59 minutes at the edge of a wide time zone. \"solar\" adds the equation of time on top of that, up to a further 16 minutes. Both non-civil options need \"longitude\" in the request and return 400 without it.","enum":["clock","local-mean","solar"],"example":"clock","fold":true,"key":"hourClock","kind":"tiles","name":"hourClock","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/chinese-astrology/bazi/day-master","title":"Calculate Day Master strength"},"calculateDrishti":{"fields":[{"description":"Date in YYYY-MM-DD format. Planetary positions are calculated for this date to determine mutual aspects (drishti).","example":"2026-02-03","key":"date","kind":"date","name":"date","required":true},{"description":"Time in HH:MM:SS format (24-hour). Exact time affects fast-moving planets (Moon, Mercury) and aspect orbs.","example":"12:00:00","key":"time","kind":"time","name":"time","required":true},{"description":"Observer latitude in decimal degrees. Used for Lagna calculation which affects house-based aspect analysis.","example":17.385044,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Observer longitude in decimal degrees. Affects local sidereal time for positional calculations.","example":78.486671,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"default":5.5,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time. Defaults to 5.5 (IST).","example":5.5,"key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"role":"location"},{"default":"sidereal","description":"Coordinate system for longitude output. \"sidereal\" (Nirayana) uses Lahiri ayanamsa, the standard for Vedic astrology. \"tropical\" (Sayana) uses raw ecliptic longitude matching Western astrology. Defaults to \"sidereal\".","enum":["sidereal","tropical"],"example":"sidereal","fold":true,"key":"coordinateSystem","kind":"tiles","name":"coordinateSystem","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":false,"method":"POST","opensOnLoad":false,"path":"/vedic-astrology/aspects","title":"Get planetary aspects (Drishti)"},"calculateDual":{"fields":[{"description":"The name to analyze in both systems. A name in any script is converted to Latin letters before it is counted, Cyrillic and Greek as the passport spelling and accents folded to the base letter, and the calculation lists the letters counted. For a script that does not write its vowels, send the Latin spelling the person uses.","example":"David","key":"name","kind":"text","name":"name","required":true}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/numerology/dual","title":"Calculate dual numerology"},"calculateEntrancePada":{"fields":[{"description":"East-west extent of a rectangular plot, in the unit given. Send this with depth for a rectangle, or send polygon instead.","example":30,"group":"plot","key":"plot.width","kind":"number","min":0,"name":"width","required":true},{"description":"North-south extent of a rectangular plot, in the unit given. Send this with width for a rectangle, or send polygon instead.","example":40,"group":"plot","key":"plot.depth","kind":"number","min":0,"name":"depth","required":true},{"default":"feet","description":"Unit the plot dimensions are given in. Every distance the response returns is in this same unit. The mandala projection is scale free, so this affects the areas and the marma size and nothing else.","enum":["feet","metres"],"example":"feet","group":"plot","key":"plot.unit","kind":"tiles","name":"unit","required":false},{"description":"Direction the front of the house looks out toward, one of the eight compass sectors. Case and punctuation are folded, so north-east, northeast and NorthEast all resolve. Send this or facingDegrees, never both.","enum":["North","Northeast","East","Southeast","South","Southwest","West","Northwest"],"example":"North","key":"facing","kind":"tiles","name":"facing","required":true},{"description":"Direction the front of the house looks out toward, as a compass bearing in degrees clockwise from true north, measured looking OUT from the building. The same convention the feng shui facing endpoints use, so a bearing works unchanged across the two domains. Send this or facing, never both.","example":15,"fold":true,"key":"facingDegrees","kind":"number","max":360,"min":0,"name":"facingDegrees","required":false},{"description":"Distance east of the plot origin, in the same unit as the plot. The x axis runs east.","example":15,"fold":true,"group":"door","key":"door.x","kind":"number","name":"x","required":false},{"description":"Distance north of the plot origin, in the same unit as the plot. The y axis runs north.","example":0,"fold":true,"group":"door","key":"door.y","kind":"number","name":"y","required":false},{"description":"Where the main door sits along the facing side, as a fraction from 0 to 1 measured from the corner the chapter starts that side at: the north-east for an east facing, the south-east for a south facing, the south-west for a west facing and the north-west for a north facing. The side carries 8 padas, so to aim at pada n of 8 send its midpoint, (n - 0.5) / 8: 0.0625 for the first pada, 0.4375 for the fourth, 0.9375 for the eighth. The response names the pada the fraction resolved to in ordinalOnSide. Requires a cardinal facing, since an intercardinal facing names no single side. Send this or door, never both.","example":0.4,"key":"doorPosition","kind":"number","max":1,"min":0,"name":"doorPosition","required":true},{"default":"81-pada","description":"Which division of the ground to read: 81-pada is the Paramasayika of Brihat Samhita 53.42, the grid the chapter numbers and names every devata on, and 64-pada is the Manduka of 53.55, for which the chapter gives structure only and no devata names. Defaults to 81-pada.","enum":["81-pada","64-pada"],"example":"81-pada","fold":true,"key":"grid","kind":"tiles","name":"grid","required":false}],"groups":[{"key":"plot","label":"Plot"},{},{"fold":true,"key":"door","label":"Door"}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/vastu/entrance","requiredAnyOf":[["facing","doorPosition"],["facing","door"],["facingDegrees","doorPosition"],["facingDegrees","door"]],"title":"Calculate entrance pada"},"calculateExpression":{"fields":[{"description":"Full birth name (first, middle, last). A name in any script is converted to Latin letters before it is counted, Cyrillic and Greek as the passport spelling and accents folded to the base letter, and the calculation lists the letters counted. For a script that does not write its vowels, send the Latin spelling the person uses.","example":"John William Smith","key":"fullName","kind":"text","name":"fullName","required":true}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/numerology/expression","title":"Calculate Expression number"},"calculateGates":{"fields":[{"description":"Birth date in YYYY-MM-DD format. The anchor for both the Personality activations at birth and the Design activations 88 degrees of solar arc earlier.","example":"1990-07-15","key":"date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Precision matters: the profile lines and gate boundaries shift with the exact minute of birth.","example":"13:00:00","key":"time","kind":"time","name":"time","required":true},{"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error.","example":"America/New_York","key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":true,"role":"location"},{"default":0,"description":"Birth latitude in decimal degrees. Optional and does not affect the bodygraph, which depends only on ecliptic longitudes. Defaults to 0.","example":0,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":false,"role":"location"},{"default":0,"description":"Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.","example":0,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":false,"role":"location"},{"default":"true","description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node activations. True is what professional Human Design software uses (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against, so leave it unset for a standard chart. It matters only when a node sits on a gate boundary, where the choice moves a node gate. Because a gate can be half of a channel, that can change the completed channels and, with them, whether a center reads defined or open, plus the definition, authority, profile or type. A chart where only one center disagrees is the usual shape, since the type and profile often survive unchanged. If another calculator disagrees on any of those, it is almost certainly using the mean node: pass \"mean\" to match it. Defaults to \"true\".","enum":["mean","true"],"example":"true","fold":true,"key":"nodeType","kind":"tiles","name":"nodeType","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/human-design/gates","title":"Calculate the 26 Human Design gate activations"},"calculateGematria":{"fields":[{"description":"Latin text to write in Hebrew and then score, up to 200 characters. Non Latin scripts are folded to Latin first, so a Cyrillic or Devanagari name works. Send textHebrew instead to control the Hebrew spelling yourself.","example":"Sarah","key":"text","kind":"text","name":"text","required":true},{"description":"Hebrew text to score, up to 200 characters. Anything outside the Hebrew script is rejected. Vowel points, cantillation marks, maqaf and paseq are removed before scoring, so a pointed and an unpointed spelling of one word give the same number.","example":"שלום","fold":true,"key":"textHebrew","kind":"text","name":"textHebrew","required":false},{"default":"letter-map-mathers","description":"How a Latin name is written in Hebrew before it is scored. Two members. letter-map-mathers is the 1887 Hermetic letter map, with e read as its author practised it: a point inside a word and alef at the start of one. It writes no c, f, w or x, so a name carrying one of them outside a two letter group returns 400 naming the letter. letter-map-modern follows the modern Israeli transcription rules for the sound each Latin letter carries in English and French spelling, covers every Latin letter, drops the geresh and does not double vav or yod, so send textHebrew for the ktiv male form. Every form states the readings it used in rule. Phonetic Ashkenazi and Sephardi schemes are not offered because no two references agree on a rule for that direction.","enum":["letter-map-mathers","letter-map-modern"],"example":"letter-map-mathers","fold":true,"key":"transliteration","kind":"tiles","name":"transliteration","required":false},{"description":"Which ciphers to return, by identifier. Omit for every computed cipher. Valid values are mispar-hechrachi, mispar-gadol, otiyot-be-milui, mispar-katan, mispar-kidmi, mispar-prati, mispar-ha-merubah-ha-klali, mispar-meshulash, mispar-musafi, kolel.","example":["mispar-hechrachi","mispar-gadol"],"fold":true,"key":"ciphers","kind":"array","name":"ciphers","required":false},{"default":"finals-500-900","description":"Which method the name mispar gadol means, because the sources use it for two. Use finals-500-900 to score the five word final letters as 500 to 900, or milui to score each letter as the value of its own spelled out name.","enum":["finals-500-900","milui"],"example":"finals-500-900","fold":true,"key":"misparGadol","kind":"tiles","name":"misparGadol","required":false},{"default":"both","description":"What AtBash and Albam return: the substituted Hebrew string, its standard value, or both. The biblical witness for AtBash is a substituted WORD rather than a number, which is why the string is available on its own.","enum":["both","string","value"],"example":"both","fold":true,"key":"atbashOutput","kind":"tiles","name":"atbashOutput","required":false},{"default":true,"description":"Whether to return the curated equal value entries for the chosen spelling. Set false to skip the lookup when only the numbers are wanted.","example":true,"fold":true,"key":"includeMatches","kind":"toggle","name":"includeMatches","required":false},{"default":false,"description":"Whether to also score the Latin text with the three Latin alphabet ciphers. They are Renaissance Christian and modern in lineage rather than rabbinic, and the response labels each one. Ignored when textHebrew was sent.","example":false,"fold":true,"key":"latinCiphers","kind":"toggle","name":"latinCiphers","required":false}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/kabbalah/gematria","requiredAnyOf":[["text"],["textHebrew"]],"title":"Calculate gematria"},"calculateGunMilan":{"fields":[{"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04","group":"person1","key":"person1.date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00","group":"person1","key":"person1.time","kind":"time","name":"time","required":true},{"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","example":28.6139,"group":"person1","key":"person1.latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","example":77.209,"group":"person1","key":"person1.longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"default":5.5,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time. Defaults to 5.5.","example":5.5,"group":"person1","key":"person1.timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"role":"location"},{"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04","group":"person2","key":"person2.date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00","group":"person2","key":"person2.time","kind":"time","name":"time","required":true},{"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","example":28.6139,"group":"person2","key":"person2.latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","example":77.209,"group":"person2","key":"person2.longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"default":5.5,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time. Defaults to 5.5.","example":5.5,"group":"person2","key":"person2.timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"role":"location"},{"default":"lahiri","description":"Sidereal frame (ayanamsa) the chart is cast in. \"lahiri\" is Lahiri/Chitrapaksha, the traditional Vedic standard used by most software, and is the default. \"raman\" is the B.V. Raman ayanamsa from Hindu Predictive Astrology, about 1.45 degrees below Lahiri. \"kp-newcomb\" and \"kp-old\" are the two Krishnamurti Paddhati frames. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"example":"lahiri","fold":true,"key":"ayanamsa","kind":"tiles","name":"ayanamsa","required":false},{"description":"Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.","example":24,"fold":true,"key":"ayanamsaValue","kind":"number","name":"ayanamsaValue","required":false}],"groups":[{"key":"person1","label":"Person 1","location":{"fields":["person1.latitude","person1.longitude","person1.timezone"],"required":true}},{"key":"person2","label":"Person 2","location":{"fields":["person2.latitude","person2.longitude","person2.timezone"],"required":true}},{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/vedic-astrology/compatibility","title":"Calculate compatibility score"},"calculateHouses":{"fields":[{"description":"Birth date in YYYY-MM-DD format. Date is critical for house cusp calculations as it determines planetary positions used in some house systems.","example":"1990-07-15","key":"date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Time is ESSENTIAL for accurate house cusps, and even minutes matter. The Ascendant (1st house cusp) changes roughly every 4 minutes. Without accurate time, house placements will be incorrect.","example":"14:30:00","key":"time","kind":"time","name":"time","required":true},{"description":"Birth location latitude in decimal degrees (-90 to 90). Location determines the local horizon and meridian, which are fundamental to house division. Higher latitudes cause more distortion in time-based systems like Placidus.","example":40.7128,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Birth location longitude in decimal degrees (-180 to 180). Affects local time and horizon calculations for house cusps.","example":-74.006,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"description":"Decimal hours from UTC (e.g. -5 for EST, 5.5 for IST, 9 for JST) OR IANA name (e.g. \"America/New_York\"). IANA resolved to the DST-correct offset for the chart date.","example":"America/New_York","key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":true,"role":"location"},{"default":"placidus","description":"House system for dividing ecliptic into 12 houses. Placidus (most popular) uses time, Whole Sign (ancient) uses signs, Equal divides from Ascendant. Use \"all\" to compare all 4 systems side-by-side for educational purposes.","enum":["placidus","whole-sign","equal","koch"],"example":"placidus","fold":true,"key":"houseSystem","kind":"tiles","name":"houseSystem","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/astrology/houses","title":"Calculate house cusps"},"calculateKuaNumber":{"fields":[{"description":"Birth date in YYYY-MM-DD format. Only the Chinese YEAR this date falls in enters the formula, so no birth time, latitude or longitude is needed. A January or early February birthday is the case that matters: it usually belongs to the PREVIOUS Chinese year and produces a different Kua. A date is read at the start of its day, and the boundary falls part-way through its own day, so a birth date landing exactly on the boundary day is placed in the outgoing year.","example":"1985-07-15","key":"date","kind":"date","name":"date","required":true},{"description":"Selects the Kua formula variant. The two formulas are different arithmetic on the same year, and they also differ in where a raw result of 5 is reassigned.","enum":["male","female"],"example":"male","key":"gender","kind":"tiles","name":"gender","required":true},{"default":"li-chun","description":"Which boundary starts the Chinese year. Defaults to li-chun, the astronomical start of spring in early February, which is the classical position and the one feng shui uses for periods, annual stars and afflictions alike. Send lunar-new-year to match popular zodiac tables, which start the year two to four weeks later. The two disagree for anyone born between the two dates.","enum":["li-chun","lunar-new-year"],"example":"li-chun","fold":true,"key":"yearBoundary","kind":"tiles","name":"yearBoundary","required":false}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/feng-shui/kua","title":"Calculate Kua number"},"calculateLifePath":{"fields":[{"description":"Birth year between 100 and 2100. Supports historical figures like Einstein (1879) and Shakespeare (1564).","example":1990,"key":"year","kind":"number","max":2100,"min":100,"name":"year","required":true},{"description":"Birth month (1-12)","example":7,"key":"month","kind":"number","max":12,"min":1,"name":"month","required":true},{"description":"Birth day (1-31)","example":15,"key":"day","kind":"number","max":31,"min":1,"name":"day","required":true}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/numerology/life-path","title":"Calculate Life Path number"},"calculateLuckPillars":{"fields":[{"description":"Birth date in YYYY-MM-DD format. Sets the year, month and day pillars. The year pillar turns at Beginning of Spring rather than on 1 January, and the month pillar turns at each of the twelve minor solar terms rather than at a calendar month boundary.","example":"1990-06-15","key":"date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Sets the hour pillar, which is one of the four and carries the whole picture of later life and offspring. Each Earthly Branch covers two hours, so a birth within a few minutes of an odd hour can land in either. All four pillars are read in the local clock of the birth, and the day boundary is applied in that same clock; only the lunisolar calendar date itself is a world constant, fixed at UTC plus 8 so one instant has one Chinese date everywhere.","example":"14:30:00","key":"time","kind":"time","name":"time","required":true},{"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error.","example":"America/New_York","key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":true,"role":"location"},{"default":0,"description":"Birth latitude in decimal degrees. Accepted for consistency with the other birth-data endpoints and does not affect any part of a BaZi chart. Defaults to 0.","example":0,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":false,"role":"location"},{"description":"Birth longitude in decimal degrees. Positive is East, negative is West. Required when hourClock is \"local-mean\" or \"solar\", which shift the hour branch to the sun over the birth place; omitting it in either case returns 400. Ignored when hourClock is \"clock\".","example":116.4,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":false,"role":"location"},{"default":"split-zi","description":"Which instant starts the sexagenary DAY, which only matters for a birth between 23:00 and 23:59. \"midnight\" is the classical position of the Ming compendium San Ming Tong Hui: the day turns at 00:00 and 23:00 to 23:59 is the late zi hour of the day that is ending, so the hour stem is taken from that day. \"early-zi\" turns the whole day at 23:00, the practice in Hong Kong, Taiwan and much of South East Asia. \"split-zi\" is the compromise most software implements and the default here: the day still turns at 00:00, but the hour stem is taken from the next day. The three give three different answers for a late-evening birth and identical answers for every other birth.","enum":["split-zi","midnight","early-zi"],"example":"split-zi","fold":true,"key":"dayBoundary","kind":"tiles","name":"dayBoundary","required":false},{"default":"li-chun","description":"Which instant starts the sexagenary YEAR. \"li-chun\" is Beginning of Spring, around 4 February, and is the classical rule every BaZi text uses, so it is the default on this endpoint. \"lunar-new-year\" is the folk rule people mean when they say which animal they are, and it falls between late January and late February. The two disagree for any birth in the weeks between them: 14 February 2026 is a Wood Snake year under lunar-new-year and a Fire Horse year under li-chun.","enum":["li-chun","lunar-new-year"],"example":"li-chun","fold":true,"key":"yearBoundary","kind":"tiles","name":"yearBoundary","required":false},{"default":"clock","description":"Which clock the day boundary and the hour branch are read from, so a correction that carries a birth across midnight moves the day pillar with the hour. \"clock\" is civil time exactly as a birth certificate records it, which is what most calculators use and the default here. \"local-mean\" shifts to the mean sun over the birth longitude, a correction of up to 59 minutes at the edge of a wide time zone. \"solar\" adds the equation of time on top of that, up to a further 16 minutes. Both non-civil options need \"longitude\" in the request and return 400 without it.","enum":["clock","local-mean","solar"],"example":"clock","fold":true,"key":"hourClock","kind":"tiles","name":"hourClock","required":false},{"description":"Subject sex, used only to pick the luck-pillar direction: a male born in a yang-stem year and a female born in a yin-stem year run forward through the sexagenary cycle, and the other two combinations run backward. It affects nothing else in the response.","enum":["male","female"],"example":"male","key":"gender","kind":"tiles","name":"gender","required":true},{"default":8,"description":"How many ten-year luck pillars to return, 1 to 12. Eight covers eighty years from the start age, which reaches past a normal lifetime for most start ages.","example":8,"fold":true,"key":"count","kind":"number","max":12,"min":1,"name":"count","required":false},{"description":"First Gregorian year of the annual pillar overlay. Omit it to leave annualPillars out of the response entirely. The annual pillar is the year the chart is currently walking through, read against the ten-year luck pillar underneath it.","example":2026,"fold":true,"key":"annualFromYear","kind":"number","max":2649,"min":1551,"name":"annualFromYear","required":false},{"default":10,"description":"How many consecutive years the annual overlay covers, 1 to 20. Ignored unless annualFromYear is present.","example":10,"fold":true,"key":"annualYears","kind":"number","max":20,"min":1,"name":"annualYears","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/chinese-astrology/bazi/luck-pillars","title":"Calculate luck pillars"},"calculateLunarDate":{"fields":[{"description":"Gregorian date to convert to the lunisolar calendar. Send this OR the lunar fields, never both. Converts from the first day of lunar year 1551 to the last day of lunar year 2648, a little inside the supported date span, because numbering a lunar month needs the winter solstice on each side of it and placing a leap month needs the year before; a date outside that answers 400 date_out_of_range.","example":"1990-06-15","key":"date","kind":"date","name":"date","required":false},{"description":"Lunisolar year to convert back to a Gregorian date. Requires lunarMonth and lunarDay.","example":1990,"key":"lunarYear","kind":"number","max":2100,"min":1900,"name":"lunarYear","required":false},{"description":"Lunar month, 1 to 12. Requires lunarYear and lunarDay.","example":5,"key":"lunarMonth","kind":"number","max":12,"min":1,"name":"lunarMonth","required":false},{"description":"Day of the lunar month, 1 to 30. Requires lunarYear and lunarMonth.","example":23,"key":"lunarDay","kind":"number","max":30,"min":1,"name":"lunarDay","required":false},{"default":false,"description":"Set true to address the leap repetition of lunarMonth rather than the first pass. Requesting a leap month a year does not have returns 400.","example":false,"fold":true,"key":"isLeapMonth","kind":"toggle","name":"isLeapMonth","required":false}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/chinese-astrology/calendar/lunar-date","title":"Convert lunar and Gregorian dates"},"calculateMaturity":{"fields":[{"description":"Your Life Path number (1-9, 11, 22, 33). Optional if year, month, day are provided.","example":5,"fold":true,"key":"lifePath","kind":"number","max":33,"min":1,"name":"lifePath","required":false},{"description":"Your Expression number (1-9, 11, 22, 33). Optional if fullName is provided.","example":7,"fold":true,"key":"expression","kind":"number","max":33,"min":1,"name":"expression","required":false},{"description":"Full birth name to calculate the Expression number automatically. Use instead of passing expression directly. A name in any script is converted to Latin letters before it is counted, Cyrillic and Greek as the passport spelling and accents folded to the base letter, and the calculation lists the letters counted. For a script that does not write its vowels, send the Latin spelling the person uses.","example":"John William Smith","key":"fullName","kind":"text","name":"fullName","required":true},{"description":"Birth year to calculate Life Path automatically. Use with month and day instead of passing lifePath directly.","example":1990,"key":"year","kind":"number","max":2100,"min":100,"name":"year","required":true},{"description":"Birth month (1-12). Required with year and day for automatic Life Path calculation.","example":7,"key":"month","kind":"number","max":12,"min":1,"name":"month","required":true},{"description":"Birth day (1-31). Required with year and month for automatic Life Path calculation.","example":15,"key":"day","kind":"number","max":31,"min":1,"name":"day","required":true}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/numerology/maturity","requiredAnyOf":[["fullName","year","month","day"],["lifePath","expression"],["lifePath","fullName"],["expression","year","month","day"]],"title":"Calculate Maturity number"},"calculateMayanCompatibility":{"fields":[{"description":"Date in YYYY-MM-DD format, in the PROLEPTIC GREGORIAN calendar, extended backwards unchanged through the 1582 reform. Years 1 to 4000 are accepted. A reference converter that switches to the Julian calendar below the reform will disagree with a date before 15 October 1582 by ten or eleven days; that is a difference of input convention rather than of arithmetic, and passing the Julian equivalent to such a tool reproduces these values exactly. A single-digit month or day is accepted and zero padded.","example":"2012-12-21","group":"personA","key":"personA.date","kind":"date","name":"date","required":true},{"description":"Date in YYYY-MM-DD format, in the PROLEPTIC GREGORIAN calendar, extended backwards unchanged through the 1582 reform. Years 1 to 4000 are accepted. A reference converter that switches to the Julian calendar below the reform will disagree with a date before 15 October 1582 by ten or eleven days; that is a difference of input convention rather than of arithmetic, and passing the Julian equivalent to such a tool reproduces these values exactly. A single-digit month or day is accepted and zero padded.","example":"2012-12-21","group":"personB","key":"personB.date","kind":"date","name":"date","required":true},{"default":"gmt-584283","description":"Which correlation constant ties the day count to a civil date. This is the single choice that shifts every value in the response, so it is a parameter rather than a hidden default, and the resolved value comes back under conventions. \"gmt-584283\" is the commonly accepted constant and the default, and it is the one the major institutional converter runs on. \"martinez-hernandez-584281\" sits two days earlier, \"astronomical-584285\" two days later, and \"martin-skidmore-584286\" three days later, each shifting the Long Count by exactly its difference in days. Four of the eight published constants are offered: the other four sit tens of thousands of days away and are of historical interest only. The 584281 constant is the Martínez Hernández correlation, after Juan Martínez Hernández.","enum":["gmt-584283","martinez-hernandez-584281","astronomical-584285","martin-skidmore-584286"],"example":"gmt-584283","fold":true,"key":"correlation","kind":"tiles","name":"correlation","required":false},{"default":"madrid-codex","description":"Which reading of the world direction and colour to serve for a day sign. The two published assignments differ by exactly one quarter turn on all twenty signs, so neither is a rounding of the other and a silent pick would be a school choice. \"madrid-codex\" is the codex reading and the default; \"landa\" is the sixteenth century assignment recorded beside it.","enum":["madrid-codex","landa"],"example":"madrid-codex","fold":true,"key":"directionScheme","kind":"tiles","name":"directionScheme","required":false}],"groups":[{"key":"personA","label":"Person A"},{"key":"personB","label":"Person B"},{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/mesoamerican-astrology/mayan/compatibility","title":"Mayan nawal compatibility"},"calculateNameCompatibility":{"fields":[{"description":"First name in Latin script. Send firstNameHebrew instead to control the spelling.","example":"Sarah","key":"firstName","kind":"text","name":"firstName","required":true},{"description":"First name already in Hebrew, which skips the transliteration step.","example":"שרה","fold":true,"key":"firstNameHebrew","kind":"text","name":"firstNameHebrew","required":false},{"description":"Second name in Latin script. Send secondNameHebrew instead to control the spelling.","example":"David","key":"secondName","kind":"text","name":"secondName","required":true},{"description":"Second name already in Hebrew, which skips the transliteration step.","example":"דוד","fold":true,"key":"secondNameHebrew","kind":"text","name":"secondNameHebrew","required":false},{"default":"letter-map-mathers","description":"How a Latin name is written in Hebrew before it is scored. Two members. letter-map-mathers is the 1887 Hermetic letter map, with e read as its author practised it: a point inside a word and alef at the start of one. It writes no c, f, w or x, so a name carrying one of them outside a two letter group returns 400 naming the letter. letter-map-modern follows the modern Israeli transcription rules for the sound each Latin letter carries in English and French spelling, covers every Latin letter, drops the geresh and does not double vav or yod, so send textHebrew for the ktiv male form. Every form states the readings it used in rule. Phonetic Ashkenazi and Sephardi schemes are not offered because no two references agree on a rule for that direction.","enum":["letter-map-mathers","letter-map-modern"],"example":"letter-map-mathers","fold":true,"key":"transliteration","kind":"tiles","name":"transliteration","required":false},{"default":"finals-500-900","description":"Which method the name mispar gadol means, because the sources use it for two. Use finals-500-900 to score the five word final letters as 500 to 900, or milui to score each letter as the value of its own spelled out name.","enum":["finals-500-900","milui"],"example":"finals-500-900","fold":true,"key":"misparGadol","kind":"tiles","name":"misparGadol","required":false}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/kabbalah/compatibility","requiredAnyOf":[["firstName","secondName"],["firstName","secondNameHebrew"],["firstNameHebrew","secondName"],["firstNameHebrew","secondNameHebrew"]],"title":"Compare two names"},"calculateNumCompatibility":{"fields":[{"description":"Full birth name to calculate Expression and Soul Urge numbers automatically. Use instead of passing expression and soulUrge directly.","example":"John William Smith","group":"person1","key":"person1.fullName","kind":"text","name":"fullName","required":true},{"description":"Birth year to calculate Life Path automatically. Use with month and day instead of passing lifePath directly.","example":1990,"group":"person1","key":"person1.year","kind":"number","max":2100,"min":100,"name":"year","required":true},{"description":"Birth month (1-12). Required with year and day for automatic Life Path calculation.","example":7,"group":"person1","key":"person1.month","kind":"number","max":12,"min":1,"name":"month","required":true},{"description":"Birth day (1-31). Required with year and month for automatic Life Path calculation.","example":15,"group":"person1","key":"person1.day","kind":"number","max":31,"min":1,"name":"day","required":true},{"description":"Person 1 Life Path number (1-9, 11, 22, 33). Optional if year, month, day are provided.","example":5,"group":"person1","key":"person1.lifePath","kind":"number","max":33,"min":1,"name":"lifePath","required":false},{"description":"Person 1 Expression number (1-9, 11, 22, 33). Optional if fullName is provided.","example":7,"group":"person1","key":"person1.expression","kind":"number","max":33,"min":1,"name":"expression","required":false},{"description":"Person 1 Soul Urge number (1-9, 11, 22, 33). Optional if fullName is provided.","example":6,"group":"person1","key":"person1.soulUrge","kind":"number","max":33,"min":1,"name":"soulUrge","required":false},{"description":"Full birth name to calculate Expression and Soul Urge numbers automatically. Use instead of passing expression and soulUrge directly.","example":"Jane Marie Doe","group":"person2","key":"person2.fullName","kind":"text","name":"fullName","required":true},{"description":"Birth year to calculate Life Path automatically. Use with month and day instead of passing lifePath directly.","example":1992,"group":"person2","key":"person2.year","kind":"number","max":2100,"min":100,"name":"year","required":true},{"description":"Birth month (1-12). Required with year and day for automatic Life Path calculation.","example":3,"group":"person2","key":"person2.month","kind":"number","max":12,"min":1,"name":"month","required":true},{"description":"Birth day (1-31). Required with year and month for automatic Life Path calculation.","example":22,"group":"person2","key":"person2.day","kind":"number","max":31,"min":1,"name":"day","required":true},{"description":"Person 2 Life Path number (1-9, 11, 22, 33). Optional if year, month, day are provided.","example":3,"group":"person2","key":"person2.lifePath","kind":"number","max":33,"min":1,"name":"lifePath","required":false},{"description":"Person 2 Expression number (1-9, 11, 22, 33). Optional if fullName is provided.","example":9,"group":"person2","key":"person2.expression","kind":"number","max":33,"min":1,"name":"expression","required":false},{"description":"Person 2 Soul Urge number (1-9, 11, 22, 33). Optional if fullName is provided.","example":2,"group":"person2","key":"person2.soulUrge","kind":"number","max":33,"min":1,"name":"soulUrge","required":false}],"groups":[{"key":"person1","label":"Person 1"},{"key":"person2","label":"Person 2"}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/numerology/compatibility","title":"Calculate numerology compatibility"},"calculatePapasamyam":{"fields":[{"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04","group":"person1","key":"person1.date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00","group":"person1","key":"person1.time","kind":"time","name":"time","required":true},{"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","example":28.6139,"group":"person1","key":"person1.latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","example":77.209,"group":"person1","key":"person1.longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"default":5.5,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time. Defaults to 5.5.","example":5.5,"group":"person1","key":"person1.timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"role":"location"},{"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04","group":"person2","key":"person2.date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00","group":"person2","key":"person2.time","kind":"time","name":"time","required":true},{"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","example":28.6139,"group":"person2","key":"person2.latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","example":77.209,"group":"person2","key":"person2.longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"default":5.5,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time. Defaults to 5.5.","example":5.5,"group":"person2","key":"person2.timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"role":"location"},{"default":"lahiri","description":"Sidereal frame (ayanamsa) the chart is cast in. \"lahiri\" is Lahiri/Chitrapaksha, the traditional Vedic standard used by most software, and is the default. \"raman\" is the B.V. Raman ayanamsa from Hindu Predictive Astrology, about 1.45 degrees below Lahiri. \"kp-newcomb\" and \"kp-old\" are the two Krishnamurti Paddhati frames. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"example":"lahiri","fold":true,"key":"ayanamsa","kind":"tiles","name":"ayanamsa","required":false},{"description":"Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.","example":24,"fold":true,"key":"ayanamsaValue","kind":"number","name":"ayanamsaValue","required":false}],"groups":[{"key":"person1","label":"Person 1","location":{"fields":["person1.latitude","person1.longitude","person1.timezone"],"required":true}},{"key":"person2","label":"Person 2","location":{"fields":["person2.latitude","person2.longitude","person2.timezone"],"required":true}},{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/vedic-astrology/compatibility/papasamyam","title":"Compare malefic affliction"},"calculateParallels":{"fields":[{"description":"Date in YYYY-MM-DD format. Planetary declinations are calculated for this date to find parallel and contraparallel aspects.","example":"2026-02-03","key":"date","kind":"date","name":"date","required":true},{"description":"Time in HH:MM:SS format (24-hour). Exact time affects declination values, especially for the fast-moving Moon.","example":"12:00:00","key":"time","kind":"time","name":"time","required":true},{"description":"Birth latitude in decimal degrees, part of the birth record. Declinations are geocentric, as every published ephemeris prints them, so it does not move them.","example":17.385044,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Birth longitude in decimal degrees, part of the birth record. Declinations are geocentric, so it does not move them; the instant comes from date, time and timezone.","example":78.486671,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"default":5.5,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time. Defaults to 5.5 (IST).","example":5.5,"key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"role":"location"},{"default":1.5,"description":"Orb in degrees for parallel/contraparallel detection. Defaults to 1.5°.","example":1.5,"fold":true,"key":"orb","kind":"number","max":3,"min":0.5,"name":"orb","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":false,"method":"POST","opensOnLoad":false,"path":"/vedic-astrology/parallels","title":"Declination Parallels"},"calculatePenta":{"fields":[{"description":"Birth date in YYYY-MM-DD format. The anchor for both the Personality activations at birth and the Design activations 88 degrees of solar arc earlier.","example":"1990-07-15","group":"members.0","key":"members.0.date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Precision matters: the profile lines and gate boundaries shift with the exact minute of birth.","example":"13:00:00","group":"members.0","key":"members.0.time","kind":"time","name":"time","required":true},{"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error.","example":"America/New_York","group":"members.0","key":"members.0.timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":true,"role":"location"},{"default":0,"description":"Birth latitude in decimal degrees. Optional and does not affect the bodygraph, which depends only on ecliptic longitudes. Defaults to 0.","example":0,"group":"members.0","key":"members.0.latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":false,"role":"location"},{"default":0,"description":"Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.","example":0,"group":"members.0","key":"members.0.longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":false,"role":"location"},{"default":"true","description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node activations. True is what professional Human Design software uses (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against, so leave it unset for a standard chart. It matters only when a node sits on a gate boundary, where the choice moves a node gate. Because a gate can be half of a channel, that can change the completed channels and, with them, whether a center reads defined or open, plus the definition, authority, profile or type. A chart where only one center disagrees is the usual shape, since the type and profile often survive unchanged. If another calculator disagrees on any of those, it is almost certainly using the mean node: pass \"mean\" to match it. Defaults to \"true\".","enum":["mean","true"],"example":"true","group":"members.0","key":"members.0.nodeType","kind":"tiles","name":"nodeType","required":false},{"description":"Birth date in YYYY-MM-DD format. The anchor for both the Personality activations at birth and the Design activations 88 degrees of solar arc earlier.","example":"1990-07-15","group":"members.1","key":"members.1.date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Precision matters: the profile lines and gate boundaries shift with the exact minute of birth.","example":"13:00:00","group":"members.1","key":"members.1.time","kind":"time","name":"time","required":true},{"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error.","example":"America/New_York","group":"members.1","key":"members.1.timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":true,"role":"location"},{"default":0,"description":"Birth latitude in decimal degrees. Optional and does not affect the bodygraph, which depends only on ecliptic longitudes. Defaults to 0.","example":0,"group":"members.1","key":"members.1.latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":false,"role":"location"},{"default":0,"description":"Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.","example":0,"group":"members.1","key":"members.1.longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":false,"role":"location"},{"default":"true","description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node activations. True is what professional Human Design software uses (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against, so leave it unset for a standard chart. It matters only when a node sits on a gate boundary, where the choice moves a node gate. Because a gate can be half of a channel, that can change the completed channels and, with them, whether a center reads defined or open, plus the definition, authority, profile or type. A chart where only one center disagrees is the usual shape, since the type and profile often survive unchanged. If another calculator disagrees on any of those, it is almost certainly using the mean node: pass \"mean\" to match it. Defaults to \"true\".","enum":["mean","true"],"example":"true","group":"members.1","key":"members.1.nodeType","kind":"tiles","name":"nodeType","required":false},{"description":"Birth date in YYYY-MM-DD format. The anchor for both the Personality activations at birth and the Design activations 88 degrees of solar arc earlier.","example":"1990-07-15","group":"members.2","key":"members.2.date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Precision matters: the profile lines and gate boundaries shift with the exact minute of birth.","example":"13:00:00","group":"members.2","key":"members.2.time","kind":"time","name":"time","required":true},{"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error.","example":"America/New_York","group":"members.2","key":"members.2.timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":true,"role":"location"},{"default":0,"description":"Birth latitude in decimal degrees. Optional and does not affect the bodygraph, which depends only on ecliptic longitudes. Defaults to 0.","example":0,"group":"members.2","key":"members.2.latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":false,"role":"location"},{"default":0,"description":"Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.","example":0,"group":"members.2","key":"members.2.longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":false,"role":"location"},{"default":"true","description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node activations. True is what professional Human Design software uses (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against, so leave it unset for a standard chart. It matters only when a node sits on a gate boundary, where the choice moves a node gate. Because a gate can be half of a channel, that can change the completed channels and, with them, whether a center reads defined or open, plus the definition, authority, profile or type. A chart where only one center disagrees is the usual shape, since the type and profile often survive unchanged. If another calculator disagrees on any of those, it is almost certainly using the mean node: pass \"mean\" to match it. Defaults to \"true\".","enum":["mean","true"],"example":"true","group":"members.2","key":"members.2.nodeType","kind":"tiles","name":"nodeType","required":false}],"groups":[{"key":"members.0","label":"Group members 1","location":{"fields":["members.0.latitude","members.0.longitude","members.0.timezone"],"required":true}},{"key":"members.1","label":"Group members 2","location":{"fields":["members.1.latitude","members.1.longitude","members.1.timezone"],"required":true}},{"key":"members.2","label":"Group members 3","location":{"fields":["members.2.latitude","members.2.longitude","members.2.timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/human-design/penta","repeats":[{"key":"members","max":5,"min":3}],"title":"Calculate Human Design Penta"},"calculatePersonalDay":{"fields":[{"description":"Birth month (1-12)","example":7,"key":"month","kind":"number","max":12,"min":1,"name":"month","required":true},{"description":"Birth day (1-31)","example":18,"key":"day","kind":"number","max":31,"min":1,"name":"day","required":true},{"description":"Target date in YYYY-MM-DD format, in the years 100 to 2100. Defaults to today (UTC).","example":"2026-04-04","fold":true,"key":"targetDate","kind":"date","name":"targetDate","required":false}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/numerology/personal-day","title":"Calculate Personal Day"},"calculatePersonalMonth":{"fields":[{"description":"Birth month (1-12)","example":7,"key":"month","kind":"number","max":12,"min":1,"name":"month","required":true},{"description":"Birth day (1-31)","example":18,"key":"day","kind":"number","max":31,"min":1,"name":"day","required":true},{"description":"Target year. Defaults to the current UTC year.","example":2026,"fold":true,"key":"year","kind":"number","max":2100,"min":100,"name":"year","required":false},{"description":"Target calendar month to forecast (1 to 12). Defaults to the current UTC month.","example":4,"fold":true,"key":"targetMonth","kind":"number","max":12,"min":1,"name":"targetMonth","required":false}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/numerology/personal-month","title":"Calculate Personal Month"},"calculatePersonalYear":{"fields":[{"description":"Birth month (1-12)","example":7,"key":"month","kind":"number","max":12,"min":1,"name":"month","required":true},{"description":"Birth day (1-31)","example":15,"key":"day","kind":"number","max":31,"min":1,"name":"day","required":true},{"description":"Year to forecast. Defaults to the current UTC year; the Personal Year turns over on 1 January.","example":2025,"fold":true,"key":"year","kind":"number","max":2100,"min":100,"name":"year","required":false}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/numerology/personal-year","title":"Calculate Personal Year"},"calculatePersonality":{"fields":[{"description":"Full birth name. Its consonants give the Personality number, so a name with none is refused. A name in any script is converted to Latin letters before it is counted, Cyrillic and Greek as the passport spelling and accents folded to the base letter, and the calculation lists the letters counted. For a script that does not write its vowels, send the Latin spelling the person uses.","example":"John William Smith","key":"fullName","kind":"text","name":"fullName","required":true}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/numerology/personality","title":"Calculate Personality number"},"calculatePlotAnalysis":{"fields":[{"description":"East-west extent of a rectangular plot, in the unit given. Send this with depth for a rectangle, or send polygon instead.","example":30,"group":"plot","key":"plot.width","kind":"number","min":0,"name":"width","required":true},{"description":"North-south extent of a rectangular plot, in the unit given. Send this with width for a rectangle, or send polygon instead.","example":40,"group":"plot","key":"plot.depth","kind":"number","min":0,"name":"depth","required":true},{"default":"feet","description":"Unit the plot dimensions are given in. Every distance the response returns is in this same unit. The mandala projection is scale free, so this affects the areas and the marma size and nothing else.","enum":["feet","metres"],"example":"feet","group":"plot","key":"plot.unit","kind":"tiles","name":"unit","required":false},{"description":"Direction the front of the house looks out toward, one of the eight compass sectors. Case and punctuation are folded, so north-east, northeast and NorthEast all resolve. Send this or facingDegrees, never both.","enum":["North","Northeast","East","Southeast","South","Southwest","West","Northwest"],"example":"North","key":"facing","kind":"tiles","name":"facing","required":true},{"description":"Direction the front of the house looks out toward, as a compass bearing in degrees clockwise from true north, measured looking OUT from the building. The same convention the feng shui facing endpoints use, so a bearing works unchanged across the two domains. Send this or facing, never both.","example":15,"fold":true,"key":"facingDegrees","kind":"number","max":360,"min":0,"name":"facingDegrees","required":false},{"description":"Which quarter of the plot the ground falls toward, that is where the LOW point is. The chapter states its rules in terms of the side that stands HIGHER, so the opposite of this value is what the verses are read against, and both are returned. Omit it if the ground is level.","enum":["North","Northeast","East","Southeast","South","Southwest","West","Northwest"],"example":"Northeast","fold":true,"key":"slopeLowDirection","kind":"tiles","name":"slopeLowDirection","required":false},{"description":"Which side a road runs along. The verdict is convention: the chapter states no rule for the side a road is on, only that an obstruction facing the gate brings misery unless it lies beyond twice the height of the house.","enum":["North","Northeast","East","Southeast","South","Southwest","West","Northwest"],"example":"North","fold":true,"key":"road","kind":"tiles","name":"road","required":false},{"description":"Quarters where the plot bulges out beyond a rectangle. Every extension verdict is convention: the chapter states no rule for a named corner and the nearest verses speak of a figure with a limb wanting.","example":["Northeast"],"fold":true,"key":"extensions","kind":"array","name":"extensions","required":false},{"description":"Quarters where a corner is missing from the rectangle. Every cut verdict is convention, for the same reason as the extensions.","example":["Southwest"],"fold":true,"key":"cuts","kind":"array","name":"cuts","required":false},{"description":"Which quarter holds standing water, a well, a tank or a sump. This one IS sourced: 53.119 gives a distinct effect for each of the eight directions and calls only the north and the north-east favourable.","enum":["North","Northeast","East","Southeast","South","Southwest","West","Northwest"],"example":"Northeast","fold":true,"key":"water","kind":"tiles","name":"water","required":false},{"default":"brihat-samhita","description":"Which reading of the ground level to lead with. brihat-samhita applies verses 115 to 117 as written, where a higher north-east is a loss, a higher east or north is permitted when level ground is unavoidable and still carries its stated cost, and a higher south or west carries its cost with no allowance. modern applies the widely taught rule that the north-east must be the lowest point, which agrees with verse 115 and contradicts the verse 116 allowance. Both readings are returned whichever you choose, so the disagreement is visible rather than hidden. Defaults to brihat-samhita.","enum":["brihat-samhita","modern"],"example":"brihat-samhita","fold":true,"key":"slopeSchool","kind":"tiles","name":"slopeSchool","required":false}],"groups":[{"key":"plot","label":"Plot"},{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/vastu/plot","requiredAnyOf":[["facing"],["facingDegrees"]],"title":"Analyse a plot"},"calculateProfile":{"fields":[{"description":"Birth date in YYYY-MM-DD format. The anchor for both the Personality activations at birth and the Design activations 88 degrees of solar arc earlier.","example":"1990-07-15","key":"date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Precision matters: the profile lines and gate boundaries shift with the exact minute of birth.","example":"13:00:00","key":"time","kind":"time","name":"time","required":true},{"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error.","example":"America/New_York","key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":true,"role":"location"},{"default":0,"description":"Birth latitude in decimal degrees. Optional and does not affect the bodygraph, which depends only on ecliptic longitudes. Defaults to 0.","example":0,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":false,"role":"location"},{"default":0,"description":"Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.","example":0,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":false,"role":"location"},{"default":"true","description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node activations. True is what professional Human Design software uses (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against, so leave it unset for a standard chart. It matters only when a node sits on a gate boundary, where the choice moves a node gate. Because a gate can be half of a channel, that can change the completed channels and, with them, whether a center reads defined or open, plus the definition, authority, profile or type. A chart where only one center disagrees is the usual shape, since the type and profile often survive unchanged. If another calculator disagrees on any of those, it is almost certainly using the mean node: pass \"mean\" to match it. Defaults to \"true\".","enum":["mean","true"],"example":"true","fold":true,"key":"nodeType","kind":"tiles","name":"nodeType","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/human-design/profile","title":"Calculate the Human Design profile and line keynotes"},"calculateRoomCompliance":{"fields":[{"description":"East-west extent of a rectangular plot, in the unit given. Send this with depth for a rectangle, or send polygon instead.","example":30,"group":"plot","key":"plot.width","kind":"number","min":0,"name":"width","required":true},{"description":"North-south extent of a rectangular plot, in the unit given. Send this with width for a rectangle, or send polygon instead.","example":40,"group":"plot","key":"plot.depth","kind":"number","min":0,"name":"depth","required":true},{"default":"feet","description":"Unit the plot dimensions are given in. Every distance the response returns is in this same unit. The mandala projection is scale free, so this affects the areas and the marma size and nothing else.","enum":["feet","metres"],"example":"feet","group":"plot","key":"plot.unit","kind":"tiles","name":"unit","required":false},{"description":"Direction the front of the house looks out toward, one of the eight compass sectors. Case and punctuation are folded, so north-east, northeast and NorthEast all resolve. Send this or facingDegrees, never both.","enum":["North","Northeast","East","Southeast","South","Southwest","West","Northwest"],"example":"North","key":"facing","kind":"tiles","name":"facing","required":true},{"description":"Direction the front of the house looks out toward, as a compass bearing in degrees clockwise from true north, measured looking OUT from the building. The same convention the feng shui facing endpoints use, so a bearing works unchanged across the two domains. Send this or facing, never both.","example":15,"fold":true,"key":"facingDegrees","kind":"number","max":360,"min":0,"name":"facingDegrees","required":false},{"description":"What the room is, one of puja, kitchen, master-bedroom, bedroom, living, dining, study, toilet, store, staircase, water-storage, entrance. Case and punctuation are folded, so Master Bedroom and master_bedroom both resolve. Four of the twelve carry a verse and the rest carry convention, and the response says which.","enum":["puja","kitchen","master-bedroom","bedroom","living","dining","study","toilet","store","staircase","water-storage","entrance"],"example":"kitchen","group":"rooms.0","key":"rooms.0.type","kind":"tiles","name":"type","required":true},{"description":"Which quarter of the plot the room sits in, if you already know it. Send this or polygon, never both.","enum":["North","Northeast","East","Southeast","South","Southwest","West","Northwest"],"example":"Southeast","group":"rooms.0","key":"rooms.0.direction","kind":"tiles","name":"direction","required":true},{"description":"The room outline in plot coordinates, 3 to 16 vertices. The quarter is read from the area centroid against thirds of the plot, so an L-shaped room lands where its mass is rather than where its corners are. Send this or direction, never both.","example":[{"x":20,"y":2},{"x":28,"y":2},{"x":28,"y":12},{"x":20,"y":12}],"group":"rooms.0","key":"rooms.0.polygon","kind":"array","name":"polygon","required":false}],"groups":[{"key":"plot","label":"Plot"},{},{"key":"rooms.0","label":"Rooms 1"}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/vastu/rooms","repeats":[{"key":"rooms","max":24,"min":1}],"requiredAnyOf":[["facing"],["facingDegrees"]],"title":"Check room placement"},"calculateShadbala":{"fields":[{"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04","key":"date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00","key":"time","kind":"time","name":"time","required":true},{"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","example":28.6139,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","example":77.209,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"default":5.5,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time. Defaults to 5.5.","example":5.5,"key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"role":"location"},{"default":"lahiri","description":"Sidereal frame (ayanamsa) the chart is cast in. \"lahiri\" is Lahiri/Chitrapaksha, the traditional Vedic standard used by most software, and is the default. \"raman\" is the B.V. Raman ayanamsa from Hindu Predictive Astrology, about 1.45 degrees below Lahiri. \"kp-newcomb\" and \"kp-old\" are the two Krishnamurti Paddhati frames. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"example":"lahiri","fold":true,"key":"ayanamsa","kind":"tiles","name":"ayanamsa","required":false},{"description":"Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.","example":24,"fold":true,"key":"ayanamsaValue","kind":"number","name":"ayanamsaValue","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/vedic-astrology/shadbala","title":"Get Shadbala (six-fold planetary strength) analysis"},"calculateSoulUrge":{"fields":[{"description":"Full birth name. Its vowels A, E, I, O and U give the Soul Urge, so a name with none is refused. A name in any script is converted to Latin letters before it is counted, Cyrillic and Greek as the passport spelling and accents folded to the base letter, and the calculation lists the letters counted. For a script that does not write its vowels, send the Latin spelling the person uses.","example":"John William Smith","key":"fullName","kind":"text","name":"fullName","required":true}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/numerology/soul-urge","title":"Calculate Soul Urge number"},"calculateSynastry":{"fields":[{"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15","group":"person1","key":"person1.date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00","group":"person1","key":"person1.time","kind":"time","name":"time","required":true},{"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","example":40.7128,"group":"person1","key":"person1.latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","example":-74.006,"group":"person1","key":"person1.longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time.","example":"America/New_York","group":"person1","key":"person1.timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":true,"role":"location"},{"default":"true","description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"example":"true","group":"person1","key":"person1.nodeType","kind":"tiles","name":"nodeType","required":false},{"description":"Optional display name for this person. Included in the response for easy identification.","example":"Alex","group":"person1","key":"person1.name","kind":"text","name":"name","required":false},{"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15","group":"person2","key":"person2.date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00","group":"person2","key":"person2.time","kind":"time","name":"time","required":true},{"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","example":40.7128,"group":"person2","key":"person2.latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","example":-74.006,"group":"person2","key":"person2.longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time.","example":"America/New_York","group":"person2","key":"person2.timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":true,"role":"location"},{"default":"true","description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"example":"true","group":"person2","key":"person2.nodeType","kind":"tiles","name":"nodeType","required":false},{"description":"Optional display name for this person. Included in the response for easy identification.","example":"Alex","group":"person2","key":"person2.name","kind":"text","name":"name","required":false},{"default":"placidus","description":"House system for both natal charts. Placidus (default), Whole Sign, Equal, or Koch.","enum":["placidus","whole-sign","equal","koch"],"example":"placidus","fold":true,"key":"houseSystem","kind":"tiles","name":"houseSystem","required":false}],"groups":[{"key":"person1","label":"Person 1","location":{"fields":["person1.latitude","person1.longitude","person1.timezone"],"required":true}},{"key":"person2","label":"Person 2","location":{"fields":["person2.latitude","person2.longitude","person2.timezone"],"required":true}},{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/astrology/synastry","title":"Calculate synastry"},"calculateTonalpohualli":{"fields":[{"description":"Date in YYYY-MM-DD format, in the PROLEPTIC GREGORIAN calendar, extended backwards unchanged through the 1582 reform. Years 1 to 4000 are accepted. A reference converter that switches to the Julian calendar below the reform will disagree with a date before 15 October 1582 by ten or eleven days; that is a difference of input convention rather than of arithmetic, and passing the Julian equivalent to such a tool reproduces these values exactly. A single-digit month or day is accepted and zero padded.","example":"2012-12-21","key":"date","kind":"date","name":"date","required":true}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/mesoamerican-astrology/aztec/tonalpohualli","title":"Aztec day sign for a date"},"calculateTransit":{"fields":[{"description":"Birth date in YYYY-MM-DD format. Used to calculate the natal chart against which transits are analyzed.","example":"1990-07-04","key":"birthDate","kind":"date","name":"birthDate","required":true},{"description":"Birth time in HH:MM:SS format (24-hour). Critical for accurate natal Lagna and Placidus house cusps which determine transit house placements.","example":"10:12:00","key":"birthTime","kind":"time","name":"birthTime","required":true},{"description":"Transit date to analyze in YYYY-MM-DD format. Planetary positions on this date are overlaid on the natal chart.","example":"2026-02-03","key":"transitDate","kind":"date","name":"transitDate","required":true},{"description":"Transit time in HH:MM:SS format (24-hour). Affects fast-moving planets like Moon. Defaults to noon.","example":"12:00:00","fold":true,"key":"transitTime","kind":"time","name":"transitTime","required":false},{"description":"Observer latitude in decimal degrees. Determines Placidus house cusps for natal chart house assignments.","example":17.385044,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Observer longitude in decimal degrees. Affects local sidereal time for Lagna and house calculations.","example":78.486671,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"default":5.5,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time. Defaults to 5.5 (IST).","example":5.5,"key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"role":"location"},{"default":"sidereal","description":"Coordinate system for longitude output. \"sidereal\" (Nirayana) uses Lahiri ayanamsa, the standard for Vedic astrology. \"tropical\" (Sayana) uses raw ecliptic longitude matching Western astrology. Defaults to \"sidereal\".","enum":["sidereal","tropical"],"example":"sidereal","fold":true,"key":"coordinateSystem","kind":"tiles","name":"coordinateSystem","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":false,"method":"POST","opensOnLoad":false,"path":"/vedic-astrology/transit","title":"Transit Analysis"},"calculateTransitAspects":{"fields":[{"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15","group":"natalChart","key":"natalChart.date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00","group":"natalChart","key":"natalChart.time","kind":"time","name":"time","required":true},{"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","example":40.7128,"group":"natalChart","key":"natalChart.latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","example":-74.006,"group":"natalChart","key":"natalChart.longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time.","example":"America/New_York","group":"natalChart","key":"natalChart.timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":true,"role":"location"},{"default":"true","description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"example":"true","group":"natalChart","key":"natalChart.nodeType","kind":"tiles","name":"nodeType","required":false},{"description":"Transit date in YYYY-MM-DD format. Defaults to current date if omitted. Use future dates for predictive transit analysis.","example":"2026-02-03","key":"transitDate","kind":"date","moment":true,"name":"transitDate","required":false},{"description":"Transit time in HH:MM:SS format, read on the clock of the natal chart timezone at the transit date (an IANA zone takes the offset in force on that date, daylight saving included). Defaults to 12:00:00 (noon) if omitted.","example":"12:00:00","key":"transitTime","kind":"time","moment":true,"name":"transitTime","required":false},{"description":"Filter to specific transiting planets. Omit to include all planets. Useful for focusing on slow-moving outer planet transits (Saturn, Jupiter, Pluto).","example":["Jupiter","Saturn","Pluto"],"fold":true,"key":"planets","kind":"array","name":"planets","required":false},{"description":"Filter to specific aspect types (conjunction, opposition, trine, square, sextile, etc.). Omit to include all aspect types.","example":["CONJUNCTION","OPPOSITION","TRINE","SQUARE"],"fold":true,"key":"aspectTypes","kind":"array","name":"aspectTypes","required":false},{"description":"Minimum aspect strength threshold (0-100). Higher values return only tighter, more potent aspects. Useful for filtering out wide-orb aspects.","example":50,"fold":true,"key":"minStrength","kind":"number","max":100,"min":0,"name":"minStrength","required":false},{"default":"placidus","description":"House system used to divide the natal chart into 12 houses. Every house number in the response is read against these natal cusps, for the natal bodies and the transiting bodies alike. Placidus (default) is time sensitive and the most widely used in Western astrology. Whole Sign assigns one sign per house. Equal divides into 30 degree segments from the Ascendant. Koch emphasizes higher latitudes. Quadrant systems fall back to Whole Sign above the polar circle.","enum":["placidus","whole-sign","equal","koch"],"example":"placidus","fold":true,"key":"houseSystem","kind":"tiles","name":"houseSystem","required":false}],"groups":[{"key":"natalChart","label":"Natal Chart","location":{"fields":["natalChart.latitude","natalChart.longitude","natalChart.timezone"],"required":true}},{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/astrology/transit-aspects","title":"Transit Aspects"},"calculateTransits":{"fields":[{"description":"Transit date in YYYY-MM-DD format (defaults to current date)","example":"2025-12-19","key":"date","kind":"date","label":"Transit date","moment":true,"name":"date","required":false},{"description":"Transit time in HH:MM:SS format (defaults to current time)","example":"12:00:00","key":"time","kind":"time","label":"Transit time","moment":true,"name":"time","required":false},{"city":true,"default":0,"description":"Transit timezone: decimal hours from UTC OR IANA name (e.g. \"America/New_York\"). IANA resolved to the DST-correct offset for the transit date. When `date` or `time` is omitted, the current moment is read in this zone, so `transitDate` and `transitTime` come back as its local clock. Defaults to 0 (UTC).","example":0,"fold":true,"key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"viewerZone":true},{"default":"true","description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"example":"true","fold":true,"key":"nodeType","kind":"tiles","name":"nodeType","required":false},{"description":"Date in YYYY-MM-DD format. A single-digit month or day is accepted and zero-padded (2026-3-5 becomes 2026-03-05). Impossible calendar dates are rejected. Calculations that read planetary positions support 1550-01-02 to 2650-01-22; outside that span they answer 400 with code date_out_of_range, and a calculation that reads a window around the date (a sunrise search, a run of days) may answer the same 400 for a date within a few days of either end.","example":"1990-07-15","group":"natalChart","key":"natalChart.date","kind":"date","name":"date","required":false},{"description":"Time in 24-hour format. Seconds are optional and default to 00 (14:30 becomes 14:30:00); a single-digit hour is zero-padded. Out-of-range values are rejected.","example":"14:30:00","group":"natalChart","key":"natalChart.time","kind":"time","name":"time","required":false},{"description":"Natal birth latitude in decimal degrees, positive north. Sets the local sidereal time behind the natal Ascendant and house cusps that the transits are measured against.","example":40.7128,"group":"natalChart","key":"natalChart.latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":false,"role":"location"},{"description":"Natal birth longitude in decimal degrees, positive east and negative west. Example: New York -74.0060, London -0.1276, Sydney 151.2093.","example":-74.006,"group":"natalChart","key":"natalChart.longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":false,"role":"location"},{"description":"Natal timezone: decimal hours OR IANA name (e.g. \"America/New_York\"). IANA resolved to the DST-correct offset for the natal date.","example":"America/New_York","group":"natalChart","key":"natalChart.timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"role":"location"}],"groups":[{},{"key":"natalChart","label":"Natal Chart","location":{"fields":["natalChart.latitude","natalChart.longitude","natalChart.timezone"],"required":false}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/astrology/transits","title":"Calculate planetary transits"},"calculateType":{"fields":[{"description":"Birth date in YYYY-MM-DD format. The anchor for both the Personality activations at birth and the Design activations 88 degrees of solar arc earlier.","example":"1990-07-15","key":"date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Precision matters: the profile lines and gate boundaries shift with the exact minute of birth.","example":"13:00:00","key":"time","kind":"time","name":"time","required":true},{"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error.","example":"America/New_York","key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":true,"role":"location"},{"default":0,"description":"Birth latitude in decimal degrees. Optional and does not affect the bodygraph, which depends only on ecliptic longitudes. Defaults to 0.","example":0,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":false,"role":"location"},{"default":0,"description":"Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.","example":0,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":false,"role":"location"},{"default":"true","description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node activations. True is what professional Human Design software uses (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against, so leave it unset for a standard chart. It matters only when a node sits on a gate boundary, where the choice moves a node gate. Because a gate can be half of a channel, that can change the completed channels and, with them, whether a center reads defined or open, plus the definition, authority, profile or type. A chart where only one center disagrees is the usual shape, since the type and profile often survive unchanged. If another calculator disagrees on any of those, it is almost certainly using the mean node: pass \"mean\" to match it. Defaults to \"true\".","enum":["mean","true"],"example":"true","fold":true,"key":"nodeType","kind":"tiles","name":"nodeType","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/human-design/type","title":"Calculate Human Design type, authority and profile"},"calculateTzolkin":{"fields":[{"description":"Date in YYYY-MM-DD format, in the PROLEPTIC GREGORIAN calendar, extended backwards unchanged through the 1582 reform. Years 1 to 4000 are accepted. A reference converter that switches to the Julian calendar below the reform will disagree with a date before 15 October 1582 by ten or eleven days; that is a difference of input convention rather than of arithmetic, and passing the Julian equivalent to such a tool reproduces these values exactly. A single-digit month or day is accepted and zero padded.","example":"2012-12-21","key":"date","kind":"date","name":"date","required":true},{"default":"gmt-584283","description":"Which correlation constant ties the day count to a civil date. This is the single choice that shifts every value in the response, so it is a parameter rather than a hidden default, and the resolved value comes back under conventions. \"gmt-584283\" is the commonly accepted constant and the default, and it is the one the major institutional converter runs on. \"martinez-hernandez-584281\" sits two days earlier, \"astronomical-584285\" two days later, and \"martin-skidmore-584286\" three days later, each shifting the Long Count by exactly its difference in days. Four of the eight published constants are offered: the other four sit tens of thousands of days away and are of historical interest only. The 584281 constant is the Martínez Hernández correlation, after Juan Martínez Hernández.","enum":["gmt-584283","martinez-hernandez-584281","astronomical-584285","martin-skidmore-584286"],"example":"gmt-584283","fold":true,"key":"correlation","kind":"tiles","name":"correlation","required":false}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/mesoamerican-astrology/mayan/tzolkin","title":"Mayan day sign for a date"},"calculateVariables":{"fields":[{"description":"Birth date in YYYY-MM-DD format. The anchor for both the Personality activations at birth and the Design activations 88 degrees of solar arc earlier.","example":"1990-07-15","key":"date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Precision matters: the profile lines and gate boundaries shift with the exact minute of birth.","example":"13:00:00","key":"time","kind":"time","name":"time","required":true},{"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error.","example":"America/New_York","key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":true,"role":"location"},{"default":0,"description":"Birth latitude in decimal degrees. Optional and does not affect the bodygraph, which depends only on ecliptic longitudes. Defaults to 0.","example":0,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":false,"role":"location"},{"default":0,"description":"Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.","example":0,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":false,"role":"location"},{"default":"true","description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node activations. True is what professional Human Design software uses (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against, so leave it unset for a standard chart. It matters only when a node sits on a gate boundary, where the choice moves a node gate. Because a gate can be half of a channel, that can change the completed channels and, with them, whether a center reads defined or open, plus the definition, authority, profile or type. A chart where only one center disagrees is the usual shape, since the type and profile often survive unchanged. If another calculator disagrees on any of those, it is almost certainly using the mean node: pass \"mean\" to match it. Defaults to \"true\".","enum":["mean","true"],"example":"true","fold":true,"key":"nodeType","kind":"tiles","name":"nodeType","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/human-design/variables","title":"Calculate Human Design Variables"},"calculateZodiacAnimal":{"fields":[{"description":"Birth date in YYYY-MM-DD format. Only the date is needed: the zodiac animal is a property of the year, so no time, timezone or place changes the answer.","example":"1990-06-15","key":"date","kind":"date","name":"date","required":true},{"default":"lunar-new-year","description":"Which instant starts the zodiac year. lunar-new-year is the folk rule and the default on this route, because it is the rule people mean when they say what animal they are: the sign turns on Chinese New Year, between late January and late February. li-chun is the classical rule every Four Pillars text uses, turning the year at the solar term Beginning of Spring around 4 February. The two agree for roughly eleven months of every year and disagree for the weeks between them, so a 14 February 2026 birth is a Snake under lunar-new-year and a Horse under li-chun. The BaZi routes default to li-chun instead, because a chart and a folk sign are answering different questions.","enum":["lunar-new-year","li-chun"],"example":"lunar-new-year","fold":true,"key":"yearBoundary","kind":"tiles","name":"yearBoundary","required":false}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/chinese-astrology/zodiac/sign","title":"Find the Chinese zodiac animal for a birth date"},"castCareerSpread":{"fields":[{"description":"Optional querent question to focus the career spread. It is echoed back on the reading and gives the seven career positions their context. Omit for general work and vocation guidance.","example":"What do I need to know about my career path?","key":"question","kind":"text","name":"question","required":false},{"description":"Optional seed for reproducible results. The same seed always draws the same seven cards into the same career positions, which is what lets a reading be shared or re-rendered. Omit for a random draw.","example":"reading-2f9c1a","key":"seed","kind":"text","name":"seed","required":false,"role":"seed"}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/tarot/spreads/career","title":"Career spread, 7 cards"},"castCelticCross":{"fields":[{"description":"Optional querent question to focus the Celtic Cross. It is echoed back on the reading and gives the ten positions their context. Omit for a general reading of the situation.","example":"What should I know about this situation?","key":"question","kind":"text","name":"question","required":false},{"description":"Optional seed for reproducible results. The same seed always draws the same ten cards into the same Celtic Cross positions, which is what lets a reading be shared or re-rendered. Omit for a random draw.","example":"reading-2f9c1a","key":"seed","kind":"text","name":"seed","required":false,"role":"seed"}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/tarot/spreads/celtic-cross","title":"Celtic Cross spread, 10 cards"},"castCustomSpread":{"fields":[{"description":"Optional name for your custom tarot spread layout. Used as the spread identifier in the response.","example":"My Custom Spread","fold":true,"key":"spreadName","kind":"text","name":"spreadName","required":false},{"description":"Name for this position in the spread (e.g. Core Issue, Hidden Factor, Best Action). Defines what aspect of the reading this card represents.","example":"Core Issue","group":"positions.0","key":"positions.0.name","kind":"text","name":"name","required":true},{"description":"Description of what this position reveals in the reading. Guides the tarot interpretation for the card drawn in this slot.","example":"What is really going on","group":"positions.0","key":"positions.0.interpretation","kind":"text","name":"interpretation","required":true},{"description":"Optional querent question to focus the custom tarot reading. Provides context for position-specific interpretations.","example":"How do I move forward with this project?","fold":true,"key":"question","kind":"text","name":"question","required":false},{"description":"Optional seed for reproducible results. Same seed with the same positions produces identical card draws for consistent divination.","example":"reading-2f9c1a","key":"seed","kind":"text","name":"seed","required":false,"role":"seed"}],"groups":[{},{"key":"positions.0","label":"Spread positions 1"}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/tarot/spreads/custom","repeats":[{"key":"positions","max":10,"min":1}],"title":"Custom spread builder"},"castDailyReading":{"fields":[{"description":"Optional seed for reproducible readings. Same seed + same date = same hexagram every time. Pass any unique identifier (userId, email hash, session token) to give each user their own hexagram for the day. Without a seed every caller receives the same shared hexagram of the day.","example":"user123","key":"seed","kind":"text","name":"seed","required":false,"role":"seed"},{"description":"Date for the reading in YYYY-MM-DD format. Defaults to today (UTC). Useful for viewing past daily readings or pre-generating future ones.","example":"2026-03-06","key":"date","kind":"date","name":"date","required":false}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/iching/daily/cast","title":"Cast daily reading with changing lines"},"castKpHoraryChart":{"fields":[{"description":"Horary number from 1 to 249, given by the querent while focused on their question. It maps to one of the 249 KP sub divisions of the zodiac, and that division sets the Ascendant of the chart. The querent should give the first number that comes to mind and use it once for that question; the astrologer never chooses it. Numbers outside 1 to 249 are rejected rather than wrapped, because a wrapped number would silently answer a different question.","example":108,"key":"horaryNumber","kind":"number","max":249,"min":1,"name":"horaryNumber","required":true},{"description":"Date the question was taken up for judgment, YYYY-MM-DD. Not a birth date: a horary chart needs no birth details at all, which is the point of the method.","example":"2026-03-08","key":"date","kind":"date","name":"date","required":true},{"description":"Time the question was taken up for judgment, 24-hour HH:MM:SS. In KP practice this is the moment the astrologer receives and understands the question, not the moment the querent first thought of it. It sets every planetary position and all twelve cusps except the Ascendant.","example":"14:30:00","key":"time","kind":"time","name":"time","required":true},{"description":"Latitude where the question is judged, decimal degrees. The house cusps are Placidus and therefore latitude dependent, so this is the place of judgment, not the querent birthplace.","example":19.076,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Longitude where the question is judged, decimal degrees.","example":72.8777,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"default":5.5,"description":"Timezone: IANA name (e.g. \"Asia/Kolkata\") OR decimal hours from UTC. Defaults to 5.5.","example":5.5,"key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"role":"location"},{"default":"kp-newcomb","description":"Ayanamsa system for sidereal conversion. \"kp-newcomb\" uses the KP-Newcomb dynamic formula (most common for KP). \"kp-old\" uses the Krishnamurti original table. \"lahiri\" uses Lahiri/Chitrapaksha ayanamsa matching most traditional Vedic software. \"raman\" uses the B.V. Raman ayanamsa, about 1.45 degrees below Lahiri. \"custom\" allows providing your own value via ayanamsaValue. Defaults to \"kp-newcomb\".","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"example":"kp-newcomb","fold":true,"key":"ayanamsa","kind":"tiles","name":"ayanamsa","required":false},{"description":"Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.","example":24,"fold":true,"key":"ayanamsaValue","kind":"number","name":"ayanamsaValue","required":false},{"default":"mean","description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the Rahu and Ketu positions. Mean is the traditional Vedic default and what printed panchangs use; the choice can move a KP sub-lord in narrow boundary cases, where a span can be as small as 0.5 degrees. Defaults to \"mean\".","enum":["mean","true"],"example":"mean","fold":true,"key":"nodeType","kind":"tiles","name":"nodeType","required":false},{"default":"general","description":"Which signification vocabulary the houseThemes map returns. \"general\" gives the classical bhava significations (self, wealth, siblings, home, and so on). \"finance\" gives the money reading of the same twelve bhavas, so house 2 returns income and savings, 5 speculation and risk appetite, 8 sudden money and leverage, 11 gains and profits, and 12 expenses and capital outflow. Use \"finance\" for wealth, income, business and market timing questions in Krishnamurti Paddhati, where the significator house groups 2, 6, 10, 11 for earned income and 5, 8, 11 for speculation are read against a running dasha. Defaults to \"general\".","enum":["general","finance"],"example":"general","fold":true,"inQuery":true,"key":"focus","kind":"tiles","name":"focus","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/vedic-astrology/kp/horary","title":"Cast a KP horary (Prashna) chart from a number 1-249"},"castLoveSpread":{"fields":[{"description":"Optional querent question to focus the love spread. It is echoed back on the reading and gives the five relationship positions their context. Omit for general relationship guidance.","example":"What do I need to know about my relationship?","key":"question","kind":"text","name":"question","required":false},{"description":"Optional seed for reproducible results. The same seed always draws the same five cards into the same love positions, which is what lets a reading be shared or re-rendered. Omit for a random draw.","example":"reading-2f9c1a","key":"seed","kind":"text","name":"seed","required":false,"role":"seed"}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/tarot/spreads/love","title":"Love spread, 5 cards"},"castReading":{"fields":[{"description":"Optional seed for reproducible castings. Same seed = same casting every time. Pass any unique identifier (userId, session token, question hash). Omit for random casting.","example":"user123-question1","inQuery":true,"key":"seed","kind":"text","name":"seed","required":false,"role":"seed"}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":true,"path":"/iching/cast","title":"Cast an I-Ching reading"},"castThreeCard":{"fields":[{"description":"Optional specific question to focus the reading. Examples: \"What should I know about my relationship?\", \"How can I improve my finances?\", \"What is blocking my creative growth?\" Leave empty for general guidance.","example":"What do I need to know about my career?","key":"question","kind":"text","name":"question","required":false},{"description":"Optional seed for reproducible results. Same seed = same 3 cards in same positions. Useful for sharing readings, testing, or ensuring users get consistent results. Omit for random draws.","example":"reading-2f9c1a","key":"seed","kind":"text","name":"seed","required":false,"role":"seed"}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/tarot/spreads/three-card","title":"Three card spread, past present future"},"castYesNo":{"fields":[{"description":"Your specific yes/no question. Be clear and focused. Good: \"Should I move to a new city?\" Bad: \"What should I do about my life?\" The more specific the question, the more useful the tarot guidance.","example":"Should I accept the job offer?","key":"question","kind":"text","name":"question","required":false},{"description":"Optional seed for reproducible results. Same seed + same question = same answer. Useful for testing, sharing readings, or ensuring consistency. Omit for random draws each time.","example":"reading-2f9c1a","key":"seed","kind":"text","name":"seed","required":false,"role":"seed"}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/tarot/yes-no","title":"Yes or no answer"},"checkKalsarpaDosha":{"fields":[{"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04","key":"date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00","key":"time","kind":"time","name":"time","required":true},{"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","example":28.6139,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","example":77.209,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"default":5.5,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time. Defaults to 5.5.","example":5.5,"key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"role":"location"},{"default":"lahiri","description":"Sidereal frame (ayanamsa) the chart is cast in. \"lahiri\" is Lahiri/Chitrapaksha, the traditional Vedic standard used by most software, and is the default. \"raman\" is the B.V. Raman ayanamsa from Hindu Predictive Astrology, about 1.45 degrees below Lahiri. \"kp-newcomb\" and \"kp-old\" are the two Krishnamurti Paddhati frames. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"example":"lahiri","fold":true,"key":"ayanamsa","kind":"tiles","name":"ayanamsa","required":false},{"description":"Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.","example":24,"fold":true,"key":"ayanamsaValue","kind":"number","name":"ayanamsaValue","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/vedic-astrology/dosha/kalsarpa","title":"Check Kalsarpa Dosha"},"checkKarmicDebt":{"fields":[{"description":"Birth year (checks Life Path)","example":1990,"key":"year","kind":"number","max":2100,"min":100,"name":"year","required":true},{"description":"Birth month (checks Life Path)","example":7,"key":"month","kind":"number","max":12,"min":1,"name":"month","required":true},{"description":"Birth day (checks Birth Day on its own, and Life Path with year and month)","example":15,"key":"day","kind":"number","max":31,"min":1,"name":"day","required":true},{"description":"Full birth name (checks Expression, Soul Urge, Personality). A name in any script is converted to Latin letters before it is counted, Cyrillic and Greek as the passport spelling and accents folded to the base letter, and the calculation lists the letters counted. For a script that does not write its vowels, send the Latin spelling the person uses.","example":"John William Smith","key":"fullName","kind":"text","name":"fullName","required":true}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/numerology/karmic-debt","requiredAnyOf":[["fullName","year","month","day"],["day"],["fullName"]],"title":"Detect Karmic Debt numbers"},"checkManglikDosha":{"fields":[{"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04","key":"date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00","key":"time","kind":"time","name":"time","required":true},{"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","example":28.6139,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","example":77.209,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"default":5.5,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time. Defaults to 5.5.","example":5.5,"key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"role":"location"},{"default":"lahiri","description":"Sidereal frame (ayanamsa) the chart is cast in. \"lahiri\" is Lahiri/Chitrapaksha, the traditional Vedic standard used by most software, and is the default. \"raman\" is the B.V. Raman ayanamsa from Hindu Predictive Astrology, about 1.45 degrees below Lahiri. \"kp-newcomb\" and \"kp-old\" are the two Krishnamurti Paddhati frames. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"example":"lahiri","fold":true,"key":"ayanamsa","kind":"tiles","name":"ayanamsa","required":false},{"description":"Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.","example":24,"fold":true,"key":"ayanamsaValue","kind":"number","name":"ayanamsaValue","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/vedic-astrology/dosha/manglik","title":"Check Manglik Dosha"},"checkSadhesati":{"fields":[{"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04","key":"date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00","key":"time","kind":"time","name":"time","required":true},{"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","example":28.6139,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","example":77.209,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"default":5.5,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time. Defaults to 5.5.","example":5.5,"key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"role":"location"},{"default":"lahiri","description":"Sidereal frame (ayanamsa) the chart is cast in. \"lahiri\" is Lahiri/Chitrapaksha, the traditional Vedic standard used by most software, and is the default. \"raman\" is the B.V. Raman ayanamsa from Hindu Predictive Astrology, about 1.45 degrees below Lahiri. \"kp-newcomb\" and \"kp-old\" are the two Krishnamurti Paddhati frames. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"example":"lahiri","fold":true,"key":"ayanamsa","kind":"tiles","name":"ayanamsa","required":false},{"description":"Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.","example":24,"fold":true,"key":"ayanamsaValue","kind":"number","name":"ayanamsaValue","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/vedic-astrology/dosha/sadhesati","title":"Check Sadhesati"},"convertLongCount":{"fields":[{"description":"Proleptic Gregorian date to convert INTO a Long Count. Supply this or longCount, never both and never neither.","example":"2012-12-21","key":"date","kind":"date","name":"date","required":true},{"description":"Dotted Long Count to convert INTO a date, written baktun.katun.tun.winal.kin. Each position is bounded by its own base, and the winal counts to 17 rather than to 19 because eighteen winal make a tun, so 9.12.11.18.0 is rejected as a date that does not exist. Supply this or date, never both and never neither.","example":"13.0.0.0.0","fold":true,"key":"longCount","kind":"text","name":"longCount","required":false},{"default":"gmt-584283","description":"Which correlation constant ties the day count to a civil date. This is the single choice that shifts every value in the response, so it is a parameter rather than a hidden default, and the resolved value comes back under conventions. \"gmt-584283\" is the commonly accepted constant and the default, and it is the one the major institutional converter runs on. \"martinez-hernandez-584281\" sits two days earlier, \"astronomical-584285\" two days later, and \"martin-skidmore-584286\" three days later, each shifting the Long Count by exactly its difference in days. Four of the eight published constants are offered: the other four sit tens of thousands of days away and are of historical interest only. The 584281 constant is the Martínez Hernández correlation, after Juan Martínez Hernández.","enum":["gmt-584283","martinez-hernandez-584281","astronomical-584285","martin-skidmore-584286"],"example":"gmt-584283","fold":true,"key":"correlation","kind":"tiles","name":"correlation","required":false}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/mesoamerican-astrology/mayan/long-count/convert","requiredAnyOf":[["date"],["longCount"]],"title":"Convert a Maya Long Count"},"detectAspectPatterns":{"fields":[{"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15","key":"date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00","key":"time","kind":"time","name":"time","required":true},{"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","example":40.7128,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","example":-74.006,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time.","example":"America/New_York","key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":true,"role":"location"},{"default":"true","description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"example":"true","fold":true,"key":"nodeType","kind":"tiles","name":"nodeType","required":false},{"description":"Use tighter orbs, so only closely formed patterns are reported. Truthy values (true, 1, yes, on; case-insensitive) narrow trine to 5 degrees, square to 5, sextile to 4, quincunx to 2. Defaults to false, the standard pattern-detection orbs.","example":"false","fold":true,"inQuery":true,"key":"strictOrbs","kind":"text","name":"strictOrbs","required":false},{"description":"Comma-separated list of optional bodies to include beyond the classical 10 planets. Valid tokens (case-insensitive): chiron, northNode (also accepts north_node, north-node, northnode). Empty by default.","example":"","fold":true,"inQuery":true,"key":"include","kind":"text","name":"include","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/astrology/aspect-patterns","title":"Detect aspect patterns"},"detectYogas":{"fields":[{"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04","key":"date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00","key":"time","kind":"time","name":"time","required":true},{"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","example":28.6139,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","example":77.209,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"default":5.5,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time. Defaults to 5.5.","example":5.5,"key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"role":"location"},{"default":"lahiri","description":"Sidereal frame (ayanamsa) the chart is cast in. \"lahiri\" is Lahiri/Chitrapaksha, the traditional Vedic standard used by most software, and is the default. \"raman\" is the B.V. Raman ayanamsa from Hindu Predictive Astrology, about 1.45 degrees below Lahiri. \"kp-newcomb\" and \"kp-old\" are the two Krishnamurti Paddhati frames. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"example":"lahiri","fold":true,"key":"ayanamsa","kind":"tiles","name":"ayanamsa","required":false},{"description":"Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.","example":24,"fold":true,"key":"ayanamsaValue","kind":"number","name":"ayanamsaValue","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/vedic-astrology/yoga/detect","title":"Detect classical Vedic yogas in a birth chart"},"drawCards":{"fields":[{"description":"Number of cards to draw (1-78). Common values: 1 for daily card, 3 for past-present-future, 5 for relationship spread, 10 for Celtic Cross. Drawing 78 returns the entire shuffled deck.","example":3,"key":"count","kind":"number","max":78,"min":1,"name":"count","required":true},{"description":"Optional seed for reproducible results. Same seed = same cards in same order. Use format like \"userId-date\" for daily consistency, or \"readingId\" for shareable readings. Omit for true randomness.","example":"user123-2025-12-27","key":"seed","kind":"text","name":"seed","required":false,"role":"seed"},{"default":true,"description":"Whether cards can appear reversed (upside down). Reversed cards have different meanings. Set false for upright-only readings. Default: true (50% chance of reversal per card).","example":true,"fold":true,"key":"allowReversals","kind":"toggle","name":"allowReversals","required":false},{"default":false,"description":"Whether same card can be drawn multiple times. Set false for traditional deck behavior (each card drawn only once). Set true for statistical analysis or oracle-style readings. Default: false.","example":false,"fold":true,"key":"allowDuplicates","kind":"toggle","name":"allowDuplicates","required":false}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/tarot/draw","title":"Draw tarot cards"},"findGrihaPraveshDates":{"fields":[{"description":"First day of the search window, in YYYY-MM-DD. Every limb is read at sunrise of the local day, because the Hindu day begins at sunrise rather than at midnight.","example":"2027-01-20","key":"startDate","kind":"date","name":"startDate","required":true},{"description":"Last day of the search window, in YYYY-MM-DD, inclusive. The window is capped at 93 days, which is a full season and the same cap the Vedic auspicious day search carries.","example":"2027-03-20","key":"endDate","kind":"date","name":"endDate","required":true},{"description":"Latitude of the house, in decimal degrees, positive north. Sunrise decides where one day ends and the next begins, so a nakshatra running out during the morning changes which day it counts for.","example":28.6139,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Longitude of the house, in decimal degrees, positive east.","example":77.209,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error.","example":"America/New_York","key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":true,"role":"location"},{"default":"muhurta-chintamani","description":"Which Muhurta text supplies the admissible nakshatras for entering a new house. muhurta-chintamani admits eight and kalaprakasika admits twelve; seven overlap and are the high confidence core, one is unique to the first and five to the second. The two texts are independent witnesses, which is what makes the overlap strong and the difference worth exposing. Defaults to muhurta-chintamani.","enum":["muhurta-chintamani","kalaprakasika"],"example":"muhurta-chintamani","fold":true,"key":"muhurtaText","kind":"tiles","name":"muhurtaText","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/vastu/timing/griha-pravesh","title":"Find griha pravesh dates"},"findSignificantDates":{"fields":[{"description":"Birth date in YYYY-MM-DD format. Anchors the natal chart and the Vimshottari dasha sequence.","example":"1990-07-15","group":"birthData","key":"birthData.date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Precision matters for the natal positions the transit aspects are measured against.","example":"13:30:00","group":"birthData","key":"birthData.time","kind":"time","name":"time","required":true},{"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error.","example":"America/New_York","group":"birthData","key":"birthData.timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":true,"role":"location"},{"default":0,"description":"Birth latitude in decimal degrees. Optional and does not affect the timeline. Defaults to 0.","example":0,"group":"birthData","key":"birthData.latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":false,"role":"location"},{"default":0,"description":"Birth longitude in decimal degrees. Optional and does not affect the timeline. Defaults to 0.","example":0,"group":"birthData","key":"birthData.longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":false,"role":"location"},{"description":"First day of the window in YYYY-MM-DD format. Defaults to today in UTC.","example":"2026-06-01","key":"startDate","kind":"date","moment":true,"name":"startDate","required":false},{"description":"Last day of the window in YYYY-MM-DD format. Defaults to startDate plus 30 days. Clamped to a maximum of 90 days from startDate.","example":"2026-08-30","key":"endDate","kind":"date","moment":true,"name":"endDate","required":false},{"description":"Which forecast domains to consider before filtering by significance. Defaults to all three.","example":["western","vedic","biorhythm"],"fold":true,"key":"domains","kind":"array","name":"domains","required":false},{"description":"Significance floor from 0 to 100 for what counts as a significant date. Defaults to 70.","example":70,"fold":true,"key":"minSignificance","kind":"number","max":100,"min":0,"name":"minSignificance","required":false},{"description":"Multiplier for this domain significance. 1 leaves it unchanged, above 1 promotes the domain, below 1 demotes it.","example":1.5,"fold":true,"group":"domainWeights","key":"domainWeights.western","kind":"number","max":100,"min":0,"name":"western","required":false},{"description":"Multiplier for this domain significance. 1 leaves it unchanged, above 1 promotes the domain, below 1 demotes it.","example":1.5,"fold":true,"group":"domainWeights","key":"domainWeights.vedic","kind":"number","max":100,"min":0,"name":"vedic","required":false},{"description":"Multiplier for this domain significance. 1 leaves it unchanged, above 1 promotes the domain, below 1 demotes it.","example":1.5,"fold":true,"group":"domainWeights","key":"domainWeights.biorhythm","kind":"number","max":100,"min":0,"name":"biorhythm","required":false}],"groups":[{"key":"birthData","label":"Birth Data","location":{"fields":["birthData.latitude","birthData.longitude","birthData.timezone"],"required":true}},{},{"fold":true,"key":"domainWeights","label":"Domain Weights"}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/forecast/significant-dates","title":"Significant dates"},"forecastSolarReturn":{"fields":[{"description":"Birth date in YYYY-MM-DD format. Anchors the natal Sun longitude the transiting Sun returns to each year.","example":"1990-07-15","key":"date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Pins the exact natal Sun position that defines the solar return moment.","example":"14:30:00","key":"time","kind":"time","name":"time","required":true},{"description":"Year to cast the solar return for. The chart is erected for the moment in this year when the transiting Sun returns to the natal Sun longitude, on or within a day of the birthday.","example":2026,"key":"year","kind":"number","max":2649,"min":1551,"name":"year","required":true},{"description":"Latitude of the solar return location in decimal degrees. The solar return is location-sensitive: use the birthplace to anchor the chart to natal geography, or the current city for a relocated solar return.","example":40.7128,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Longitude of the solar return location in decimal degrees. Sets the local sidereal time, so it drives the Ascendant, Midheaven, and house cusps of the return chart.","example":-74.006,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error.","example":"America/New_York","key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":true,"role":"location"},{"default":"placidus","description":"House system for the return chart. placidus is the Western default. whole-sign, equal, and koch are also supported.","enum":["placidus","whole-sign","equal","koch"],"example":"placidus","fold":true,"key":"houseSystem","kind":"tiles","name":"houseSystem","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/forecast/solar-return","title":"Solar return chart"},"forecastTransits":{"fields":[{"description":"Birth date in YYYY-MM-DD format. Anchors the natal chart and the Vimshottari dasha sequence.","example":"1990-07-15","group":"birthData","key":"birthData.date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Precision matters for the natal positions the transit aspects are measured against.","example":"13:30:00","group":"birthData","key":"birthData.time","kind":"time","name":"time","required":true},{"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error.","example":"America/New_York","group":"birthData","key":"birthData.timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":true,"role":"location"},{"default":0,"description":"Birth latitude in decimal degrees. Optional and does not affect the timeline. Defaults to 0.","example":0,"group":"birthData","key":"birthData.latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":false,"role":"location"},{"default":0,"description":"Birth longitude in decimal degrees. Optional and does not affect the timeline. Defaults to 0.","example":0,"group":"birthData","key":"birthData.longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":false,"role":"location"},{"description":"First day of the transit window in YYYY-MM-DD format. Defaults to today in UTC.","example":"2026-06-01","key":"startDate","kind":"date","moment":true,"name":"startDate","required":false},{"description":"Last day of the transit window in YYYY-MM-DD format. Defaults to startDate plus 30 days. Clamped to a maximum of 90 days from startDate.","example":"2026-08-30","key":"endDate","kind":"date","moment":true,"name":"endDate","required":false},{"description":"Drop transit events scoring below this significance threshold from 0 to 100. Defaults to 0.","example":0,"fold":true,"key":"minSignificance","kind":"number","max":100,"min":0,"name":"minSignificance","required":false}],"groups":[{"key":"birthData","label":"Birth Data","location":{"fields":["birthData.latitude","birthData.longitude","birthData.timezone"],"required":true}},{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/forecast/transits","title":"Western astrology forecast"},"generateAsteroids":{"fields":[{"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15","key":"date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00","key":"time","kind":"time","name":"time","required":true},{"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","example":40.7128,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","example":-74.006,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time.","example":"America/New_York","key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":true,"role":"location"},{"default":"true","description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"example":"true","fold":true,"key":"nodeType","kind":"tiles","name":"nodeType","required":false},{"default":"placidus","description":"House system used to assign each asteroid to a natal house. Placidus (default), Whole Sign, Equal, or Koch. Above the polar circle, quadrant systems fall back to Whole Sign and the echoed houseSystem reports the system actually used.","enum":["placidus","whole-sign","equal","koch"],"example":"placidus","fold":true,"key":"houseSystem","kind":"tiles","name":"houseSystem","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/astrology/asteroids","title":"Asteroid goddesses calculator"},"generateAstrocartography":{"fields":[{"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15","key":"date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00","key":"time","kind":"time","name":"time","required":true},{"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","example":40.7128,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","example":-74.006,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time.","example":"America/New_York","key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":true,"role":"location"},{"default":"true","description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"example":"true","fold":true,"key":"nodeType","kind":"tiles","name":"nodeType","required":false},{"description":"Optional comma separated list of extra bodies to plot beyond the ten classical planets. Allowed values: north-node, chiron, lilith. north-node is the mean lunar node. Unknown values are ignored. Defaults to none.","example":"chiron","fold":true,"inQuery":true,"key":"include","kind":"text","name":"include","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/astrology/astrocartography","title":"Astrocartography map"},"generateBaziChart":{"fields":[{"description":"Birth date in YYYY-MM-DD format. Sets the year, month and day pillars. The year pillar turns at Beginning of Spring rather than on 1 January, and the month pillar turns at each of the twelve minor solar terms rather than at a calendar month boundary.","example":"1990-06-15","key":"date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Sets the hour pillar, which is one of the four and carries the whole picture of later life and offspring. Each Earthly Branch covers two hours, so a birth within a few minutes of an odd hour can land in either. All four pillars are read in the local clock of the birth, and the day boundary is applied in that same clock; only the lunisolar calendar date itself is a world constant, fixed at UTC plus 8 so one instant has one Chinese date everywhere.","example":"14:30:00","key":"time","kind":"time","name":"time","required":true},{"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error.","example":"America/New_York","key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":true,"role":"location"},{"default":0,"description":"Birth latitude in decimal degrees. Accepted for consistency with the other birth-data endpoints and does not affect any part of a BaZi chart. Defaults to 0.","example":0,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":false,"role":"location"},{"description":"Birth longitude in decimal degrees. Positive is East, negative is West. Required when hourClock is \"local-mean\" or \"solar\", which shift the hour branch to the sun over the birth place; omitting it in either case returns 400. Ignored when hourClock is \"clock\".","example":116.4,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":false,"role":"location"},{"default":"split-zi","description":"Which instant starts the sexagenary DAY, which only matters for a birth between 23:00 and 23:59. \"midnight\" is the classical position of the Ming compendium San Ming Tong Hui: the day turns at 00:00 and 23:00 to 23:59 is the late zi hour of the day that is ending, so the hour stem is taken from that day. \"early-zi\" turns the whole day at 23:00, the practice in Hong Kong, Taiwan and much of South East Asia. \"split-zi\" is the compromise most software implements and the default here: the day still turns at 00:00, but the hour stem is taken from the next day. The three give three different answers for a late-evening birth and identical answers for every other birth.","enum":["split-zi","midnight","early-zi"],"example":"split-zi","fold":true,"key":"dayBoundary","kind":"tiles","name":"dayBoundary","required":false},{"default":"li-chun","description":"Which instant starts the sexagenary YEAR. \"li-chun\" is Beginning of Spring, around 4 February, and is the classical rule every BaZi text uses, so it is the default on this endpoint. \"lunar-new-year\" is the folk rule people mean when they say which animal they are, and it falls between late January and late February. The two disagree for any birth in the weeks between them: 14 February 2026 is a Wood Snake year under lunar-new-year and a Fire Horse year under li-chun.","enum":["li-chun","lunar-new-year"],"example":"li-chun","fold":true,"key":"yearBoundary","kind":"tiles","name":"yearBoundary","required":false},{"default":"clock","description":"Which clock the day boundary and the hour branch are read from, so a correction that carries a birth across midnight moves the day pillar with the hour. \"clock\" is civil time exactly as a birth certificate records it, which is what most calculators use and the default here. \"local-mean\" shifts to the mean sun over the birth longitude, a correction of up to 59 minutes at the edge of a wide time zone. \"solar\" adds the equation of time on top of that, up to a further 16 minutes. Both non-civil options need \"longitude\" in the request and return 400 without it.","enum":["clock","local-mean","solar"],"example":"clock","fold":true,"key":"hourClock","kind":"tiles","name":"hourClock","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/chinese-astrology/bazi/chart","title":"Generate BaZi chart"},"generateBirthChart":{"fields":[{"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04","key":"date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00","key":"time","kind":"time","name":"time","required":true},{"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","example":28.6139,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","example":77.209,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"default":5.5,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time. Defaults to 5.5.","example":5.5,"key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"role":"location"},{"default":"lahiri","description":"Sidereal frame (ayanamsa) the chart is cast in. \"lahiri\" is Lahiri/Chitrapaksha, the traditional Vedic standard used by most software, and is the default. \"raman\" is the B.V. Raman ayanamsa from Hindu Predictive Astrology, about 1.45 degrees below Lahiri. \"kp-newcomb\" and \"kp-old\" are the two Krishnamurti Paddhati frames. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"example":"lahiri","fold":true,"key":"ayanamsa","kind":"tiles","name":"ayanamsa","required":false},{"description":"Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.","example":24,"fold":true,"key":"ayanamsaValue","kind":"number","name":"ayanamsaValue","required":false},{"default":false,"description":"Set true to include a localized meaning and one-sentence classical interpretation beside each graha avastha state, under avasthaInfo on that graha in meta. Defaults to false, so an existing integration is byte-identical until it opts in. Saves a second call to GET /avasthas and the client-side join that would otherwise be needed to turn Yuva or Swapna into readable text.","example":true,"fold":true,"key":"avasthaInfo","kind":"toggle","name":"avasthaInfo","required":false},{"default":false,"description":"Set true to also return Uranus, Neptune and Pluto, under the Sanskrit names Arun, Varun and Yam that Indian software prints for them. They arrive in a separate modernPlanets array, NOT inside meta, because classical Jyotish is defined over nine grahas: the moderns rule no sign, so they have no dignity, avastha, combustion or aspect strength and it would be fabrication to report one. Each carries longitude, rashi, degree in sign, nakshatra with pada and lord, and retrograde status. Defaults to false, so an existing integration is byte-identical until it opts in.","example":true,"fold":true,"key":"modernPlanets","kind":"toggle","name":"modernPlanets","required":false},{"default":"general","description":"Which signification vocabulary the houseThemes map returns. \"general\" gives the classical bhava significations (self, wealth, siblings, home, and so on). \"finance\" gives the money reading of the same twelve bhavas, so house 2 returns income and savings, 5 speculation and risk appetite, 8 sudden money and leverage, 11 gains and profits, and 12 expenses and capital outflow. Use \"finance\" for wealth, income, business and market timing questions in Krishnamurti Paddhati, where the significator house groups 2, 6, 10, 11 for earned income and 5, 8, 11 for speculation are read against a running dasha. Defaults to \"general\".","enum":["general","finance"],"example":"general","fold":true,"inQuery":true,"key":"focus","kind":"tiles","name":"focus","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/vedic-astrology/birth-chart","title":"Get birth chart (D1 Rashi chart)"},"generateBirthProfile":{"fields":[{"description":"Birth date in YYYY-MM-DD, proleptic Gregorian. Dates before the 1582 reform are read on the same proleptic reckoning rather than switched to the Julian calendar.","example":"1990-06-15","key":"date","kind":"date","name":"date","required":true},{"description":"Birth time in HH:MM:SS local to the timezone field. Defaults to noon when omitted, which is stated because the name read from the hour changes every twenty minutes and a defaulted time cannot be precise.","example":"14:30:00","fold":true,"key":"time","kind":"time","name":"time","required":false},{"city":true,"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error.","example":"America/New_York","key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":true},{"default":"solar-longitude","description":"How the name of the day is found. Use solar-longitude for the exact five degree arc the Sun stood in at the birth moment, or lenain-blocks for the fixed civil calendar of five day periods. The Sun does not move at a constant rate, so the two drift apart by up to about three days by early August and were never reconciled.","enum":["solar-longitude","lenain-blocks"],"example":"solar-longitude","fold":true,"key":"angelDating","kind":"tiles","name":"angelDating","required":false},{"default":"march-21","description":"Which date the civil wheel of five day periods opens on. Both are conventions rather than facts: the equinox itself moves inside a window that covers both days, and it fell on 20 March in 2026. march-21 is the pinned published wheel and march-20 is that wheel shifted one day. Ignored when angelDating is solar-longitude.","enum":["march-21","march-20"],"example":"march-21","fold":true,"key":"yearStart","kind":"tiles","name":"yearStart","required":false},{"default":"extend-previous","description":"Where 29 February falls. The civil wheel was built for a 365 day year and has no slot for it, so published tables differ: extend-previous reads the day as part of the period ending 28 February, next-angel reads it as the opening of the period starting 1 March. Ignored when angelDating is solar-longitude.","enum":["extend-previous","next-angel"],"example":"extend-previous","fold":true,"key":"leapDayPolicy","kind":"tiles","name":"leapDayPolicy","required":false},{"default":false,"description":"Set true when the moment falls after nightfall, which advances the Hebrew date by one day because the Hebrew day begins in the evening. It is a caller assertion rather than a computation, since sunset depends on a place and this conversion takes none.","example":false,"fold":true,"key":"afterSunset","kind":"toggle","name":"afterSunset","required":false}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/kabbalah/birth-profile","title":"Generate a birth profile"},"generateBodygraph":{"fields":[{"description":"Birth date in YYYY-MM-DD format. The anchor for both the Personality activations at birth and the Design activations 88 degrees of solar arc earlier.","example":"1990-07-15","key":"date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Precision matters: the profile lines and gate boundaries shift with the exact minute of birth.","example":"13:00:00","key":"time","kind":"time","name":"time","required":true},{"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error.","example":"America/New_York","key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":true,"role":"location"},{"default":0,"description":"Birth latitude in decimal degrees. Optional and does not affect the bodygraph, which depends only on ecliptic longitudes. Defaults to 0.","example":0,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":false,"role":"location"},{"default":0,"description":"Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.","example":0,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":false,"role":"location"},{"default":"true","description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node activations. True is what professional Human Design software uses (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against, so leave it unset for a standard chart. It matters only when a node sits on a gate boundary, where the choice moves a node gate. Because a gate can be half of a channel, that can change the completed channels and, with them, whether a center reads defined or open, plus the definition, authority, profile or type. A chart where only one center disagrees is the usual shape, since the type and profile often survive unchanged. If another calculator disagrees on any of those, it is almost certainly using the mean node: pass \"mean\" to match it. Defaults to \"true\".","enum":["mean","true"],"example":"true","fold":true,"key":"nodeType","kind":"tiles","name":"nodeType","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/human-design/bodygraph","title":"Generate full Human Design bodygraph"},"generateCompositeChart":{"fields":[{"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15","group":"person1","key":"person1.date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00","group":"person1","key":"person1.time","kind":"time","name":"time","required":true},{"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","example":40.7128,"group":"person1","key":"person1.latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","example":-74.006,"group":"person1","key":"person1.longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time.","example":"America/New_York","group":"person1","key":"person1.timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":true,"role":"location"},{"default":"true","description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"example":"true","group":"person1","key":"person1.nodeType","kind":"tiles","name":"nodeType","required":false},{"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15","group":"person2","key":"person2.date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00","group":"person2","key":"person2.time","kind":"time","name":"time","required":true},{"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","example":40.7128,"group":"person2","key":"person2.latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","example":-74.006,"group":"person2","key":"person2.longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time.","example":"America/New_York","group":"person2","key":"person2.timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":true,"role":"location"},{"default":"true","description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"example":"true","group":"person2","key":"person2.nodeType","kind":"tiles","name":"nodeType","required":false},{"default":"placidus","description":"House system for the composite chart. Placidus (default), Whole Sign, Equal, or Koch.","enum":["placidus","whole-sign","equal","koch"],"example":"placidus","fold":true,"key":"houseSystem","kind":"tiles","name":"houseSystem","required":false}],"groups":[{"key":"person1","label":"Person 1","location":{"fields":["person1.latitude","person1.longitude","person1.timezone"],"required":true}},{"key":"person2","label":"Person 2","location":{"fields":["person2.latitude","person2.longitude","person2.timezone"],"required":true}},{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/astrology/composite-chart","title":"Composite Chart"},"generateDigest":{"fields":[{"description":"Birth date in YYYY-MM-DD format. Anchors the natal chart and the Vimshottari dasha sequence.","example":"1990-07-15","group":"birthData","key":"birthData.date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Precision matters for the natal positions the transit aspects are measured against.","example":"13:30:00","group":"birthData","key":"birthData.time","kind":"time","name":"time","required":true},{"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error.","example":"America/New_York","group":"birthData","key":"birthData.timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":true,"role":"location"},{"default":0,"description":"Birth latitude in decimal degrees. Optional and does not affect the timeline. Defaults to 0.","example":0,"group":"birthData","key":"birthData.latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":false,"role":"location"},{"default":0,"description":"Birth longitude in decimal degrees. Optional and does not affect the timeline. Defaults to 0.","example":0,"group":"birthData","key":"birthData.longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":false,"role":"location"},{"description":"Start anchor for every window in YYYY-MM-DD format. The next 24h, 7d, 30d, and 90d windows are measured forward from this date at 00:00:00 UTC. Defaults to today in UTC.","example":"2026-06-01","key":"startDate","kind":"date","moment":true,"name":"startDate","required":false},{"description":"Which forecast domains to include before rolling up the windows. Defaults to all three.","example":["western","vedic","biorhythm"],"fold":true,"key":"domains","kind":"array","name":"domains","required":false},{"description":"Drop events scoring below this significance threshold from 0 to 100 before the rollup. Defaults to 0.","example":0,"fold":true,"key":"minSignificance","kind":"number","max":100,"min":0,"name":"minSignificance","required":false},{"description":"Multiplier for this domain significance. 1 leaves it unchanged, above 1 promotes the domain, below 1 demotes it.","example":1.5,"fold":true,"group":"domainWeights","key":"domainWeights.western","kind":"number","max":100,"min":0,"name":"western","required":false},{"description":"Multiplier for this domain significance. 1 leaves it unchanged, above 1 promotes the domain, below 1 demotes it.","example":1.5,"fold":true,"group":"domainWeights","key":"domainWeights.vedic","kind":"number","max":100,"min":0,"name":"vedic","required":false},{"description":"Multiplier for this domain significance. 1 leaves it unchanged, above 1 promotes the domain, below 1 demotes it.","example":1.5,"fold":true,"group":"domainWeights","key":"domainWeights.biorhythm","kind":"number","max":100,"min":0,"name":"biorhythm","required":false},{"description":"Number of highest-significance events to surface per window. Defaults to 3, capped at 20.","example":3,"fold":true,"key":"top","kind":"number","max":20,"min":0,"name":"top","required":false}],"groups":[{"key":"birthData","label":"Birth Data","location":{"fields":["birthData.latitude","birthData.longitude","birthData.timezone"],"required":true}},{},{"fold":true,"key":"domainWeights","label":"Domain Weights"}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/forecast/digest","title":"Forecast digest"},"generateDivisionalChart":{"fields":[{"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04","key":"date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00","key":"time","kind":"time","name":"time","required":true},{"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","example":28.6139,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","example":77.209,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"default":5.5,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time. Defaults to 5.5.","example":5.5,"key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"role":"location"},{"default":"lahiri","description":"Sidereal frame (ayanamsa) the chart is cast in. \"lahiri\" is Lahiri/Chitrapaksha, the traditional Vedic standard used by most software, and is the default. \"raman\" is the B.V. Raman ayanamsa from Hindu Predictive Astrology, about 1.45 degrees below Lahiri. \"kp-newcomb\" and \"kp-old\" are the two Krishnamurti Paddhati frames. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"example":"lahiri","fold":true,"key":"ayanamsa","kind":"tiles","name":"ayanamsa","required":false},{"description":"Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.","example":24,"fold":true,"key":"ayanamsaValue","kind":"number","name":"ayanamsaValue","required":false},{"description":"Divisional chart number. Each division reveals a specific life area. Supported: 2 (Hora, wealth), 3 (Drekkana, siblings), 4 (Chaturthamsa, property), 7 (Saptamsa, children), 9 (Navamsa, marriage), 10 (Dasamsa, career), 12 (Dwadasamsa, parents), 16 (Shodasamsa, vehicles), 20 (Vimsamsa, spirituality), 24 (Chaturvimsamsa, education), 27 (Bhamsa, strength), 30 (Trimsamsa, misfortunes), 40 (Khavedamsa, merit), 45 (Akshavedamsa, character), 60 (Shashtiamsa, past life karma).","example":10,"key":"division","kind":"number","name":"division","required":true}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/vedic-astrology/divisional-chart","title":"Get divisional chart (Varga)"},"generateEightMansions":{"fields":[{"description":"Kua number to build the map for, if you already have one. Send this OR date and gender, not neither. A Kua of 5 is read as the Kua 2 chart, since 5 has no direction of its own.","example":6,"fold":true,"key":"kua","kind":"number","max":9,"min":1,"name":"kua","required":false},{"description":"Birth date in YYYY-MM-DD format, used to derive the Kua when no kua is sent. Requires gender alongside it. A date is read at the start of its day, so a birth date landing exactly on the year boundary is placed in the outgoing year.","example":"1985-07-15","key":"date","kind":"date","name":"date","required":true},{"description":"Selects the Kua formula variant. Required when the Kua is being derived from a birth date.","enum":["male","female"],"example":"male","key":"gender","kind":"tiles","name":"gender","required":true},{"default":"li-chun","description":"Which boundary starts the Chinese year when the Kua is derived from a birth date. Defaults to li-chun, the classical position. Ignored when a kua is sent directly, and echoed back either way.","enum":["li-chun","lunar-new-year"],"example":"li-chun","fold":true,"key":"yearBoundary","kind":"tiles","name":"yearBoundary","required":false},{"description":"Optional compass sector the main door faces, one of North, Northeast, East, Southeast, South, Southwest, West, Northwest. When sent, the response names the star sitting on that sector so a caller can judge an entrance without scanning the whole map.","enum":["North","Northeast","East","Southeast","South","Southwest","West","Northwest"],"example":"Southeast","fold":true,"key":"facing","kind":"tiles","name":"facing","required":false}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/feng-shui/eight-mansions","requiredAnyOf":[["date","gender"],["kua"]],"title":"Generate Eight Mansions map"},"generateFixedStars":{"fields":[{"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15","key":"date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00","key":"time","kind":"time","name":"time","required":true},{"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","example":40.7128,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","example":-74.006,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time.","example":"America/New_York","key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":true,"role":"location"},{"default":"true","description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"example":"true","fold":true,"key":"nodeType","kind":"tiles","name":"nodeType","required":false},{"default":1,"description":"Conjunction orb in degrees, the maximum separation for a star to count as conjunct a chart point. Defaults to 1, maximum 3. Widen it to surface looser contacts or tighten it for only the closest hits.","example":1,"fold":true,"inQuery":true,"key":"orb","kind":"number","max":3,"min":0,"name":"orb","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/astrology/fixed-stars","title":"Fixed stars and star conjunctions calculator"},"generateFlyingStarChart":{"fields":[{"description":"Construction period of the building, 1 to 9. This is the twenty year cycle the building was completed in, or last renovated heavily enough to reset, and it is fixed for the life of the building. Periods change at Li Chun in early February, so a building finished in January 2024 is a Period 8 building. Defaults to the period in force now.","example":9,"fold":true,"key":"period","kind":"number","max":9,"min":1,"name":"period","required":false},{"description":"The mountain the front of the building faces, by id or by compass label such as S2. Send this or facingDegrees, not neither. The facing side is the open, active, public side, which is not always the side with the front door.","enum":["ren","zi","gui","chou","gen","yin","jia","mao","yi","chen","xun","si","bing","wu","ding","wei","kun","shen","geng","you","xin","xu","qian","hai","N1","N2","N3","NE1","NE2","NE3","E1","E2","E3","SE1","SE2","SE3","S1","S2","S3","SW1","SW2","SW3","W1","W2","W3","NW1","NW2","NW3"],"example":"wu","fold":true,"key":"facing","kind":"select","name":"facing","required":false},{"description":"The compass bearing the front of the building faces, 0 to 360 degrees, measured looking out from inside. Resolved to one of the 24 mountains. Send this or facing, not neither.","example":180,"key":"facingDegrees","kind":"number","max":360,"min":0,"name":"facingDegrees","required":true}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/feng-shui/flying-stars/natal","requiredAnyOf":[["facingDegrees"],["facing"]],"title":"Generate flying star natal chart"},"generateKpChart":{"fields":[{"description":"Birth date in YYYY-MM-DD format","example":"1990-07-04","key":"date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. CRITICAL for accurate Lagna and house calculations.","example":"10:12:00","key":"time","kind":"time","name":"time","required":true},{"description":"Birth location latitude in decimal degrees","example":28.6139,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Birth location longitude in decimal degrees","example":77.209,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"default":5.5,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time. Defaults to 5.5 (IST) for Vedic astrology.","example":5.5,"key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"role":"location"},{"default":"kp-newcomb","description":"Ayanamsa system for sidereal conversion. \"kp-newcomb\" uses the KP-Newcomb dynamic formula (most common for KP). \"kp-old\" uses the Krishnamurti original table. \"lahiri\" uses Lahiri/Chitrapaksha ayanamsa matching most traditional Vedic software. \"raman\" uses the B.V. Raman ayanamsa, about 1.45 degrees below Lahiri. \"custom\" allows providing your own value via ayanamsaValue. Defaults to \"kp-newcomb\".","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"example":"kp-newcomb","fold":true,"key":"ayanamsa","kind":"tiles","name":"ayanamsa","required":false},{"description":"Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.","example":24,"fold":true,"key":"ayanamsaValue","kind":"number","name":"ayanamsaValue","required":false},{"default":"mean","description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the Rahu and Ketu positions. Mean is the traditional Vedic default and what printed panchangs use; the choice can move a KP sub-lord in narrow boundary cases, where a span can be as small as 0.5 degrees. Defaults to \"mean\".","enum":["mean","true"],"example":"mean","fold":true,"key":"nodeType","kind":"tiles","name":"nodeType","required":false},{"default":"general","description":"Which signification vocabulary the houseThemes map returns. \"general\" gives the classical bhava significations (self, wealth, siblings, home, and so on). \"finance\" gives the money reading of the same twelve bhavas, so house 2 returns income and savings, 5 speculation and risk appetite, 8 sudden money and leverage, 11 gains and profits, and 12 expenses and capital outflow. Use \"finance\" for wealth, income, business and market timing questions in Krishnamurti Paddhati, where the significator house groups 2, 6, 10, 11 for earned income and 5, 8, 11 for speculation are read against a running dasha. Defaults to \"general\".","enum":["general","finance"],"example":"general","fold":true,"inQuery":true,"key":"focus","kind":"tiles","name":"focus","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/vedic-astrology/kp/chart","title":"Generate complete KP birth chart"},"generateLilith":{"fields":[{"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15","key":"date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00","key":"time","kind":"time","name":"time","required":true},{"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","example":40.7128,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","example":-74.006,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time.","example":"America/New_York","key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":true,"role":"location"},{"default":"true","description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"example":"true","fold":true,"key":"nodeType","kind":"tiles","name":"nodeType","required":false},{"default":"placidus","description":"House system used to place each Lilith variant in a house. Placidus (default), Whole Sign, Equal, or Koch.","enum":["placidus","whole-sign","equal","koch"],"example":"placidus","fold":true,"key":"houseSystem","kind":"tiles","name":"houseSystem","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/astrology/lilith","title":"Black Moon Lilith calculator"},"generateLocalSpace":{"fields":[{"description":"Birth date in YYYY-MM-DD format. Combined with time and timezone it fixes the birth instant whose planetary positions are projected onto the local horizon.","example":"1990-07-15","key":"date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Time is essential: the local horizon rotates a full circle each day, so the azimuth (compass direction) of every body depends on the exact birth time.","example":"14:30:00","key":"time","kind":"time","name":"time","required":true},{"description":"Birthplace latitude in decimal degrees (-90 to 90). This is the origin point of every local space line and the observer latitude used to turn each body into an azimuth and altitude.","example":40.7128,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Birthplace longitude in decimal degrees (-180 to 180). Sets the local horizon orientation and the starting point from which the directional lines radiate.","example":-74.006,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"description":"Decimal hours from UTC (e.g. -5 for EST, 5.5 for IST, 9 for JST) OR IANA name (e.g. \"America/New_York\"). IANA resolved to the offset in force at the birth date and time.","example":"America/New_York","key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":true,"role":"location"},{"description":"Optional comma-separated extra bodies to add beyond the 10 classical planets. Allowed values: north-node, chiron, lilith. north-node is the mean lunar node. Omit to return the 10 classical planets only.","example":"chiron,lilith","fold":true,"inQuery":true,"key":"include","kind":"text","name":"include","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/astrology/local-space","title":"Local space astrology map"},"generateLunarReturn":{"fields":[{"description":"Original birth date in YYYY-MM-DD format. Used to determine natal Moon longitude for the lunar return calculation.","example":"1990-07-15","key":"birthDate","kind":"date","name":"birthDate","required":true},{"description":"Original birth time in 24-hour HH:MM:SS format. Determines exact natal Moon position for monthly return timing.","example":"14:30:00","key":"birthTime","kind":"time","name":"birthTime","required":true},{"description":"Approximate date near the desired lunar return (YYYY-MM-DD). The Moon returns to its natal position every ~27.3 days, so provide a date within a few days of the expected return.","example":"2026-02-12","key":"returnDate","kind":"date","name":"returnDate","required":true},{"description":"Latitude of the lunar return location in decimal degrees (-90 to 90). Affects the Ascendant and house cusps of the return chart.","example":40.7128,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Longitude of the lunar return location in decimal degrees (-180 to 180). Determines local sidereal time for house calculations.","example":-74.006,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"description":"Decimal hours from UTC OR IANA name (e.g. \"America/New_York\"). IANA resolved to the DST-correct offset for the birthDate. Output datetime is adjusted to this timezone.","example":"America/New_York","key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":true,"role":"location"},{"default":"placidus","description":"House system for the lunar return chart. Placidus (default), Whole Sign, Equal, or Koch.","enum":["placidus","whole-sign","equal","koch"],"example":"placidus","fold":true,"key":"houseSystem","kind":"tiles","name":"houseSystem","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/astrology/lunar-return","title":"Lunar Return Chart"},"generateMandala":{"fields":[{"description":"East-west extent of a rectangular plot, in the unit given. Send this with depth for a rectangle, or send polygon instead.","example":30,"group":"plot","key":"plot.width","kind":"number","min":0,"name":"width","required":true},{"description":"North-south extent of a rectangular plot, in the unit given. Send this with width for a rectangle, or send polygon instead.","example":40,"group":"plot","key":"plot.depth","kind":"number","min":0,"name":"depth","required":true},{"default":"feet","description":"Unit the plot dimensions are given in. Every distance the response returns is in this same unit. The mandala projection is scale free, so this affects the areas and the marma size and nothing else.","enum":["feet","metres"],"example":"feet","group":"plot","key":"plot.unit","kind":"tiles","name":"unit","required":false},{"default":"81-pada","description":"Which division of the ground to read: 81-pada is the Paramasayika of Brihat Samhita 53.42, the grid the chapter numbers and names every devata on, and 64-pada is the Manduka of 53.55, for which the chapter gives structure only and no devata names. Defaults to 81-pada.","enum":["81-pada","64-pada"],"example":"81-pada","fold":true,"key":"grid","kind":"tiles","name":"grid","required":false}],"groups":[{"key":"plot","label":"Plot"},{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/vastu/mandala","title":"Generate Vastu Purusha Mandala"},"generateMayanChart":{"fields":[{"description":"Date in YYYY-MM-DD format, in the PROLEPTIC GREGORIAN calendar, extended backwards unchanged through the 1582 reform. Years 1 to 4000 are accepted. A reference converter that switches to the Julian calendar below the reform will disagree with a date before 15 October 1582 by ten or eleven days; that is a difference of input convention rather than of arithmetic, and passing the Julian equivalent to such a tool reproduces these values exactly. A single-digit month or day is accepted and zero padded.","example":"2012-12-21","key":"date","kind":"date","name":"date","required":true},{"default":"gmt-584283","description":"Which correlation constant ties the day count to a civil date. This is the single choice that shifts every value in the response, so it is a parameter rather than a hidden default, and the resolved value comes back under conventions. \"gmt-584283\" is the commonly accepted constant and the default, and it is the one the major institutional converter runs on. \"martinez-hernandez-584281\" sits two days earlier, \"astronomical-584285\" two days later, and \"martin-skidmore-584286\" three days later, each shifting the Long Count by exactly its difference in days. Four of the eight published constants are offered: the other four sit tens of thousands of days away and are of historical interest only. The 584281 constant is the Martínez Hernández correlation, after Juan Martínez Hernández.","enum":["gmt-584283","martinez-hernandez-584281","astronomical-584285","martin-skidmore-584286"],"example":"gmt-584283","fold":true,"key":"correlation","kind":"tiles","name":"correlation","required":false},{"default":"classic","description":"Which Haab day is read as the start of the year when naming its Year Bearer. Only four of the twenty day signs can ever carry a year, and which four depends entirely on this choice, so the three schools never agree. \"classic\" reads the seating of Pop and is the default, because it is the set highland daykeepers still use; its four bearers are Ikʼ, Manikʼ, Ebʼ and Kabʼan. \"campeche\" reads 1 Pop and gives Akʼbʼal, Lamat, Bʼen and Etzʼnabʼ. \"colonial-yucatec\" reads 2 Pop and gives Kʼan, Muluk, Ix and Kawak. The three sets share no member, so a bearer alone tells you which school produced it.","enum":["classic","campeche","colonial-yucatec"],"example":"classic","fold":true,"key":"yearBearerSystem","kind":"tiles","name":"yearBearerSystem","required":false}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/mesoamerican-astrology/mayan/chart","title":"Generate a Mayan chart"},"generateNameProfile":{"fields":[{"description":"The name in Latin script, to be written in Hebrew and then scored. Non Latin scripts are folded to Latin first. Send nameHebrew instead to control the spelling yourself.","example":"Sarah","key":"name","kind":"text","name":"name","required":true},{"description":"The name already in Hebrew, which skips the transliteration step entirely and scores exactly the spelling you sent.","example":"שרה","fold":true,"key":"nameHebrew","kind":"text","name":"nameHebrew","required":false},{"default":"letter-map-mathers","description":"How a Latin name is written in Hebrew before it is scored. Two members. letter-map-mathers is the 1887 Hermetic letter map, with e read as its author practised it: a point inside a word and alef at the start of one. It writes no c, f, w or x, so a name carrying one of them outside a two letter group returns 400 naming the letter. letter-map-modern follows the modern Israeli transcription rules for the sound each Latin letter carries in English and French spelling, covers every Latin letter, drops the geresh and does not double vav or yod, so send textHebrew for the ktiv male form. Every form states the readings it used in rule. Phonetic Ashkenazi and Sephardi schemes are not offered because no two references agree on a rule for that direction.","enum":["letter-map-mathers","letter-map-modern"],"example":"letter-map-mathers","fold":true,"key":"transliteration","kind":"tiles","name":"transliteration","required":false},{"default":"finals-500-900","description":"Which method the name mispar gadol means, because the sources use it for two. Use finals-500-900 to score the five word final letters as 500 to 900, or milui to score each letter as the value of its own spelled out name.","enum":["finals-500-900","milui"],"example":"finals-500-900","fold":true,"key":"misparGadol","kind":"tiles","name":"misparGadol","required":false}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/kabbalah/name-profile","requiredAnyOf":[["name"],["nameHebrew"]],"title":"Generate a name profile"},"generateNatalChart":{"fields":[{"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15","key":"date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00","key":"time","kind":"time","name":"time","required":true},{"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","example":40.7128,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","example":-74.006,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time.","example":"America/New_York","key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":true,"role":"location"},{"default":"true","description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"example":"true","fold":true,"key":"nodeType","kind":"tiles","name":"nodeType","required":false},{"default":"placidus","description":"House system for dividing the chart into 12 houses. Placidus (default) is most popular in Western astrology and time-sensitive. Whole Sign assigns one sign per house (simpler, ancient). Equal houses divide chart into 30° segments from Ascendant. Koch emphasizes houses in high latitudes.","enum":["placidus","whole-sign","equal","koch"],"example":"placidus","fold":true,"key":"houseSystem","kind":"tiles","name":"houseSystem","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/astrology/natal-chart","title":"Generate natal chart"},"generateNavamsa":{"fields":[{"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04","key":"date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00","key":"time","kind":"time","name":"time","required":true},{"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","example":28.6139,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","example":77.209,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"default":5.5,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time. Defaults to 5.5.","example":5.5,"key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"role":"location"},{"default":"lahiri","description":"Sidereal frame (ayanamsa) the chart is cast in. \"lahiri\" is Lahiri/Chitrapaksha, the traditional Vedic standard used by most software, and is the default. \"raman\" is the B.V. Raman ayanamsa from Hindu Predictive Astrology, about 1.45 degrees below Lahiri. \"kp-newcomb\" and \"kp-old\" are the two Krishnamurti Paddhati frames. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"example":"lahiri","fold":true,"key":"ayanamsa","kind":"tiles","name":"ayanamsa","required":false},{"description":"Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.","example":24,"fold":true,"key":"ayanamsaValue","kind":"number","name":"ayanamsaValue","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/vedic-astrology/navamsa","title":"Get Navamsa chart (D9)"},"generateNumerologyChart":{"fields":[{"description":"Full birth name as it appears on the birth certificate. Used for every letter-based number in the chart: Expression, Soul Urge, Personality, Karmic Lessons, Hidden Passion, Subconscious Self and the special letters. A name in any script is converted to Latin letters before it is counted, Cyrillic and Greek as the passport spelling and accents folded to the base letter, and the calculation lists the letters counted. For a script that does not write its vowels, send the Latin spelling the person uses.","example":"John William Smith","key":"fullName","kind":"text","name":"fullName","required":true},{"description":"Birth year between 100 and 2100. Supports historical figures like Einstein (1879) and Shakespeare (1564).","example":1990,"key":"year","kind":"number","max":2100,"min":100,"name":"year","required":true},{"description":"Birth month (1-12)","example":7,"key":"month","kind":"number","max":12,"min":1,"name":"month","required":true},{"description":"Birth day (1-31)","example":15,"key":"day","kind":"number","max":31,"min":1,"name":"day","required":true},{"description":"Calendar year for the Personal Year, defaults to the current UTC year. It moves the Personal Year only: the nested personalMonth and maturityStatus.currentAge always read the current UTC date.","example":2025,"fold":true,"key":"currentYear","kind":"number","max":2100,"min":100,"name":"currentYear","required":false}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/numerology/chart","title":"Generate numerology chart"},"generatePlanetaryReturn":{"fields":[{"description":"Original birth date in YYYY-MM-DD format. Used to determine the natal longitude of the selected planet.","example":"1990-07-15","key":"birthDate","kind":"date","name":"birthDate","required":true},{"description":"Original birth time in 24-hour HH:MM:SS format. Determines exact natal planet position for return timing.","example":"14:30:00","key":"birthTime","kind":"time","name":"birthTime","required":true},{"description":"Planet for the return calculation. Supports Mercury (~88 days), Venus (~225 days), Mars (~687 days), Jupiter (~12 years), and Saturn (~29 years). Saturn return is a major life milestone in Western astrology.","enum":["Mercury","Venus","Mars","Jupiter","Saturn"],"example":"Jupiter","key":"planet","kind":"tiles","name":"planet","required":true},{"description":"Approximate date near the expected planetary return (YYYY-MM-DD). The return nearest this date is returned, so a date off by months still lands on a genuine return; during a retrograde loop the planet crosses its natal degree up to three times and the crossing nearest the date is the one returned.","example":"2026-08-15","key":"approximateDate","kind":"date","name":"approximateDate","required":true},{"description":"Latitude of the return location in decimal degrees (-90 to 90). Affects house cusps and Ascendant of the return chart.","example":40.7128,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Longitude of the return location in decimal degrees (-180 to 180).","example":-74.006,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"description":"Decimal hours from UTC OR IANA name (e.g. \"America/New_York\"). IANA resolved to the DST-correct offset for the birthDate. Output datetime is adjusted to this timezone.","example":"America/New_York","key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":true,"role":"location"},{"default":"placidus","description":"House system for the return chart. Placidus (default), Whole Sign, Equal, or Koch.","enum":["placidus","whole-sign","equal","koch"],"example":"placidus","fold":true,"key":"houseSystem","kind":"tiles","name":"houseSystem","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/astrology/planetary-returns","title":"Planetary Return Chart"},"generateProfections":{"fields":[{"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15","key":"date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00","key":"time","kind":"time","name":"time","required":true},{"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","example":40.7128,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","example":-74.006,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time.","example":"America/New_York","key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":true,"role":"location"},{"default":"true","description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"example":"true","fold":true,"key":"nodeType","kind":"tiles","name":"nodeType","required":false},{"description":"Date whose profection year you want, in YYYY-MM-DD format. The completed whole years from the birth date to this date select the profected house and sign. Must fall on or after the birth date.","example":"2025-08-04","key":"targetDate","kind":"date","name":"targetDate","required":true},{"default":"placidus","description":"House system used only to report where the lord of the year sits in the natal chart. The profected house and sign always use whole sign profection from the rising sign. Placidus (default), Whole Sign, Equal, or Koch.","enum":["placidus","whole-sign","equal","koch"],"example":"placidus","fold":true,"key":"houseSystem","kind":"tiles","name":"houseSystem","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/astrology/profections","title":"Annual profections calculator"},"generateProgressions":{"fields":[{"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15","key":"date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00","key":"time","kind":"time","name":"time","required":true},{"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","example":40.7128,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","example":-74.006,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time.","example":"America/New_York","key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":true,"role":"location"},{"default":"true","description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"example":"true","fold":true,"key":"nodeType","kind":"tiles","name":"nodeType","required":false},{"description":"Date to progress the chart to, in YYYY-MM-DD format. Usually today or a forecast date. The day-for-a-year key turns the elapsed years since birth into the same number of ephemeris days after the birth moment.","example":"2025-07-15","key":"targetDate","kind":"date","name":"targetDate","required":true}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/astrology/progressions","title":"Secondary progressions calculator"},"generateRelocationChart":{"fields":[{"description":"Birth date in YYYY-MM-DD format. The birth moment is unchanged by relocation, so this still defines the planetary positions of the chart.","example":"1961-08-04","key":"date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Combined with the timezone it fixes the exact birth instant, which the relocated angles and houses are recomputed for.","example":"19:24:00","key":"time","kind":"time","name":"time","required":true},{"description":"Birth timezone: decimal hours from UTC (e.g. -5 for EST, 5.5 for IST) OR IANA name (e.g. \"America/New_York\"). Resolved to the offset in force at the birth date and time. This is the birthplace timezone, not the new location timezone.","example":-10,"key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":true,"role":"location"},{"description":"Birthplace latitude in decimal degrees (-90 to 90). Used for the original natal angles and houses that the relocated chart is compared against.","example":21.3069,"group":"birth","key":"birthLatitude","kind":"number","label":"Birth latitude","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Birthplace longitude in decimal degrees (-180 to 180). Positive East, negative West.","example":-157.8583,"group":"birth","key":"birthLongitude","kind":"number","label":"Birth longitude","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"description":"New location latitude in decimal degrees (-90 to 90). The relocated Ascendant and house cusps are most sensitive to north-south movement.","example":40.7167,"group":"relocation","key":"relocationLatitude","kind":"number","label":"Relocation latitude","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"New location longitude in decimal degrees (-180 to 180). The relocated Midheaven shifts roughly one degree per degree of longitude moved.","example":-74.006,"group":"relocation","key":"relocationLongitude","kind":"number","label":"Relocation longitude","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"default":"placidus","description":"House system for dividing the relocated chart into 12 houses. Placidus (default) is time-sensitive and most popular in Western astrology. Whole Sign assigns one sign per house. Equal divides into 30 degree segments from the Ascendant. Koch emphasizes higher latitudes. Quadrant systems fall back to Whole Sign above the polar circle.","enum":["placidus","whole-sign","equal","koch"],"example":"placidus","fold":true,"key":"houseSystem","kind":"tiles","name":"houseSystem","required":false}],"groups":[{},{"key":"birth","label":"Birth","location":{"fields":["birthLatitude","birthLongitude","timezone"],"required":true}},{"key":"relocation","label":"Relocation","location":{"fields":["relocationLatitude","relocationLongitude"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/astrology/relocation-chart","title":"Generate relocation chart"},"generateSolarArc":{"fields":[{"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15","key":"date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00","key":"time","kind":"time","name":"time","required":true},{"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","example":40.7128,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","example":-74.006,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time.","example":"America/New_York","key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":true,"role":"location"},{"default":"true","description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"example":"true","fold":true,"key":"nodeType","kind":"tiles","name":"nodeType","required":false},{"description":"Date to direct the chart to, in YYYY-MM-DD format. Every natal point is advanced by the solar arc accumulated from birth to this date, about one degree for each year of life.","example":"2025-07-15","key":"targetDate","kind":"date","name":"targetDate","required":true}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/astrology/solar-arc","title":"Solar arc directions calculator"},"generateSolarReturn":{"fields":[{"description":"Original birth date in YYYY-MM-DD format. Used to determine natal Sun longitude for the solar return calculation.","example":"1990-07-15","key":"birthDate","kind":"date","name":"birthDate","required":true},{"description":"Original birth time in 24-hour HH:MM:SS format. Determines exact natal Sun position for annual return timing.","example":"14:30:00","key":"birthTime","kind":"time","name":"birthTime","required":true},{"description":"Year for which to cast the solar return chart. The chart is erected for the exact moment the transiting Sun conjuncts the natal Sun longitude in this year.","example":2026,"key":"returnYear","kind":"number","name":"returnYear","required":true},{"description":"Latitude of the solar return location in decimal degrees (-90 to 90). Use current residence or travel location at time of birthday. Solar return charts are location-sensitive.","example":40.7128,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Longitude of the solar return location in decimal degrees (-180 to 180). Affects house cusps and Ascendant of the return chart.","example":-74.006,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"description":"Decimal hours from UTC OR IANA name (e.g. \"America/New_York\"). IANA resolved to the DST-correct offset for the birthDate. Output datetime is adjusted to this timezone.","example":"America/New_York","key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":true,"role":"location"},{"default":"placidus","description":"House system for the solar return chart. Placidus (default) is most common in Western astrology. Whole Sign, Equal, and Koch also supported.","enum":["placidus","whole-sign","equal","koch"],"example":"placidus","fold":true,"key":"houseSystem","kind":"tiles","name":"houseSystem","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/astrology/solar-return","title":"Solar Return Chart"},"generateTimeline":{"fields":[{"description":"Birth date in YYYY-MM-DD format. Anchors the natal chart and the Vimshottari dasha sequence.","example":"1990-07-15","group":"birthData","key":"birthData.date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Precision matters for the natal positions the transit aspects are measured against.","example":"13:30:00","group":"birthData","key":"birthData.time","kind":"time","name":"time","required":true},{"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error.","example":"America/New_York","group":"birthData","key":"birthData.timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":true,"role":"location"},{"default":0,"description":"Birth latitude in decimal degrees. Optional and does not affect the timeline. Defaults to 0.","example":0,"group":"birthData","key":"birthData.latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":false,"role":"location"},{"default":0,"description":"Birth longitude in decimal degrees. Optional and does not affect the timeline. Defaults to 0.","example":0,"group":"birthData","key":"birthData.longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":false,"role":"location"},{"description":"First day of the forecast window in YYYY-MM-DD format. Defaults to today in UTC.","example":"2026-06-01","key":"startDate","kind":"date","moment":true,"name":"startDate","required":false},{"description":"Last day of the forecast window in YYYY-MM-DD format. Defaults to startDate plus 30 days. The window is clamped to a maximum of 90 days from startDate.","example":"2026-08-30","key":"endDate","kind":"date","moment":true,"name":"endDate","required":false},{"description":"Which forecast domains to include. Defaults to all three. Pass a subset to scope the timeline to one or two engines.","example":["western","vedic","biorhythm"],"fold":true,"key":"domains","kind":"array","name":"domains","required":false},{"description":"Drop events scoring below this significance threshold from 0 to 100. Defaults to 0, keeping all events.","example":0,"fold":true,"key":"minSignificance","kind":"number","max":100,"min":0,"name":"minSignificance","required":false},{"description":"Multiplier for this domain significance. 1 leaves it unchanged, above 1 promotes the domain, below 1 demotes it.","example":1.5,"fold":true,"group":"domainWeights","key":"domainWeights.western","kind":"number","max":100,"min":0,"name":"western","required":false},{"description":"Multiplier for this domain significance. 1 leaves it unchanged, above 1 promotes the domain, below 1 demotes it.","example":1.5,"fold":true,"group":"domainWeights","key":"domainWeights.vedic","kind":"number","max":100,"min":0,"name":"vedic","required":false},{"description":"Multiplier for this domain significance. 1 leaves it unchanged, above 1 promotes the domain, below 1 demotes it.","example":1.5,"fold":true,"group":"domainWeights","key":"domainWeights.biorhythm","kind":"number","max":100,"min":0,"name":"biorhythm","required":false}],"groups":[{"key":"birthData","label":"Birth Data","location":{"fields":["birthData.latitude","birthData.longitude","birthData.timezone"],"required":true}},{},{"fold":true,"key":"domainWeights","label":"Domain Weights"}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/forecast/timeline","title":"Cross-domain forecast timeline"},"generateTransit":{"fields":[{"description":"Birth date in YYYY-MM-DD format. The anchor for both the Personality activations at birth and the Design activations 88 degrees of solar arc earlier.","example":"1990-07-15","group":"birthData","key":"birthData.date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Precision matters: the profile lines and gate boundaries shift with the exact minute of birth.","example":"13:00:00","group":"birthData","key":"birthData.time","kind":"time","name":"time","required":true},{"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error.","example":"America/New_York","group":"birthData","key":"birthData.timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":true,"role":"location"},{"default":0,"description":"Birth latitude in decimal degrees. Optional and does not affect the bodygraph, which depends only on ecliptic longitudes. Defaults to 0.","example":0,"group":"birthData","key":"birthData.latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":false,"role":"location"},{"default":0,"description":"Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.","example":0,"group":"birthData","key":"birthData.longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":false,"role":"location"},{"default":"true","description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node activations. True is what professional Human Design software uses (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against, so leave it unset for a standard chart. It matters only when a node sits on a gate boundary, where the choice moves a node gate. Because a gate can be half of a channel, that can change the completed channels and, with them, whether a center reads defined or open, plus the definition, authority, profile or type. A chart where only one center disagrees is the usual shape, since the type and profile often survive unchanged. If another calculator disagrees on any of those, it is almost certainly using the mean node: pass \"mean\" to match it. Defaults to \"true\".","enum":["mean","true"],"example":"true","group":"birthData","key":"birthData.nodeType","kind":"tiles","name":"nodeType","required":false},{"description":"Transit date in YYYY-MM-DD UTC. Optional. Defaults to today in UTC when omitted, giving the just-now transit.","example":"2026-05-23","key":"date","kind":"date","label":"Transit date","moment":true,"name":"date","required":false},{"description":"Transit time in HH:MM:SS UTC. Optional. Defaults to the current UTC time when omitted. Precision matters: the Moon moves through a gate in roughly half a day.","example":"12:00:00","key":"time","kind":"time","label":"Transit time","moment":true,"name":"time","required":false}],"groups":[{"key":"birthData","label":"Birth Data","location":{"fields":["birthData.latitude","birthData.longitude","birthData.timezone"],"required":true}},{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/human-design/transit","title":"Generate Human Design transit overlay"},"getAlmanacDay":{"fields":[{"description":"Gregorian date in YYYY-MM-DD format, evaluated at the reference meridian. Years 1900 to 2100.","example":"1990-06-15","inQuery":false,"key":"date","kind":"date","name":"date","required":true}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":false,"path":"/chinese-astrology/calendar/day/{date}","title":"Get the almanac for a day"},"getAngelNumber":{"fields":[{"description":"Angel number sequence to look up (e.g., \"111\", \"444\", \"1212\", \"1234\"). Must match an entry in the database.","example":"444","inQuery":false,"key":"number","kind":"text","name":"number","required":true,"source":{"lang":true,"limit":50,"path":"/angel-numbers/numbers"}}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":false,"path":"/angel-numbers/numbers/{number}","title":"Get angel number meaning"},"getAnnualAfflictions":{"fields":[{"description":"Solar year, 1900 to 2100. The year runs from Li Chun to Li Chun, so a date in January belongs to the previous year here.","example":2026,"inQuery":false,"key":"year","kind":"number","max":2100,"min":1900,"name":"year","required":true}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":false,"path":"/feng-shui/afflictions/{year}","title":"Annual afflictions"},"getAnnualFlyingStars":{"fields":[{"description":"Solar year, 1900 to 2100. The year runs from Li Chun to Li Chun, so a date in January belongs to the previous year here.","example":2026,"inQuery":false,"key":"year","kind":"number","max":2100,"min":1900,"name":"year","required":true}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":false,"path":"/feng-shui/flying-stars/annual/{year}","title":"Annual flying stars"},"getAvastha":{"fields":[{"description":"Avastha slug. Baladi: bala, kumara, yuva, vriddha, mrita. Jagradadi: jagrat, swapna, sushupti. Deeptadi: dipta, svastha, pramudita, shanta, dina, duhkhita, vikala, khala, kopa.","enum":["bala","kumara","yuva","vriddha","mrita","jagrat","swapna","sushupti","dipta","svastha","pramudita","shanta","dina","duhkhita","vikala","khala","kopa"],"example":"dipta","inQuery":false,"key":"id","kind":"select","label":"Avastha","name":"id","required":true}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":false,"path":"/vedic-astrology/avasthas/{id}","title":"Get avastha by ID"},"getAztecDaySign":{"fields":[{"description":"Day sign id, case-insensitive and punctuation-insensitive. One of cipactli, ehecatl, calli, cuetzpalin, coatl, miquiztli, mazatl, tochtli, atl, itzcuintli, ozomahtli, malinalli, acatl, ocelotl, cuauhtli, cozcacuauhtli, ollin, tecpatl, quiahuitl, xochitl.","enum":["cipactli","ehecatl","calli","cuetzpalin","coatl","miquiztli","mazatl","tochtli","atl","itzcuintli","ozomahtli","malinalli","acatl","ocelotl","cuauhtli","cozcacuauhtli","ollin","tecpatl","quiahuitl","xochitl"],"example":"cipactli","inQuery":false,"key":"id","kind":"select","label":"Day sign","name":"id","required":true}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":false,"path":"/mesoamerican-astrology/aztec/day-signs/{id}","title":"Get one Aztec day sign"},"getAztecTrecena":{"fields":[{"description":"Trecena number, 1 to 20. Trecena 1 opens on 1 Cipactli, trecena 2 on 1 Ocelotl, and each subsequent period opens thirteen signs further round the twenty.","example":1,"inQuery":false,"key":"number","kind":"number","name":"number","required":true}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":false,"path":"/mesoamerican-astrology/aztec/trecenas/{number}","title":"Get one Aztec trecena"},"getBaguaSector":{"fields":[{"description":"Life area id. One of career, knowledge, family, wealth, fame, love, children, helpful-people, health.","enum":["career","knowledge","family","wealth","fame","love","children","helpful-people","health"],"example":"wealth","inQuery":false,"key":"id","kind":"tiles","label":"Life area","name":"id","required":true}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":false,"path":"/feng-shui/bagua/{id}","title":"Look up a Bagua sector"},"getBasicPanchang":{"fields":[{"description":"Date in YYYY-MM-DD format. Panchang elements (Tithi, Nakshatra, Yoga, Karana) are calculated for this date.","example":"2025-12-17","key":"date","kind":"date","name":"date","required":true},{"description":"Time in HH:MM:SS format (24-hour). Determines the exact Moon and Sun positions for tithi and nakshatra calculation.","example":"12:00:00","key":"time","kind":"time","name":"time","required":true},{"description":"Observer latitude in decimal degrees. Determines sunrise/sunset times which define the Vara (weekday) and muhurta boundaries.","example":28.6139,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Observer longitude in decimal degrees. Affects local time calculations for sunrise/sunset-dependent panchang elements.","example":77.209,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"default":5.5,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time. Defaults to 5.5 (IST).","example":5.5,"key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"role":"location"}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/vedic-astrology/panchang/basic","title":"Get basic Panchang"},"getBirthstones":{"fields":[{"description":"Birth month as a number from 1 (January) to 12 (December).","example":2,"inQuery":false,"key":"month","kind":"number","max":12,"min":1,"name":"month","required":true}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":false,"path":"/crystals/birthstone/{month}","title":"Birthstones by month"},"getCard":{"fields":[{"description":"Card identifier. Major arcana: \"fool\", \"magician\", \"death\". Minor arcana: \"ace-of-cups\", \"seven-of-wands\", \"queen-of-swords\", \"king-of-pentacles\". Casing and separators are flexible, so \"Fool\" and \"ACE_OF_CUPS\" both resolve, and a leading definite article is optional, so \"the-star\" resolves to \"star\". The canonical form, and the one every response echoes, is kebab-case with no article.","example":"fool","inQuery":false,"key":"id","kind":"text","name":"id","required":true,"source":{"lang":true,"limit":100,"path":"/tarot/cards"}}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":false,"path":"/tarot/cards/{id}","title":"Get tarot card by id"},"getCenter":{"fields":[{"description":"Center id. One of head, ajna, throat, g, heart, sacral, solar-plexus, spleen, root.","enum":["head","ajna","throat","g","heart","sacral","solar-plexus","spleen","root"],"example":"sacral","inQuery":false,"key":"id","kind":"tiles","label":"Center","name":"id","required":true}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":false,"path":"/human-design/centers/{id}","title":"Look up a Human Design center by id"},"getChoghadiya":{"fields":[{"description":"Date in YYYY-MM-DD format. A single-digit month or day is accepted and zero-padded (2026-3-5 becomes 2026-03-05). Impossible calendar dates are rejected. Calculations that read planetary positions support 1550-01-02 to 2650-01-22; outside that span they answer 400 with code date_out_of_range, and a calculation that reads a window around the date (a sunrise search, a run of days) may answer the same 400 for a date within a few days of either end.","example":"2026-02-03","key":"date","kind":"date","name":"date","required":true},{"description":"Observer latitude in decimal degrees. Determines sunrise and sunset times which define day/night boundaries for muhurta calculations.","example":17.385044,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Observer longitude in decimal degrees. Affects local time calculations for sunrise, sunset, and muhurta period boundaries.","example":78.486671,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"default":5.5,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time. Used for accurate sunrise/sunset calculation and output time formatting. Essential for correct Choghadiya periods outside IST. Defaults to 5.5 (IST).","example":5.5,"key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"role":"location"}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":false,"method":"POST","opensOnLoad":false,"path":"/vedic-astrology/panchang/choghadiya","title":"Get Choghadiya"},"getCitiesByCountry":{"fields":[{"description":"ISO 3166-1 alpha-2 country code, case-insensitive. Common codes: DE (Germany), FR (France), GB (United Kingdom), US (United States), ES (Spain), IT (Italy), NL (Netherlands), IN (India), BR (Brazil), JP (Japan).","example":"DE","inQuery":false,"key":"iso2","kind":"text","name":"iso2","required":true},{"default":20,"description":"Maximum items to return per page. Range: 1-100, default 20.","example":20,"inQuery":true,"key":"limit","kind":"number","max":100,"min":1,"name":"limit","required":false,"role":"hidden-default"},{"default":0,"description":"Number of items to skip for pagination. Default 0.","example":0,"inQuery":true,"key":"offset","kind":"number","min":0,"name":"offset","required":false,"role":"hidden-default"}],"groups":[{}],"hasLang":false,"method":"GET","opensOnLoad":false,"path":"/location/countries/{iso2}","title":"Get cities in a country"},"getCompoundNumber":{"fields":[{"description":"Compound number from 10 to 52.","example":"23","inQuery":false,"key":"number","kind":"text","name":"number","required":true}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":false,"path":"/numerology/compound-number/{number}","title":"Get compound number meaning"},"getCriticalDays":{"fields":[{"description":"Birth date of the person in YYYY-MM-DD format.","example":"1990-07-15","key":"birthDate","kind":"date","name":"birthDate","required":true},{"description":"Start date of the search range in YYYY-MM-DD format. Defaults to today (UTC).","example":"2026-04-01","fold":true,"key":"startDate","kind":"date","name":"startDate","required":false},{"description":"End date of the search range in YYYY-MM-DD format. Defaults to startDate + 90 days. Maximum range: 180 days.","example":"2026-06-30","fold":true,"key":"endDate","kind":"date","name":"endDate","required":false}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/biorhythm/critical-days","title":"Find critical days"},"getCrystal":{"fields":[{"description":"URL-safe crystal identifier, case-insensitive (e.g., \"amethyst\", \"Amethyst\", \"rose-quartz\" all resolve). Must match an entry in the database.","example":"amethyst","inQuery":false,"key":"id","kind":"text","name":"id","required":true,"source":{"lang":true,"limit":100,"path":"/crystals"}}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":false,"path":"/crystals/{id}","title":"Get crystal by id"},"getCrystalPairings":{"fields":[{"description":"URL-safe crystal identifier to find pairings for, case-insensitive (e.g., \"amethyst\", \"Amethyst\", \"rose-quartz\" all resolve).","example":"amethyst","inQuery":false,"key":"id","kind":"text","name":"id","required":true}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":false,"path":"/crystals/pairings/{id}","title":"Crystal pairings"},"getCrystalsByChakra":{"fields":[{"description":"Chakra name, case-insensitive (e.g., heart, Heart, HEART all work). Valid: Root, Sacral, Solar Plexus, Heart, Throat, Third Eye, Crown.","enum":["Root","Sacral","Solar Plexus","Heart","Throat","Third Eye","Crown"],"example":"Heart","inQuery":false,"key":"chakra","kind":"tiles","name":"chakra","required":true},{"default":20,"description":"Maximum items to return per page. Range: 1-30, default 20.","example":20,"inQuery":true,"key":"limit","kind":"number","max":30,"min":1,"name":"limit","required":false,"role":"hidden-default"},{"default":0,"description":"Number of items to skip for pagination. Default 0.","example":0,"inQuery":true,"key":"offset","kind":"number","min":0,"name":"offset","required":false,"role":"hidden-default"}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":false,"path":"/crystals/chakra/{chakra}","title":"Crystals by chakra"},"getCrystalsByElement":{"fields":[{"description":"Element name, case-insensitive (e.g., water, Water, WATER all work). Valid: Earth, Water, Fire, Air, Storm.","enum":["Earth","Water","Fire","Air","Storm"],"example":"Water","inQuery":false,"key":"element","kind":"tiles","name":"element","required":true},{"default":20,"description":"Maximum items to return per page. Range: 1-30, default 20.","example":20,"inQuery":true,"key":"limit","kind":"number","max":30,"min":1,"name":"limit","required":false,"role":"hidden-default"},{"default":0,"description":"Number of items to skip for pagination. Default 0.","example":0,"inQuery":true,"key":"offset","kind":"number","min":0,"name":"offset","required":false,"role":"hidden-default"}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":false,"path":"/crystals/element/{element}","title":"Crystals by element"},"getCrystalsByZodiac":{"fields":[{"description":"Zodiac sign name, case-insensitive (e.g., pisces, Pisces, PISCES all work). Valid: aries, taurus, gemini, cancer, leo, virgo, libra, scorpio, sagittarius, capricorn, aquarius, pisces.","enum":["aries","taurus","gemini","cancer","leo","virgo","libra","scorpio","sagittarius","capricorn","aquarius","pisces"],"example":"pisces","inQuery":false,"key":"sign","kind":"tiles","name":"sign","required":true},{"default":20,"description":"Maximum items to return per page. Range: 1-30, default 20.","example":20,"inQuery":true,"key":"limit","kind":"number","max":30,"min":1,"name":"limit","required":false,"role":"hidden-default"},{"default":0,"description":"Number of items to skip for pagination. Default 0.","example":0,"inQuery":true,"key":"offset","kind":"number","min":0,"name":"offset","required":false,"role":"hidden-default"}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":false,"path":"/crystals/zodiac/{sign}","title":"Crystals by zodiac sign"},"getCurrentDasha":{"fields":[{"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04","key":"date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00","key":"time","kind":"time","name":"time","required":true},{"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","example":28.6139,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","example":77.209,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"default":5.5,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time. Defaults to 5.5.","example":5.5,"key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"role":"location"},{"default":"lahiri","description":"Ayanamsa system used to place the birth Moon in its nakshatra, which sets every dasha start and end date. \"lahiri\" uses Lahiri/Chitrapaksha, the traditional Vedic standard, and is the default. \"kp-newcomb\" uses the KP-Newcomb dynamic formula, matching Krishnamurti Paddhati software. \"kp-old\" uses the Krishnamurti original table from KP Reader-1. \"raman\" uses the B.V. Raman ayanamsa, the second frame traditional Indian software commonly offers beside Lahiri. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. Switching frames shifts every dasha boundary by weeks, so pick the one your reference software uses.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"example":"lahiri","fold":true,"key":"ayanamsa","kind":"tiles","name":"ayanamsa","required":false},{"description":"Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.","example":24,"fold":true,"key":"ayanamsaValue","kind":"number","name":"ayanamsaValue","required":false},{"default":false,"description":"Set true to attach the KP significators of each period lord: its star lord, sub lord, occupied house, the houses it signifies at levels L1 to L4, and a strength grade. Off by default, so responses stay exactly as they are for clients that only need dates. Requires the birth latitude and longitude, since significators are read off a Placidus house chart, and uses the same ayanamsa frame selected above.","example":false,"fold":true,"key":"significators","kind":"toggle","name":"significators","required":false},{"default":"mean","description":"Lunar node type for Rahu and Ketu, used ONLY when \"significators\" is true. Dasha dates themselves come from the Moon and never move with this field. \"mean\" uses the smooth mean node (traditional default). \"true\" uses the osculating node, which swings up to 1.5 degrees either side of mean over a 173-day cycle and can therefore change which house or star a node falls in. Defaults to \"mean\".","enum":["mean","true"],"example":"mean","fold":true,"key":"nodeType","kind":"tiles","name":"nodeType","required":false},{"description":"ISO 8601 datetime (YYYY-MM-DDTHH:MM:SS) to read the running periods at, for a reading prepared for a future day, a backtest, or a chart cast for a past moment. Defaults to the current instant. Interpreted as local time in the request timezone (a trailing Z is accepted but ignored); with timezone 0 it is UTC.","example":"2026-08-23T13:47:46Z","fold":true,"key":"datetime","kind":"datetime","name":"datetime","required":false},{"default":"general","description":"Which signification vocabulary the houseThemes map returns. \"general\" gives the classical bhava significations (self, wealth, siblings, home, and so on). \"finance\" gives the money reading of the same twelve bhavas, so house 2 returns income and savings, 5 speculation and risk appetite, 8 sudden money and leverage, 11 gains and profits, and 12 expenses and capital outflow. Use \"finance\" for wealth, income, business and market timing questions in Krishnamurti Paddhati, where the significator house groups 2, 6, 10, 11 for earned income and 5, 8, 11 for speculation are read against a running dasha. Defaults to \"general\".","enum":["general","finance"],"example":"general","fold":true,"inQuery":true,"key":"focus","kind":"tiles","name":"focus","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/vedic-astrology/dasha/current","title":"Get current Mahadasha, Antardasha, Pratyantardasha, Sookshma, Prana"},"getCurrentMoonPhase":{"fields":[{"description":"Date in YYYY-MM-DD format. Defaults to today if omitted.","example":"2025-12-18","inQuery":true,"key":"date","kind":"date","name":"date","required":false},{"description":"Time in 24-hour HH:MM:SS format. Defaults to 12:00:00 (noon). Moon moves ~13 degrees per day so time affects phase precision.","example":"12:00:00","inQuery":true,"key":"time","kind":"time","name":"time","required":false},{"city":true,"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\"). IANA resolved to the DST-correct offset for the given date. With `date` omitted, today is the date in this zone. Defaults to 0 (UTC).","example":"America/New_York","inQuery":true,"key":"timezone","kind":"text","name":"timezone","required":false,"viewerZone":true}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":true,"path":"/astrology/moon-phase/current","title":"Get current moon phase"},"getDailyAngelNumber":{"fields":[{"description":"Optional seed for reproducible readings. Same seed + same date = same angel number every time. Pass any unique identifier (userId, email hash, session token) to give each user their own angel number for the day. Without a seed every caller receives the same shared angel number of the day.","example":"user123","key":"seed","kind":"text","name":"seed","required":false,"role":"seed"},{"description":"Date for the reading in YYYY-MM-DD format. Defaults to today (UTC). Useful for viewing past daily readings or pre-generating future ones.","example":"2026-03-06","key":"date","kind":"date","name":"date","required":false}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/angel-numbers/daily","title":"Daily angel number"},"getDailyAyurvedaReading":{"fields":[{"description":"Reading date in YYYY-MM-DD format. Past and future dates are both supported, for editorial scheduling and backfill. Defaults to the current day in the timezone parameter.","example":"2026-06-21","fold":true,"inQuery":true,"key":"date","kind":"date","name":"date","required":false},{"description":"Latitude in decimal degrees. It sets how long the day and the night actually are, which is what the dosha periods are cut from.","example":51.5074,"inQuery":true,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Longitude in decimal degrees. It sets the clock time of sunrise at this place.","example":-0.1278,"inQuery":true,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"description":"Selects which day counts as current when date is omitted, and which local day sunrise is computed for. Defaults to UTC, so the reading rolls over at 00:00 UTC. Accepts an IANA name (e.g. \"Europe/London\"), decimal hours (e.g. 5.5 for IST), or a fixed UTC offset (e.g. \"-05:00\").","example":"Europe/London","inQuery":true,"key":"timezone","kind":"text","name":"timezone","required":false,"role":"location"}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"GET","opensOnLoad":false,"path":"/ayurveda/daily","title":"Daily Ayurveda reading"},"getDailyAztecReading":{"fields":[{"description":"Date in YYYY-MM-DD format, in the PROLEPTIC GREGORIAN calendar, extended backwards unchanged through the 1582 reform. Years 1 to 4000 are accepted. A reference converter that switches to the Julian calendar below the reform will disagree with a date before 15 October 1582 by ten or eleven days; that is a difference of input convention rather than of arithmetic, and passing the Julian equivalent to such a tool reproduces these values exactly. A single-digit month or day is accepted and zero padded. Defaults to the current day in UTC.","example":"2026-09-02","inQuery":true,"key":"date","kind":"date","name":"date","required":false}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":true,"path":"/mesoamerican-astrology/aztec/daily","title":"Daily Aztec energy reading"},"getDailyBiorhythm":{"fields":[{"description":"Optional seed for reproducible readings. Same seed + same date = same reading every time. Pass any unique identifier (userId, email hash, session token) to give each user their own reading for the day. Without a seed every caller receives the same shared reading of the day.","example":"user123","key":"seed","kind":"text","name":"seed","required":false,"role":"seed"},{"description":"Date for the reading in YYYY-MM-DD format. Defaults to today (UTC). Useful for viewing past daily readings or pre-generating future ones.","example":"2026-03-06","key":"date","kind":"date","name":"date","required":false}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/biorhythm/daily","title":"Get daily biorhythm"},"getDailyCard":{"fields":[{"description":"Optional seed for reproducible readings. Same seed + same date = same card every time. Pass any unique identifier (userId, email hash, session token) to give each user their own card for the day. Without a seed every caller receives the same shared card of the day.","example":"user123","key":"seed","kind":"text","name":"seed","required":false,"role":"seed"},{"description":"Date for the reading in YYYY-MM-DD format. Defaults to today (UTC). Useful for viewing past daily readings or pre-generating future ones.","example":"2026-03-06","key":"date","kind":"date","name":"date","required":false}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/tarot/daily","title":"Daily tarot card"},"getDailyCrystal":{"fields":[{"description":"Optional seed for reproducible readings. Same seed + same date = same crystal every time. Pass any unique identifier (userId, email hash, session token) to give each user their own crystal for the day. Without a seed every caller receives the same shared crystal of the day.","example":"user123","key":"seed","kind":"text","name":"seed","required":false,"role":"seed"},{"description":"Date for the reading in YYYY-MM-DD format. Defaults to today (UTC). Useful for viewing past daily readings or pre-generating future ones.","example":"2026-03-06","key":"date","kind":"date","name":"date","required":false}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/crystals/daily","title":"Daily crystal"},"getDailyDreamSymbol":{"fields":[{"description":"Optional seed for reproducible readings. Same seed + same date = same symbol every time. Pass any unique identifier (userId, email hash, session token) to give each user their own symbol for the day. Without a seed every caller receives the same shared symbol of the day.","example":"user123","key":"seed","kind":"text","name":"seed","required":false,"role":"seed"},{"description":"Date for the reading in YYYY-MM-DD format. Defaults to today (UTC). Useful for viewing past daily readings or pre-generating future ones.","example":"2026-03-06","key":"date","kind":"date","name":"date","required":false}],"groups":[{}],"hasLang":false,"method":"POST","opensOnLoad":false,"path":"/dreams/daily","title":"Daily dream symbol"},"getDailyHexagram":{"fields":[{"description":"Optional seed for reproducible readings. Same seed + same date = same hexagram every time. Pass any unique identifier (userId, email hash, session token) to give each user their own hexagram for the day. Without a seed every caller receives the same shared hexagram of the day.","example":"user123","key":"seed","kind":"text","name":"seed","required":false,"role":"seed"},{"description":"Date for the reading in YYYY-MM-DD format. Defaults to today (UTC). Useful for viewing past daily readings or pre-generating future ones.","example":"2026-03-06","key":"date","kind":"date","name":"date","required":false}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/iching/daily","title":"Daily hexagram"},"getDailyHoroscope":{"fields":[{"description":"Zodiac sign, case-insensitive (e.g., aries, Aries, ARIES all work).","enum":["aries","taurus","gemini","cancer","leo","virgo","libra","scorpio","sagittarius","capricorn","aquarius","pisces"],"example":"aries","inQuery":false,"key":"sign","kind":"tiles","name":"sign","required":true},{"description":"Forecast date in YYYY-MM-DD format. Past and future dates are both supported, for editorial scheduling and backfill. Defaults to the current period in the timezone parameter.","example":"2026-04-03","fold":true,"inQuery":true,"key":"date","kind":"date","name":"date","required":false},{"city":true,"description":"Selects which period counts as current when date is omitted. Defaults to UTC, so the forecast rolls over at 00:00 UTC on each day. Pass the timezone of the end user to roll over on their local clock instead. Ignored when date is set. Accepts an IANA name (e.g. \"America/New_York\"), decimal hours (e.g. 5.5 for IST), or a fixed UTC offset (e.g. \"-05:00\").","example":"America/New_York","fold":true,"inQuery":true,"key":"timezone","kind":"text","name":"timezone","required":false,"viewerZone":true}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":false,"path":"/astrology/horoscope/{sign}/daily","title":"Daily horoscope by zodiac sign"},"getDailyMayanReading":{"fields":[{"description":"Date in YYYY-MM-DD format, in the PROLEPTIC GREGORIAN calendar, extended backwards unchanged through the 1582 reform. Years 1 to 4000 are accepted. A reference converter that switches to the Julian calendar below the reform will disagree with a date before 15 October 1582 by ten or eleven days; that is a difference of input convention rather than of arithmetic, and passing the Julian equivalent to such a tool reproduces these values exactly. A single-digit month or day is accepted and zero padded. Defaults to the current day in UTC.","example":"2026-09-02","inQuery":true,"key":"date","kind":"date","name":"date","required":false},{"default":"gmt-584283","description":"Which correlation constant ties the day count to a civil date. This is the single choice that shifts every value in the response, so it is a parameter rather than a hidden default, and the resolved value comes back under conventions. \"gmt-584283\" is the commonly accepted constant and the default, and it is the one the major institutional converter runs on. \"martinez-hernandez-584281\" sits two days earlier, \"astronomical-584285\" two days later, and \"martin-skidmore-584286\" three days later, each shifting the Long Count by exactly its difference in days. Four of the eight published constants are offered: the other four sit tens of thousands of days away and are of historical interest only. The 584281 constant is the Martínez Hernández correlation, after Juan Martínez Hernández.","enum":["gmt-584283","martinez-hernandez-584281","astronomical-584285","martin-skidmore-584286"],"example":"gmt-584283","fold":true,"inQuery":true,"key":"correlation","kind":"tiles","name":"correlation","required":false}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":true,"path":"/mesoamerican-astrology/mayan/daily","title":"Daily Mayan energy reading"},"getDailyNumber":{"fields":[{"description":"Optional seed for reproducible readings. Same seed + same date = same number every time. Pass any unique identifier (userId, email hash, session token) to give each user their own number for the day. Without a seed every caller receives the same shared number of the day.","example":"user123","key":"seed","kind":"text","name":"seed","required":false,"role":"seed"},{"description":"Date for the reading in YYYY-MM-DD format. Defaults to today (UTC). Useful for viewing past daily readings or pre-generating future ones.","example":"2026-03-06","key":"date","kind":"date","name":"date","required":false}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/numerology/daily","title":"Get daily numerology number"},"getDailySephirah":{"fields":[{"description":"Date in YYYY-MM-DD. Defaults to the current UTC date when omitted, so a caller that wants a fixed answer should send one.","example":"2026-04-04","inQuery":true,"key":"date","kind":"date","name":"date","required":false},{"city":true,"description":"IANA name or decimal offset, used only to decide which calendar date it is where the caller is when date is omitted. It does not move the count, which is a calendar count rather than a clock one.","example":"Asia/Jerusalem","inQuery":true,"key":"timezone","kind":"text","name":"timezone","required":false,"viewerZone":true},{"description":"Set true when the moment falls after nightfall, which advances the Hebrew date by one day because the Hebrew day begins in the evening. It is a caller assertion rather than a computation, since sunset depends on a place and this route takes none.","example":"false","inQuery":true,"key":"afterSunset","kind":"text","name":"afterSunset","required":false}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":true,"path":"/kabbalah/daily","title":"Get the sephirah of the day"},"getDailyZodiacReading":{"fields":[{"description":"Animal id, case-insensitive. One of rat, ox, tiger, rabbit, dragon, snake, horse, goat, monkey, rooster, dog, pig.","enum":["rat","ox","tiger","rabbit","dragon","snake","horse","goat","monkey","rooster","dog","pig"],"example":"rat","inQuery":false,"key":"id","kind":"tiles","label":"Animal","name":"id","required":true},{"description":"Reading date in YYYY-MM-DD format. Past and future dates are both supported, for editorial scheduling and backfill. Defaults to the current day in the timezone parameter.","example":"2026-04-03","fold":true,"inQuery":true,"key":"date","kind":"date","name":"date","required":false},{"city":true,"description":"Selects which day counts as current when date is omitted. Defaults to UTC, so the reading rolls over at 00:00 UTC each day. Pass the timezone of the end user to roll over on their local clock instead. Ignored when date is set. Accepts an IANA name (e.g. \"America/New_York\"), decimal hours (e.g. 5.5 for IST), or a fixed UTC offset (e.g. \"-05:00\").","example":"America/New_York","fold":true,"inQuery":true,"key":"timezone","kind":"text","name":"timezone","required":false,"viewerZone":true}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":false,"path":"/chinese-astrology/zodiac/{id}/daily","title":"Daily Chinese zodiac reading"},"getDetailedPanchang":{"fields":[{"description":"Date in YYYY-MM-DD format. A single-digit month or day is accepted and zero-padded (2026-3-5 becomes 2026-03-05). Impossible calendar dates are rejected. Calculations that read planetary positions support 1550-01-02 to 2650-01-22; outside that span they answer 400 with code date_out_of_range, and a calculation that reads a window around the date (a sunrise search, a run of days) may answer the same 400 for a date within a few days of either end.","example":"2026-02-03","key":"date","kind":"date","name":"date","required":true},{"description":"Observer latitude in decimal degrees. Determines sunrise and sunset times which define day/night boundaries for muhurta calculations.","example":28.6139,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Observer longitude in decimal degrees. Affects local time calculations for sunrise, sunset, and muhurta period boundaries.","example":77.209,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"default":5.5,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time. Send the timezone that matches the coordinates: sunrise, sunset and every muhurta boundary are found by searching forward from local midnight, so the default anchors the search to an Indian day. Omitting it for a location outside IST returns a correctly ordered set of periods for the wrong window, shifted by the difference between 5.5 and the real offset. Defaults to 5.5 (IST).","example":5.5,"key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"role":"location"}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/vedic-astrology/panchang/detailed","title":"Get detailed Panchang with Rahu Kaal, Yamaganda, Gulika"},"getDevata":{"fields":[{"description":"Devata id, lower case transliteration. The two Indras are indra-outer for the east perimeter square and indra-inner for the inner ring one. Case and punctuation are folded.","enum":["agni","parjanya","jayanta","indra-outer","surya","satya","bhrisa","antariksha","vayu","pusha","vitatha","brihatkshata","yama","gandharva","bhringaraja","mriga","pitri","dauvarika","sugriva","kusumadanta","varuna","asura","sosha","papayakshma","roga","ahi","mukhya","bhallata","soma","bhujaga","aditi","diti","aryaman","savita","vivasvan","indra-inner","mitra","rajayakshma","prthvidhara","apavatsa","apa","savitra","jaya","rudra","brahma"],"example":"jayanta","inQuery":false,"key":"id","kind":"select","label":"Devata","name":"id","required":true}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":false,"path":"/vastu/devatas/{id}","title":"Look up one devata"},"getDikpalaDirection":{"fields":[{"description":"Direction id, one of North, Northeast, East, Southeast, South, Southwest, West, Northwest. Case and punctuation are folded.","enum":["North","Northeast","East","Southeast","South","Southwest","West","Northwest"],"example":"Northeast","inQuery":false,"key":"id","kind":"tiles","label":"Direction","name":"id","required":true}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":false,"path":"/vastu/directions/{id}","title":"Look up one direction"},"getDinacharyaSchedule":{"fields":[{"description":"The local calendar date, in YYYY-MM-DD format. Sunrise and sunset are computed for this date at the given place, and the whole routine follows from them, so the answer changes through the year at any latitude away from the equator.","example":"2026-06-21","key":"date","kind":"date","name":"date","required":true},{"description":"Latitude in decimal degrees. It sets how long the day and the night actually are, which is the whole difference between this and a printed timetable: at 51 north in June the day runs about sixteen and a half hours and its thirds are five and a half hours each.","example":51.5074,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Longitude in decimal degrees. It sets the clock time of sunrise at this place.","example":-0.1278,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"default":0,"description":"Timezone as an IANA name such as \"Europe/London\", or as decimal hours from UTC such as 5.5. An IANA name is resolved to the offset in force on the requested date, and on the clock-hour grid at the local hour each block opens, so on a daylight-saving change every block keeps its printed hour and one that falls in the skipped hour moves forward past it. It decides which local day is meant and, on the clock-hour grid, where the blocks fall. Defaults to 0.","example":"Europe/London","key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"role":"location"},{"default":"sunrise-anchored","description":"How the six dosha periods are cut. \"sunrise-anchored\" divides the actual day and the actual night at this place into thirds, which is the division the frame chapter states, and is the default. \"clock-hours\" is the modern grid of six four-hour blocks from six in the morning; no classical text assigns clock hours, and the grid is only exact at an equinox near the equator. Both sets are returned whichever is chosen, so a caller can show one and reconcile against the other.","enum":["sunrise-anchored","clock-hours"],"example":"sunrise-anchored","fold":true,"key":"doshaClock","kind":"tiles","name":"doshaClock","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/ayurveda/dinacharya","title":"Dinacharya daily routine"},"getDosha":{"fields":[{"description":"Dosha identifier, case-insensitive. One of vata, pitta or kapha.","enum":["vata","pitta","kapha"],"example":"vata","inQuery":false,"key":"id","kind":"tiles","label":"Dosha","name":"id","required":true}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":false,"path":"/ayurveda/doshas/{id}","title":"Get one dosha"},"getDreamSymbol":{"fields":[{"description":"Unique symbol identifier in kebab-case (e.g., \"snake\", \"chase-dreams\", \"losing-teeth\").","example":"snake","inQuery":false,"key":"id","kind":"text","name":"id","required":true,"source":{"limit":50,"path":"/dreams/symbols","search":"q"}}],"groups":[{}],"hasLang":false,"method":"GET","opensOnLoad":false,"path":"/dreams/symbols/{id}","title":"Get dream symbol by id"},"getEclipticCrossings":{"fields":[{"description":"Year to scan for ecliptic crossings (1551 to 2649).","example":2026,"key":"year","kind":"number","max":2649,"min":1551,"name":"year","required":true},{"city":true,"default":0,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved once, at the start of the window, and that offset applies to every time in the response. Output times are converted to this timezone. Defaults to 0 (UTC).","example":5.5,"fold":true,"key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"viewerZone":true},{"default":"sidereal","description":"Coordinate system for longitude output. \"sidereal\" (Nirayana) uses Lahiri ayanamsa, the standard for Vedic astrology. \"tropical\" (Sayana) uses raw ecliptic longitude matching Western astrology. Defaults to \"sidereal\".","enum":["sidereal","tropical"],"example":"sidereal","fold":true,"key":"coordinateSystem","kind":"tiles","name":"coordinateSystem","required":false}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/vedic-astrology/ecliptic-crossings","title":"Ecliptic Crossings"},"getFieldLabels":{"fields":[],"groups":[],"hasLang":true,"method":"GET","opensOnLoad":true,"path":"/languages/field-labels","title":"Get field labels for a language"},"getForecast":{"fields":[{"description":"Birth date of the person in YYYY-MM-DD format.","example":"1990-07-15","key":"birthDate","kind":"date","name":"birthDate","required":true},{"description":"Start date of the forecast range in YYYY-MM-DD format. Defaults to today (UTC).","example":"2026-04-01","fold":true,"key":"startDate","kind":"date","name":"startDate","required":false},{"description":"End date of the forecast range in YYYY-MM-DD format. Defaults to startDate + 30 days. Maximum range: 90 days.","example":"2026-04-30","fold":true,"key":"endDate","kind":"date","name":"endDate","required":false}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/biorhythm/forecast","title":"Get biorhythm forecast"},"getGate":{"fields":[{"description":"Gate number from 1 to 64.","example":34,"inQuery":false,"key":"number","kind":"number","max":64,"min":1,"name":"number","required":true}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":false,"path":"/human-design/gates/{number}","title":"Look up a Human Design gate by number"},"getHaabMonth":{"fields":[{"description":"Haab period id, case-insensitive and punctuation-insensitive. One of pop, wo, sip, sotz, sek, xul, yaxkin, mol, chen, yax, sak, keh, mak, kankin, muwan, pax, kayab, kumku, wayeb.","enum":["pop","wo","sip","sotz","sek","xul","yaxkin","mol","chen","yax","sak","keh","mak","kankin","muwan","pax","kayab","kumku","wayeb"],"example":"pop","inQuery":false,"key":"id","kind":"select","label":"Haab period","name":"id","required":true}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":false,"path":"/mesoamerican-astrology/mayan/haab-months/{id}","title":"Get one Haab period"},"getHebrewLetter":{"fields":[{"description":"Letter identifier, one of alef, bet, gimel, dalet, he, vav, zayin, chet, tet, yod, kaf, lamed, mem, nun, samekh, ayin, pe, tzadi, qof, resh, shin, tav. Matching folds case and punctuation.","enum":["alef","bet","gimel","dalet","he","vav","zayin","chet","tet","yod","kaf","lamed","mem","nun","samekh","ayin","pe","tzadi","qof","resh","shin","tav"],"example":"shin","inQuery":false,"key":"id","kind":"select","label":"Letter","name":"id","required":true},{"default":"sefer-yetzirah-gra","description":"Which reading assigns the element, planet or sign to each letter. The seven double letters are the contested column and the four readings genuinely disagree on them; the twelve simple letters run in natural zodiacal order in all four. The golden-dawn member does NOT exchange He and Tzade, which is a later change from a different author.","enum":["sefer-yetzirah-gra","sefer-yetzirah-short","sefer-yetzirah-saadia","golden-dawn"],"example":"sefer-yetzirah-gra","fold":true,"inQuery":true,"key":"letterAttribution","kind":"tiles","name":"letterAttribution","required":false}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":false,"path":"/kabbalah/letters/{id}","title":"Get one Hebrew letter"},"getHeliacalVisibility":{"fields":[{"description":"Local calendar date to judge, in YYYY-MM-DD format. There is deliberately no time field: heliacal visibility is a once-a-day verdict read at that day sunrise or sunset, so a clock time could only pick a different day.","example":"2026-07-25","key":"date","kind":"date","name":"date","required":true},{"description":"Observer latitude in decimal degrees, restricted to -60 to 60. Visibility depends on the observer, unlike the longitude orb every chart API reports, because the angle the ecliptic makes with the horizon decides how long a graha lingers after the Sun. Beyond this band the classical rule stops describing solar glare and starts describing polar horizon geometry, so it is declined rather than answered wrongly.","example":19.076,"key":"latitude","kind":"number","max":60,"min":-60,"name":"latitude","required":true,"role":"location"},{"description":"Observer longitude in decimal degrees. Sets local sunrise and sunset, which are the instants the verdict is read at. Example: Mumbai 72.8777, Delhi 77.2090, London -0.1278.","example":72.8777,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"default":5.5,"description":"Timezone: IANA name (e.g. \"Asia/Kolkata\", \"Europe/London\") OR decimal hours from UTC. Fixes which local day the date refers to, and every datetime in the response is returned in it. Defaults to 5.5.","example":5.5,"key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"role":"location"}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":false,"method":"POST","opensOnLoad":false,"path":"/vedic-astrology/heliacal","title":"Heliacal rising and setting (udaya and asta)"},"getHexagram":{"fields":[{"description":"Hexagram number in King Wen sequence (1-64).","example":1,"inQuery":false,"key":"number","kind":"number","max":64,"min":1,"name":"number","required":true}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":false,"path":"/iching/hexagrams/{number}","title":"Get hexagram by number"},"getHora":{"fields":[{"description":"Date in YYYY-MM-DD format. A single-digit month or day is accepted and zero-padded (2026-3-5 becomes 2026-03-05). Impossible calendar dates are rejected. Calculations that read planetary positions support 1550-01-02 to 2650-01-22; outside that span they answer 400 with code date_out_of_range, and a calculation that reads a window around the date (a sunrise search, a run of days) may answer the same 400 for a date within a few days of either end.","example":"2026-02-03","key":"date","kind":"date","name":"date","required":true},{"description":"Observer latitude in decimal degrees. Determines sunrise and sunset times which define day/night boundaries for muhurta calculations.","example":17.385044,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Observer longitude in decimal degrees. Affects local time calculations for sunrise, sunset, and muhurta period boundaries.","example":78.486671,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"default":5.5,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time. Used for accurate sunrise/sunset calculation and output time formatting. Essential for correct Hora periods outside IST. Defaults to 5.5 (IST).","example":5.5,"key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"role":"location"}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":false,"method":"POST","opensOnLoad":false,"path":"/vedic-astrology/panchang/hora","title":"Get Hora"},"getKpAyanamsa":{"fields":[{"description":"Date for ayanamsa calculation in YYYY-MM-DD format. Defaults to today if not provided. Ayanamsa changes by ~0.01 degrees per month due to the precession of Earth.","example":"2025-12-26","inQuery":true,"key":"date","kind":"date","name":"date","required":false},{"description":"Time of day in 24-hour HH:MM:SS format, interpreted in the timezone below. Omit for midnight UTC. The ayanamsa moves about 0.14 arcseconds across a day, so supplying the time matters only when reconciling a chart against reference software to the arcsecond.","example":"09:00:00","inQuery":true,"key":"time","kind":"time","name":"time","required":false},{"city":true,"description":"IANA name (e.g. \"Asia/Kolkata\", \"America/New_York\"), decimal hours (e.g. 5.5 for IST, -5 for EST), or a fixed UTC offset (e.g. \"+05:30\"). IANA resolved to the offset in force at the given date and the time field above. Defaults to 0 (UTC).","example":"Asia/Kolkata","inQuery":true,"key":"timezone","kind":"text","name":"timezone","required":false,"viewerZone":true}],"groups":[{}],"hasLang":false,"method":"GET","opensOnLoad":true,"path":"/vedic-astrology/kp/ayanamsa","title":"Get KP-Newcomb ayanamsa"},"getKpCusps":{"fields":[{"description":"Birth date in YYYY-MM-DD format","example":"1990-07-04","key":"date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format","example":"10:12:00","key":"time","kind":"time","name":"time","required":true},{"description":"Birth location latitude in decimal degrees","example":28.6139,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Birth location longitude in decimal degrees","example":77.209,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"default":5.5,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time. Defaults to 5.5 (IST) for Vedic astrology.","example":5.5,"key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"role":"location"},{"default":"kp-newcomb","description":"Ayanamsa system for sidereal conversion. \"kp-newcomb\" uses the KP-Newcomb dynamic formula (most common for KP). \"kp-old\" uses the Krishnamurti original table. \"lahiri\" uses Lahiri/Chitrapaksha ayanamsa matching most traditional Vedic software. \"raman\" uses the B.V. Raman ayanamsa, about 1.45 degrees below Lahiri. \"custom\" allows providing your own value via ayanamsaValue. Defaults to \"kp-newcomb\".","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"example":"kp-newcomb","fold":true,"key":"ayanamsa","kind":"tiles","name":"ayanamsa","required":false},{"description":"Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.","example":24,"fold":true,"key":"ayanamsaValue","kind":"number","name":"ayanamsaValue","required":false},{"default":"general","description":"Which signification vocabulary the houseThemes map returns. \"general\" gives the classical bhava significations (self, wealth, siblings, home, and so on). \"finance\" gives the money reading of the same twelve bhavas, so house 2 returns income and savings, 5 speculation and risk appetite, 8 sudden money and leverage, 11 gains and profits, and 12 expenses and capital outflow. Use \"finance\" for wealth, income, business and market timing questions in Krishnamurti Paddhati, where the significator house groups 2, 6, 10, 11 for earned income and 5, 8, 11 for speculation are read against a running dasha. Defaults to \"general\".","enum":["general","finance"],"example":"general","fold":true,"inQuery":true,"key":"focus","kind":"tiles","name":"focus","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/vedic-astrology/kp/cusps","title":"Get KP Placidus house cusps with sub-lords"},"getKpDailyFinance":{"fields":[{"description":"Birth date, YYYY-MM-DD. Fixes the Placidus cusps, the four tier significators and the Vimshottari balance every layer reads.","example":"1990-06-15","key":"birthDate","kind":"date","name":"birthDate","required":true},{"description":"Birth time, HH:MM:SS, 24 hour, local to the birth place. The cusp sub lords move about one sub every four minutes of clock time, so this is the input the whole reading is most sensitive to.","example":"07:30:00","key":"birthTime","kind":"time","name":"birthTime","required":true},{"description":"Birth latitude in decimal degrees. Sets the Placidus cusps; also the place the ruling planets and the Moon windows are read at.","example":28.6139,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Birth longitude in decimal degrees, east positive.","example":77.209,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"default":5.5,"description":"Timezone as an IANA name (Asia/Kolkata) or decimal hours from UTC. Applies to the birth time, to the reading date and time, and to every local timestamp in the response. IANA names resolve to the offset in force on the date being read.","example":5.5,"key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"role":"location"},{"description":"Civil date to read, YYYY-MM-DD in the request timezone. Defaults to today (UTC). The Moon windows cover this date from midnight to midnight.","example":"2026-09-14","fold":true,"key":"date","kind":"date","name":"date","required":false},{"description":"Reading moment on that date, HH:MM:SS local. The ruling planets and the running sookshma lord are read at this instant. Defaults to 12:00:00; pass a market open or any hour for an intraday read.","example":"12:00:00","fold":true,"key":"time","kind":"time","name":"time","required":false},{"default":"kp-newcomb","description":"Ayanamsa system for sidereal conversion. \"kp-newcomb\" uses the KP-Newcomb dynamic formula, the most common choice for KP astrology. \"kp-old\" uses the Krishnamurti original table from KP Reader-1 with constant precession rate. \"lahiri\" uses Lahiri/Chitrapaksha ayanamsa, matching most traditional Vedic software. \"raman\" uses the B.V. Raman ayanamsa from Hindu Predictive Astrology, a recognised traditional school that sits about 1.45 degrees below Lahiri. Defaults to \"kp-newcomb\".","enum":["kp-newcomb","kp-old","lahiri","raman"],"example":"kp-newcomb","fold":true,"key":"ayanamsa","kind":"tiles","name":"ayanamsa","required":false},{"default":"mean","description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the Rahu and Ketu positions. Mean is the traditional Vedic default and what printed panchangs use; the choice can move a KP sub-lord in narrow boundary cases, where a span can be as small as 0.5 degrees. Defaults to \"mean\".","enum":["mean","true"],"example":"mean","fold":true,"key":"nodeType","kind":"tiles","name":"nodeType","required":false},{"default":[2,11],"description":"Houses whose significators count as gain, 1 to 12. Defaults to the convention, 2 and 11. Override it to run your own school: the two lists may not share a house.","example":[2,11],"fold":true,"key":"gainHouses","kind":"array","name":"gainHouses","required":false},{"default":[6,8,12],"description":"Houses whose significators count as loss, 1 to 12. Defaults to the convention, 6 and 8 and 12. Override it to run your own school: the two lists may not share a house.","example":[6,8,12],"fold":true,"key":"lossHouses","kind":"array","name":"lossHouses","required":false},{"description":"Percent of the final score the cusps layer carries.","example":30,"fold":true,"group":"weights","key":"weights.cusps","kind":"number","max":100,"min":0,"name":"cusps","required":false},{"description":"Percent of the final score the dasha layer carries.","example":40,"fold":true,"group":"weights","key":"weights.dasha","kind":"number","max":100,"min":0,"name":"dasha","required":false},{"description":"Percent of the final score the rulingPlanets layer carries.","example":15,"fold":true,"group":"weights","key":"weights.rulingPlanets","kind":"number","max":100,"min":0,"name":"rulingPlanets","required":false},{"description":"Percent of the final score the moonWindows layer carries.","example":15,"fold":true,"group":"weights","key":"weights.moonWindows","kind":"number","max":100,"min":0,"name":"moonWindows","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}},{"fold":true,"key":"weights","label":"Weights"}],"hasLang":false,"method":"POST","opensOnLoad":false,"path":"/vedic-astrology/kp/daily-finance","title":"Daily finance score from four KP sub lord layers"},"getKpPlanets":{"fields":[{"description":"Birth date in YYYY-MM-DD format","example":"1990-07-04","key":"date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format","example":"10:12:00","key":"time","kind":"time","name":"time","required":true},{"description":"Birth location latitude in decimal degrees","example":28.6139,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Birth location longitude in decimal degrees","example":77.209,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"default":5.5,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time. Defaults to 5.5 (IST) for Vedic astrology.","example":5.5,"key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"role":"location"},{"default":"kp-newcomb","description":"Ayanamsa system for sidereal conversion. \"kp-newcomb\" uses the KP-Newcomb dynamic formula (most common for KP). \"kp-old\" uses the Krishnamurti original table. \"lahiri\" uses Lahiri/Chitrapaksha ayanamsa matching most traditional Vedic software. \"raman\" uses the B.V. Raman ayanamsa, about 1.45 degrees below Lahiri. \"custom\" allows providing your own value via ayanamsaValue. Defaults to \"kp-newcomb\".","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"example":"kp-newcomb","fold":true,"key":"ayanamsa","kind":"tiles","name":"ayanamsa","required":false},{"description":"Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.","example":24,"fold":true,"key":"ayanamsaValue","kind":"number","name":"ayanamsaValue","required":false},{"default":"mean","description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the Rahu and Ketu positions. Mean is the traditional Vedic default and what printed panchangs use; the choice can move a KP sub-lord in narrow boundary cases, where a span can be as small as 0.5 degrees. Defaults to \"mean\".","enum":["mean","true"],"example":"mean","fold":true,"key":"nodeType","kind":"tiles","name":"nodeType","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":false,"method":"POST","opensOnLoad":false,"path":"/vedic-astrology/kp/planets","title":"Get KP planetary positions with sub-lords"},"getKpPlanetsInterval":{"fields":[{"description":"Start datetime in ISO 8601 (YYYY-MM-DDTHH:MM:SS). Interpreted as local time when a non-zero timezone is provided (a trailing Z is accepted but ignored); with timezone 0 it is UTC.","example":"2025-01-15T00:00:00Z","key":"startDatetime","kind":"datetime","name":"startDatetime","required":true},{"description":"End datetime in ISO 8601 (YYYY-MM-DDTHH:MM:SS). Maximum 7 days from start. Interpreted as local time when a non-zero timezone is provided (a trailing Z is accepted but ignored); with timezone 0 it is UTC.","example":"2025-01-15T23:59:00Z","key":"endDatetime","kind":"datetime","name":"endDatetime","required":true},{"description":"Time between calculations in minutes. Range: 15 (quarter-hourly) to 1440 (daily).","example":60,"key":"intervalMinutes","kind":"number","max":1440,"min":15,"name":"intervalMinutes","required":true},{"description":"Observer latitude in decimal degrees (for future Lagna calculations)","example":28.6139,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Observer longitude in decimal degrees (for future Lagna calculations)","example":77.209,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"default":0,"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC. IANA resolved to the DST-correct offset for the startDatetime date. When non-zero, all datetimes are treated as local time in this timezone (Z suffix is ignored). Defaults to 0 (UTC).","example":5.5,"key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"role":"location"},{"default":"kp-newcomb","description":"Ayanamsa system for sidereal conversion. \"kp-newcomb\" uses the KP-Newcomb dynamic formula, the most common choice for KP astrology. \"kp-old\" uses the Krishnamurti original table from KP Reader-1 with constant precession rate. \"lahiri\" uses Lahiri/Chitrapaksha ayanamsa, matching most traditional Vedic software. \"raman\" uses the B.V. Raman ayanamsa from Hindu Predictive Astrology, a recognised traditional school that sits about 1.45 degrees below Lahiri. Defaults to \"kp-newcomb\".","enum":["kp-newcomb","kp-old","lahiri","raman"],"example":"kp-newcomb","fold":true,"key":"ayanamsa","kind":"tiles","name":"ayanamsa","required":false},{"default":"mean","description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the Rahu and Ketu positions. Mean is the traditional Vedic default and what printed panchangs use; the choice can move a KP sub-lord in narrow boundary cases, where a span can be as small as 0.5 degrees. Defaults to \"mean\".","enum":["mean","true"],"example":"mean","fold":true,"key":"nodeType","kind":"tiles","name":"nodeType","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":false,"method":"POST","opensOnLoad":false,"path":"/vedic-astrology/kp/planets-interval","title":"Get KP planets at time intervals"},"getKpRasiChanges":{"fields":[{"description":"Planet to track (case-insensitive). Valid values: Sun, Moon, Mars, Mercury, Jupiter, Venus, Saturn","enum":["Sun","Moon","Mars","Mercury","Jupiter","Venus","Saturn"],"example":"Sun","key":"planet","kind":"tiles","name":"planet","required":true},{"description":"First day of the search (YYYY-MM-DD), a calendar day in `timezone`.","example":"2025-01-01","key":"startDate","kind":"date","name":"startDate","required":true},{"description":"Last day of the search, inclusive (YYYY-MM-DD), a calendar day in `timezone`. Not before startDate, at most 365 days after it.","example":"2025-12-31","key":"endDate","kind":"date","name":"endDate","required":true},{"city":true,"default":0,"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\"), a fixed offset like \"+05:30\", OR decimal hours from UTC. One offset is taken from startDate (DST-correct for that date) and used for the whole range, so a window crossing a daylight-saving change is read on the earlier offset throughout; send a fixed offset if you need that explicit. The two dates are read as calendar days in this timezone and output times are converted to it, so one date with 5.5 is that whole Indian day. Defaults to 0 (UTC).","example":5.5,"fold":true,"key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"viewerZone":true},{"default":"kp-newcomb","description":"Ayanamsa system for sidereal conversion. \"kp-newcomb\" uses the KP-Newcomb dynamic formula, the most common choice for KP astrology. \"kp-old\" uses the Krishnamurti original table from KP Reader-1 with constant precession rate. \"lahiri\" uses Lahiri/Chitrapaksha ayanamsa, matching most traditional Vedic software. \"raman\" uses the B.V. Raman ayanamsa from Hindu Predictive Astrology, a recognised traditional school that sits about 1.45 degrees below Lahiri. Defaults to \"kp-newcomb\".","enum":["kp-newcomb","kp-old","lahiri","raman"],"example":"kp-newcomb","fold":true,"key":"ayanamsa","kind":"tiles","name":"ayanamsa","required":false},{"default":"mean","description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the Rahu and Ketu positions. Mean is the traditional Vedic default and what printed panchangs use; the choice can move a KP sub-lord in narrow boundary cases, where a span can be as small as 0.5 degrees. Defaults to \"mean\".","enum":["mean","true"],"example":"mean","fold":true,"key":"nodeType","kind":"tiles","name":"nodeType","required":false}],"groups":[{}],"hasLang":false,"method":"POST","opensOnLoad":false,"path":"/vedic-astrology/kp/rasi-changes","title":"Find KP rasi ingress times"},"getKpRulingInterval":{"fields":[{"description":"Start of the interval range in ISO 8601 (YYYY-MM-DDTHH:MM:SS). Interpreted as local time when a non-zero timezone is provided (a trailing Z is accepted but ignored); with timezone 0 it is UTC.","example":"2026-02-03T00:00:00Z","key":"startDatetime","kind":"datetime","name":"startDatetime","required":true},{"description":"End of the interval range in ISO 8601 (YYYY-MM-DDTHH:MM:SS). Interpreted as local time when a non-zero timezone is provided (a trailing Z is accepted but ignored); with timezone 0 it is UTC.","example":"2026-02-03T01:00:00Z","key":"endDatetime","kind":"datetime","name":"endDatetime","required":true},{"description":"Interval between calculations in minutes (1-1440). Use 1-5 for birth time rectification.","example":5,"key":"intervalMinutes","kind":"number","max":1440,"min":1,"name":"intervalMinutes","required":true},{"description":"Observer latitude in decimal degrees","example":17.385044,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Observer longitude in decimal degrees","example":78.486671,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"default":5.5,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved once, at the start of the window, and that offset applies to every time in the response. When non-zero, all datetimes are treated as local time in this timezone (Z suffix is ignored). Output times are also converted to this timezone. Defaults to 5.5 (IST).","example":5.5,"key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"role":"location"},{"default":"kp-newcomb","description":"Ayanamsa system for sidereal conversion. \"kp-newcomb\" uses the KP-Newcomb dynamic formula, the most common choice for KP astrology. \"kp-old\" uses the Krishnamurti original table from KP Reader-1 with constant precession rate. \"lahiri\" uses Lahiri/Chitrapaksha ayanamsa, matching most traditional Vedic software. \"raman\" uses the B.V. Raman ayanamsa from Hindu Predictive Astrology, a recognised traditional school that sits about 1.45 degrees below Lahiri. Defaults to \"kp-newcomb\".","enum":["kp-newcomb","kp-old","lahiri","raman"],"example":"kp-newcomb","fold":true,"key":"ayanamsa","kind":"tiles","name":"ayanamsa","required":false},{"default":"mean","description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the Rahu and Ketu positions. Mean is the traditional Vedic default and what printed panchangs use; the choice can move a KP sub-lord in narrow boundary cases, where a span can be as small as 0.5 degrees. Defaults to \"mean\".","enum":["mean","true"],"example":"mean","fold":true,"key":"nodeType","kind":"tiles","name":"nodeType","required":false},{"default":"general","description":"Which signification vocabulary the houseThemes map returns. \"general\" gives the classical bhava significations (self, wealth, siblings, home, and so on). \"finance\" gives the money reading of the same twelve bhavas, so house 2 returns income and savings, 5 speculation and risk appetite, 8 sudden money and leverage, 11 gains and profits, and 12 expenses and capital outflow. Use \"finance\" for wealth, income, business and market timing questions in Krishnamurti Paddhati, where the significator house groups 2, 6, 10, 11 for earned income and 5, 8, 11 for speculation are read against a running dasha. Defaults to \"general\".","enum":["general","finance"],"example":"general","fold":true,"inQuery":true,"key":"focus","kind":"tiles","name":"focus","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/vedic-astrology/kp/ruling-planets-interval","title":"Get KP ruling planets with significators at intervals"},"getKpRulingPlanets":{"fields":[{"description":"Observer latitude in decimal degrees","example":28.6139,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Observer longitude in decimal degrees","example":77.209,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"default":5.5,"description":"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC. IANA resolved to the DST-correct offset based on birthDate or datetime. Defaults to 5.5.","example":5.5,"key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"role":"location"},{"description":"ISO 8601 datetime (YYYY-MM-DDTHH:MM:SS) for ruling planets. Defaults to current time. Interpreted as local time when a non-zero timezone is provided (a trailing Z is accepted but ignored); with timezone 0 it is UTC.","example":"2025-01-15T10:30:00Z","fold":true,"key":"datetime","kind":"datetime","name":"datetime","required":false},{"description":"Birth date (YYYY-MM-DD) to calculate significators. If provided with birthTime, response includes which houses each ruling planet signifies.","example":"1990-07-04","fold":true,"key":"birthDate","kind":"date","name":"birthDate","required":false},{"description":"Birth time (HH:MM:SS) for significator calculation. Required if birthDate is provided.","example":"10:12:00","fold":true,"key":"birthTime","kind":"time","name":"birthTime","required":false},{"default":"mean","description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the Rahu and Ketu positions. Mean is the traditional Vedic default and what printed panchangs use; the choice can move a KP sub-lord in narrow boundary cases, where a span can be as small as 0.5 degrees. Defaults to \"mean\".","enum":["mean","true"],"example":"mean","fold":true,"key":"nodeType","kind":"tiles","name":"nodeType","required":false},{"default":"general","description":"Which signification vocabulary the houseThemes map returns. \"general\" gives the classical bhava significations (self, wealth, siblings, home, and so on). \"finance\" gives the money reading of the same twelve bhavas, so house 2 returns income and savings, 5 speculation and risk appetite, 8 sudden money and leverage, 11 gains and profits, and 12 expenses and capital outflow. Use \"finance\" for wealth, income, business and market timing questions in Krishnamurti Paddhati, where the significator house groups 2, 6, 10, 11 for earned income and 5, 8, 11 for speculation are read against a running dasha. Defaults to \"general\".","enum":["general","finance"],"example":"general","fold":true,"inQuery":true,"key":"focus","kind":"tiles","name":"focus","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/vedic-astrology/kp/ruling-planets","title":"Get KP ruling planets with optional significators"},"getKpSublordChanges":{"fields":[{"description":"Planet to track (case-insensitive). Valid values: Sun, Moon, Mars, Mercury, Jupiter, Venus, Saturn","enum":["Sun","Moon","Mars","Mercury","Jupiter","Venus","Saturn"],"example":"Moon","key":"planet","kind":"tiles","name":"planet","required":true},{"description":"First day of the search (YYYY-MM-DD), a calendar day in `timezone`.","example":"2025-01-01","key":"startDate","kind":"date","name":"startDate","required":true},{"description":"Last day of the search, inclusive (YYYY-MM-DD), a calendar day in `timezone`. Not before startDate, at most 365 days after it.","example":"2025-01-31","key":"endDate","kind":"date","name":"endDate","required":true},{"city":true,"default":0,"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\"), a fixed offset like \"+05:30\", OR decimal hours from UTC. One offset is taken from startDate (DST-correct for that date) and used for the whole range, so a window crossing a daylight-saving change is read on the earlier offset throughout; send a fixed offset if you need that explicit. The two dates are read as calendar days in this timezone and output times are converted to it, so one date with 5.5 is that whole Indian day. Defaults to 0 (UTC).","example":5.5,"fold":true,"key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"viewerZone":true},{"default":"kp-newcomb","description":"Ayanamsa system for sidereal conversion. \"kp-newcomb\" uses the KP-Newcomb dynamic formula, the most common choice for KP astrology. \"kp-old\" uses the Krishnamurti original table from KP Reader-1 with constant precession rate. \"lahiri\" uses Lahiri/Chitrapaksha ayanamsa, matching most traditional Vedic software. \"raman\" uses the B.V. Raman ayanamsa from Hindu Predictive Astrology, a recognised traditional school that sits about 1.45 degrees below Lahiri. Defaults to \"kp-newcomb\".","enum":["kp-newcomb","kp-old","lahiri","raman"],"example":"kp-newcomb","fold":true,"key":"ayanamsa","kind":"tiles","name":"ayanamsa","required":false},{"default":"mean","description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the Rahu and Ketu positions. Mean is the traditional Vedic default and what printed panchangs use; the choice can move a KP sub-lord in narrow boundary cases, where a span can be as small as 0.5 degrees. Defaults to \"mean\".","enum":["mean","true"],"example":"mean","fold":true,"key":"nodeType","kind":"tiles","name":"nodeType","required":false}],"groups":[{}],"hasLang":false,"method":"POST","opensOnLoad":false,"path":"/vedic-astrology/kp/sublord-changes","title":"Find KP sublord changes"},"getKuaNumber":{"fields":[{"description":"Kua number, 1 to 9.","example":8,"inQuery":false,"key":"number","kind":"number","max":9,"min":1,"name":"number","required":true}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":false,"path":"/feng-shui/kua/{number}","title":"Look up a Kua number"},"getLunarAspects":{"fields":[{"description":"Year for monthly analysis (1551 to 2649). Defaults to the current year (UTC).","example":2026,"key":"year","kind":"number","max":2649,"min":1551,"name":"year","required":false},{"description":"Month number (1-12). Defaults to the current month (UTC).","example":2,"key":"month","kind":"number","max":12,"min":1,"name":"month","required":false},{"city":true,"default":0,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved once, at the start of the window, and that offset applies to every time in the response. Output times are converted to this timezone. Defaults to 0 (UTC).","example":5.5,"fold":true,"key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"viewerZone":true},{"default":"sidereal","description":"Coordinate system for longitude output. \"sidereal\" (Nirayana) uses Lahiri ayanamsa, the standard for Vedic astrology. \"tropical\" (Sayana) uses raw ecliptic longitude matching Western astrology. Defaults to \"sidereal\".","enum":["sidereal","tropical"],"example":"sidereal","fold":true,"key":"coordinateSystem","kind":"tiles","name":"coordinateSystem","required":false}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/vedic-astrology/aspects/lunar","title":"Monthly Lunar Aspects"},"getMajorDashas":{"fields":[{"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04","key":"date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00","key":"time","kind":"time","name":"time","required":true},{"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","example":28.6139,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","example":77.209,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"default":5.5,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time. Defaults to 5.5.","example":5.5,"key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"role":"location"},{"default":"lahiri","description":"Ayanamsa system used to place the birth Moon in its nakshatra, which sets every dasha start and end date. \"lahiri\" uses Lahiri/Chitrapaksha, the traditional Vedic standard, and is the default. \"kp-newcomb\" uses the KP-Newcomb dynamic formula, matching Krishnamurti Paddhati software. \"kp-old\" uses the Krishnamurti original table from KP Reader-1. \"raman\" uses the B.V. Raman ayanamsa, the second frame traditional Indian software commonly offers beside Lahiri. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. Switching frames shifts every dasha boundary by weeks, so pick the one your reference software uses.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"example":"lahiri","fold":true,"key":"ayanamsa","kind":"tiles","name":"ayanamsa","required":false},{"description":"Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.","example":24,"fold":true,"key":"ayanamsaValue","kind":"number","name":"ayanamsaValue","required":false},{"default":false,"description":"Set true to attach the KP significators of each period lord: its star lord, sub lord, occupied house, the houses it signifies at levels L1 to L4, and a strength grade. Off by default, so responses stay exactly as they are for clients that only need dates. Requires the birth latitude and longitude, since significators are read off a Placidus house chart, and uses the same ayanamsa frame selected above.","example":false,"fold":true,"key":"significators","kind":"toggle","name":"significators","required":false},{"default":"mean","description":"Lunar node type for Rahu and Ketu, used ONLY when \"significators\" is true. Dasha dates themselves come from the Moon and never move with this field. \"mean\" uses the smooth mean node (traditional default). \"true\" uses the osculating node, which swings up to 1.5 degrees either side of mean over a 173-day cycle and can therefore change which house or star a node falls in. Defaults to \"mean\".","enum":["mean","true"],"example":"mean","fold":true,"key":"nodeType","kind":"tiles","name":"nodeType","required":false},{"default":"general","description":"Which signification vocabulary the houseThemes map returns. \"general\" gives the classical bhava significations (self, wealth, siblings, home, and so on). \"finance\" gives the money reading of the same twelve bhavas, so house 2 returns income and savings, 5 speculation and risk appetite, 8 sudden money and leverage, 11 gains and profits, and 12 expenses and capital outflow. Use \"finance\" for wealth, income, business and market timing questions in Krishnamurti Paddhati, where the significator house groups 2, 6, 10, 11 for earned income and 5, 8, 11 for speculation are read against a running dasha. Defaults to \"general\".","enum":["general","finance"],"example":"general","fold":true,"inQuery":true,"key":"focus","kind":"tiles","name":"focus","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/vedic-astrology/dasha/major","title":"Get all 9 Mahadasha periods (120-year cycle)"},"getMayanDaySign":{"fields":[{"description":"Day sign id, case-insensitive and punctuation-insensitive. One of imix, ik, akbal, kan, chikchan, kimi, manik, lamat, muluk, ok, chuwen, eb, ben, ix, men, kib, kaban, etznab, kawak, ajaw.","enum":["imix","ik","akbal","kan","chikchan","kimi","manik","lamat","muluk","ok","chuwen","eb","ben","ix","men","kib","kaban","etznab","kawak","ajaw"],"example":"imix","inQuery":false,"key":"id","kind":"select","label":"Day sign","name":"id","required":true},{"default":"madrid-codex","description":"Which reading of the world direction and colour to serve for a day sign. The two published assignments differ by exactly one quarter turn on all twenty signs, so neither is a rounding of the other and a silent pick would be a school choice. \"madrid-codex\" is the codex reading and the default; \"landa\" is the sixteenth century assignment recorded beside it.","enum":["madrid-codex","landa"],"example":"madrid-codex","fold":true,"inQuery":true,"key":"directionScheme","kind":"tiles","name":"directionScheme","required":false}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":false,"path":"/mesoamerican-astrology/mayan/day-signs/{id}","title":"Get one Mayan day sign"},"getMonthlyAlmanac":{"fields":[{"description":"Gregorian year, 1900 to 2100. Defaults to the current UTC year when omitted, together with month.","example":1990,"inQuery":true,"key":"year","kind":"number","max":2100,"min":1900,"name":"year","required":false},{"description":"Gregorian month, 1 to 12. Defaults to the current UTC month when omitted, together with year.","example":6,"inQuery":true,"key":"month","kind":"number","max":12,"min":1,"name":"month","required":false}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":true,"path":"/chinese-astrology/calendar/monthly","title":"Get a month of almanac days"},"getMonthlyAspects":{"fields":[{"description":"Year for monthly analysis (1551 to 2649). Defaults to the current year (UTC).","example":2026,"key":"year","kind":"number","max":2649,"min":1551,"name":"year","required":false},{"description":"Month number (1-12). Defaults to the current month (UTC).","example":2,"key":"month","kind":"number","max":12,"min":1,"name":"month","required":false},{"city":true,"default":0,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved once, at the start of the window, and that offset applies to every time in the response. Output times are converted to this timezone. Defaults to 0 (UTC).","example":5.5,"fold":true,"key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"viewerZone":true},{"default":"sidereal","description":"Coordinate system for longitude output. \"sidereal\" (Nirayana) uses Lahiri ayanamsa, the standard for Vedic astrology. \"tropical\" (Sayana) uses raw ecliptic longitude matching Western astrology. Defaults to \"sidereal\".","enum":["sidereal","tropical"],"example":"sidereal","fold":true,"key":"coordinateSystem","kind":"tiles","name":"coordinateSystem","required":false}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/vedic-astrology/aspects/monthly","title":"Monthly Planetary Aspects"},"getMonthlyDeclinationParallels":{"fields":[{"description":"Year for the declination calendar (1551 to 2649). Defaults to the current year (UTC).","example":2026,"key":"year","kind":"number","max":2649,"min":1551,"name":"year","required":false},{"description":"Month number (1-12). Defaults to the current month (UTC).","example":3,"key":"month","kind":"number","max":12,"min":1,"name":"month","required":false},{"city":true,"default":0,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved once, at the start of the window, and that offset applies to every time in the response. Event dates and times are reported in this zone, which is what makes a published calendar read correctly for its audience. Defaults to 0 (UTC).","example":"America/New_York","fold":true,"key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"viewerZone":true},{"default":1.5,"description":"How far from exact still counts, in degrees. The traditional orb for a declination contact is tighter than for a zodiacal aspect because declination changes slowly. Defaults to 1.5.","example":1.5,"fold":true,"key":"orb","kind":"number","max":3,"min":0.1,"name":"orb","required":false},{"default":"true","description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"example":"true","fold":true,"key":"nodeType","kind":"tiles","name":"nodeType","required":false}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/astrology/parallels/monthly","title":"Monthly Parallels"},"getMonthlyEphemeris":{"fields":[{"description":"Year for monthly ephemeris (1551 to 2649). Defaults to the current year (UTC).","example":2026,"key":"year","kind":"number","max":2649,"min":1551,"name":"year","required":false},{"description":"Month number (1-12) for ephemeris. Defaults to the current month (UTC).","example":2,"key":"month","kind":"number","max":12,"min":1,"name":"month","required":false},{"default":"sidereal","description":"Coordinate system for longitude output. \"sidereal\" (Nirayana) uses Lahiri ayanamsa, the standard for Vedic astrology. \"tropical\" (Sayana) uses raw ecliptic longitude matching Western astrology. Defaults to \"sidereal\".","enum":["sidereal","tropical"],"example":"sidereal","fold":true,"key":"coordinateSystem","kind":"tiles","name":"coordinateSystem","required":false}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/vedic-astrology/planetary-positions/monthly","title":"Monthly Ephemeris"},"getMonthlyFlyingStars":{"fields":[{"description":"Solar year, 1900 to 2100. Defaults to the solar year in progress, which changes at Li Chun rather than on 1 January.","example":2026,"inQuery":true,"key":"year","kind":"number","max":2100,"min":1900,"name":"year","required":false},{"description":"Solar month, 1 to 12, where 1 begins at Li Chun in early February. This is NOT the calendar month: solar month 1 covers roughly 4 February to 5 March. Defaults to the solar month in progress.","example":1,"inQuery":true,"key":"month","kind":"number","max":12,"min":1,"name":"month","required":false}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":true,"path":"/feng-shui/flying-stars/monthly","title":"Monthly flying stars"},"getMonthlyHoroscope":{"fields":[{"description":"Zodiac sign, case-insensitive (e.g., aries, Aries, ARIES all work).","enum":["aries","taurus","gemini","cancer","leo","virgo","libra","scorpio","sagittarius","capricorn","aquarius","pisces"],"example":"aries","inQuery":false,"key":"sign","kind":"tiles","name":"sign","required":true},{"description":"Any date inside the target month, in YYYY-MM-DD format. The forecast covers the whole calendar month containing it. Defaults to the current period in the timezone parameter.","example":"2026-04-03","fold":true,"inQuery":true,"key":"date","kind":"date","name":"date","required":false},{"city":true,"description":"Selects which period counts as current when date is omitted. Defaults to UTC, so the forecast rolls over at 00:00 UTC on the 1st. Pass the timezone of the end user to roll over on their local clock instead. Ignored when date is set. Accepts an IANA name (e.g. \"America/New_York\"), decimal hours (e.g. 5.5 for IST), or a fixed UTC offset (e.g. \"-05:00\").","example":"America/New_York","fold":true,"inQuery":true,"key":"timezone","kind":"text","name":"timezone","required":false,"viewerZone":true}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":false,"path":"/astrology/horoscope/{sign}/monthly","title":"Monthly horoscope by zodiac sign"},"getMonthlyParallels":{"fields":[{"description":"Year for monthly parallel analysis (1551 to 2649). Defaults to the current year (UTC).","example":2026,"key":"year","kind":"number","max":2649,"min":1551,"name":"year","required":false},{"description":"Month number (1-12) for parallel analysis. Defaults to the current month (UTC).","example":2,"key":"month","kind":"number","max":12,"min":1,"name":"month","required":false},{"city":true,"default":0,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved once, at the start of the window, and that offset applies to every time in the response. Output times are converted to this timezone. Defaults to 0 (UTC).","example":5.5,"fold":true,"key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"viewerZone":true}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/vedic-astrology/parallels/monthly","title":"Monthly Declination Parallels"},"getMonthlyTransits":{"fields":[{"description":"Year for monthly transit analysis (1551 to 2649). Defaults to the current year (UTC).","example":2026,"key":"year","kind":"number","max":2649,"min":1551,"name":"year","required":false},{"description":"Month number (1-12) for transit analysis. Defaults to the current month (UTC).","example":2,"key":"month","kind":"number","max":12,"min":1,"name":"month","required":false},{"city":true,"default":0,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved once, at the start of the window, and that offset applies to every time in the response. Output times are converted to this timezone. Defaults to 0 (UTC).","example":5.5,"fold":true,"key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"viewerZone":true},{"default":"sidereal","description":"Coordinate system for longitude output. \"sidereal\" (Nirayana) uses Lahiri ayanamsa, the standard for Vedic astrology. \"tropical\" (Sayana) uses raw ecliptic longitude matching Western astrology. Defaults to \"sidereal\".","enum":["sidereal","tropical"],"example":"sidereal","fold":true,"key":"coordinateSystem","kind":"tiles","name":"coordinateSystem","required":false}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/vedic-astrology/transit/monthly","title":"Monthly Transit"},"getMonthlyTropicalAspects":{"fields":[{"description":"Year for the aspect calendar (1551 to 2649). Defaults to the current year (UTC).","example":2026,"key":"year","kind":"number","max":2649,"min":1551,"name":"year","required":false},{"description":"Month number (1-12). Defaults to the current month (UTC).","example":3,"key":"month","kind":"number","max":12,"min":1,"name":"month","required":false},{"city":true,"default":0,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved once, at the start of the window, and that offset applies to every time in the response. Event dates and times are reported in this zone, which is what makes a published calendar read correctly for its audience. Defaults to 0 (UTC).","example":"America/New_York","fold":true,"key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"viewerZone":true},{"default":"true","description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"example":"true","fold":true,"key":"nodeType","kind":"tiles","name":"nodeType","required":false}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/astrology/aspects/monthly","title":"Monthly Aspects"},"getMonthlyTropicalEphemeris":{"fields":[{"description":"Year for the monthly ephemeris (1551 to 2649). Defaults to the current year (UTC).","example":2026,"key":"year","kind":"number","max":2649,"min":1551,"name":"year","required":false},{"description":"Month number (1-12) for the ephemeris. Defaults to the current month (UTC).","example":8,"key":"month","kind":"number","max":12,"min":1,"name":"month","required":false}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/astrology/planets/monthly","title":"Monthly Ephemeris"},"getMonthlyTropicalTransits":{"fields":[{"description":"Year for the monthly transit table (1551 to 2649). Defaults to the current year (UTC).","example":2026,"key":"year","kind":"number","max":2649,"min":1551,"name":"year","required":false},{"description":"Month number (1-12). Defaults to the current month (UTC).","example":3,"key":"month","kind":"number","max":12,"min":1,"name":"month","required":false},{"city":true,"default":0,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved once, at the start of the window, and that offset applies to every time in the response. Ingress dates and times are reported in this zone, which is what makes a published calendar read correctly for its audience. Defaults to 0 (UTC).","example":"America/New_York","fold":true,"key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"viewerZone":true},{"default":"true","description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"example":"true","fold":true,"key":"nodeType","kind":"tiles","name":"nodeType","required":false}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/astrology/transits/monthly","title":"Monthly Transits"},"getMonthlyTzolkinCalendar":{"fields":[{"description":"Gregorian year of the grid, 1900 to 2100. Defaults to the current year in UTC. Wider historical ranges are available on the single date routes, which are not bounded to this window.","example":2026,"inQuery":true,"key":"year","kind":"number","max":2100,"min":1900,"name":"year","required":false},{"description":"Calendar month of the grid, 1 to 12. Defaults to the current month in UTC.","example":9,"inQuery":true,"key":"month","kind":"number","max":12,"min":1,"name":"month","required":false},{"default":"gmt-584283","description":"Which correlation constant ties the day count to a civil date. This is the single choice that shifts every value in the response, so it is a parameter rather than a hidden default, and the resolved value comes back under conventions. \"gmt-584283\" is the commonly accepted constant and the default, and it is the one the major institutional converter runs on. \"martinez-hernandez-584281\" sits two days earlier, \"astronomical-584285\" two days later, and \"martin-skidmore-584286\" three days later, each shifting the Long Count by exactly its difference in days. Four of the eight published constants are offered: the other four sit tens of thousands of days away and are of historical interest only. The 584281 constant is the Martínez Hernández correlation, after Juan Martínez Hernández.","enum":["gmt-584283","martinez-hernandez-584281","astronomical-584285","martin-skidmore-584286"],"example":"gmt-584283","fold":true,"inQuery":true,"key":"correlation","kind":"tiles","name":"correlation","required":false}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":true,"path":"/mesoamerican-astrology/mayan/calendar/monthly","title":"Monthly Tzolkin calendar grid"},"getMoonCalendar":{"fields":[{"description":"Calendar year, 1551 to 2649.","example":2026,"inQuery":false,"key":"year","kind":"number","max":2649,"min":1551,"name":"year","required":true},{"description":"Calendar month (1-12). 1 = January, 12 = December.","example":3,"inQuery":false,"key":"month","kind":"number","max":12,"min":1,"name":"month","required":true}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":false,"path":"/astrology/moon-phase/calendar/{year}/{month}","title":"Get lunar calendar"},"getNakshatra":{"fields":[{"description":"Nakshatra ID slug. Examples: ashwini, bharani, krittika, rohini, mrigashira, ardra, punarvasu, pushya, ashlesha, magha, etc.","enum":["ashwini","bharani","krittika","rohini","mrigashira","ardra","punarvasu","pushya","ashlesha","magha","purva-phalguni","uttara-phalguni","hasta","chitra","swati","vishakha","anuradha","jyeshtha","moola","purva-ashadha","uttara-ashadha","shravana","dhanishta","shatabhisha","purva-bhadrapada","uttara-bhadrapada","revati"],"example":"ashwini","inQuery":false,"key":"id","kind":"select","label":"Nakshatra","name":"id","required":true}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":false,"path":"/vedic-astrology/nakshatras/{id}","title":"Get Nakshatra by ID"},"getNumberMeaning":{"fields":[{"description":"Numerology number (1-9, 11, 22, 33)","example":"5","inQuery":false,"key":"number","kind":"text","name":"number","required":true}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":false,"path":"/numerology/meanings/{number}","title":"Get number meaning"},"getPhases":{"fields":[{"description":"Birth date of the person in YYYY-MM-DD format.","example":"1990-07-15","key":"birthDate","kind":"date","name":"birthDate","required":true},{"description":"Date to get phase information for in YYYY-MM-DD format. Defaults to today (UTC).","example":"2026-04-10","fold":true,"key":"targetDate","kind":"date","name":"targetDate","required":false}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/biorhythm/phases","title":"Get phase info"},"getPlanetMeaning":{"fields":[{"description":"Planet ID (lowercase, e.g., sun, moon, mercury) or display name (case-insensitive, e.g., Sun, MOON). Spaces, hyphens and underscores are interchangeable, so the two lunar nodes answer to north-node and south-node as well as to their ids north node and south node, and Black Moon Lilith answers to black-moon-lilith as well as to lilith.","example":"sun","inQuery":false,"key":"id","kind":"text","name":"id","required":true,"source":{"lang":true,"path":"/astrology/planet-meanings"}}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":false,"path":"/astrology/planet-meanings/{id}","title":"Get planet meaning details"},"getPlanetPositions":{"fields":[{"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04","key":"date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00","key":"time","kind":"time","name":"time","required":true},{"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","example":28.6139,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","example":77.209,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"default":5.5,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time. Defaults to 5.5.","example":5.5,"key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"role":"location"},{"default":"lahiri","description":"Sidereal frame (ayanamsa) the chart is cast in. \"lahiri\" is Lahiri/Chitrapaksha, the traditional Vedic standard used by most software, and is the default. \"raman\" is the B.V. Raman ayanamsa from Hindu Predictive Astrology, about 1.45 degrees below Lahiri. \"kp-newcomb\" and \"kp-old\" are the two Krishnamurti Paddhati frames. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"example":"lahiri","fold":true,"key":"ayanamsa","kind":"tiles","name":"ayanamsa","required":false},{"description":"Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.","example":24,"fold":true,"key":"ayanamsaValue","kind":"number","name":"ayanamsaValue","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/vedic-astrology/planetary-positions","title":"Get planetary positions"},"getPlanetaryNodePassages":{"fields":[{"description":"Year to scan for node passages (1551 to 2649).","example":2026,"key":"year","kind":"number","max":2649,"min":1551,"name":"year","required":true},{"city":true,"default":0,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved once, at the start of the window, and that offset applies to every time in the response. Crossing dates and times are reported in this zone. Defaults to 0 (UTC).","example":"America/New_York","fold":true,"key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"viewerZone":true}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/astrology/ecliptic-crossings","title":"Ecliptic Crossings"},"getPlanetaryPositions":{"fields":[{"description":"Target date for planetary positions in YYYY-MM-DD format. Use current date for transit positions, or any historical/future date for research. Planets move daily, so this date determines their zodiac positions.","example":"2025-12-18","key":"date","kind":"date","name":"date","required":true},{"description":"Time in 24-hour HH:MM:SS format for precise calculations. Moon moves ~13° per day, so time matters for accurate lunar position. Use 12:00:00 (noon) as default if exact time not needed.","example":"12:00:00","key":"time","kind":"time","name":"time","required":true},{"default":"true","description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"example":"true","fold":true,"key":"nodeType","kind":"tiles","name":"nodeType","required":false},{"description":"Observer latitude in decimal degrees (-90 to 90). While planetary longitudes are geocentric (same worldwide), this is needed for house calculations if extending functionality. For basic ephemeris, use 0 as default.","example":40.7128,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Observer longitude in decimal degrees (-180 to 180). Used for precise local time conversion. For basic planetary positions, this has minimal impact but ensures accuracy.","example":-74.006,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"description":"Decimal hours from UTC (e.g. -5 for EST, 5.5 for IST, 9 for JST, 5.75 for NPT) OR IANA name (e.g. \"America/New_York\"). IANA resolved to the DST-correct offset for the chart date.","example":"America/New_York","key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":true,"role":"location"}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/astrology/planets","title":"Get planetary positions"},"getPranaDashas":{"fields":[{"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04","key":"date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00","key":"time","kind":"time","name":"time","required":true},{"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","example":28.6139,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","example":77.209,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"default":5.5,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time. Defaults to 5.5.","example":5.5,"key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"role":"location"},{"default":"lahiri","description":"Ayanamsa system used to place the birth Moon in its nakshatra, which sets every dasha start and end date. \"lahiri\" uses Lahiri/Chitrapaksha, the traditional Vedic standard, and is the default. \"kp-newcomb\" uses the KP-Newcomb dynamic formula, matching Krishnamurti Paddhati software. \"kp-old\" uses the Krishnamurti original table from KP Reader-1. \"raman\" uses the B.V. Raman ayanamsa, the second frame traditional Indian software commonly offers beside Lahiri. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. Switching frames shifts every dasha boundary by weeks, so pick the one your reference software uses.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"example":"lahiri","fold":true,"key":"ayanamsa","kind":"tiles","name":"ayanamsa","required":false},{"description":"Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.","example":24,"fold":true,"key":"ayanamsaValue","kind":"number","name":"ayanamsaValue","required":false},{"default":false,"description":"Set true to attach the KP significators of each period lord: its star lord, sub lord, occupied house, the houses it signifies at levels L1 to L4, and a strength grade. Off by default, so responses stay exactly as they are for clients that only need dates. Requires the birth latitude and longitude, since significators are read off a Placidus house chart, and uses the same ayanamsa frame selected above.","example":false,"fold":true,"key":"significators","kind":"toggle","name":"significators","required":false},{"default":"mean","description":"Lunar node type for Rahu and Ketu, used ONLY when \"significators\" is true. Dasha dates themselves come from the Moon and never move with this field. \"mean\" uses the smooth mean node (traditional default). \"true\" uses the osculating node, which swings up to 1.5 degrees either side of mean over a 173-day cycle and can therefore change which house or star a node falls in. Defaults to \"mean\".","enum":["mean","true"],"example":"mean","fold":true,"key":"nodeType","kind":"tiles","name":"nodeType","required":false},{"description":"Mahadasha planet name, case-insensitive. Valid: Ketu, Venus, Sun, Moon, Mars, Rahu, Jupiter, Saturn, Mercury.","enum":["Ketu","Venus","Sun","Moon","Mars","Rahu","Jupiter","Saturn","Mercury"],"example":"Saturn","inQuery":false,"key":"mahadasha","kind":"tiles","name":"mahadasha","required":true},{"description":"Antardasha (bhukti) planet name inside that Mahadasha, case-insensitive.","enum":["Ketu","Venus","Sun","Moon","Mars","Rahu","Jupiter","Saturn","Mercury"],"example":"Venus","inQuery":false,"key":"antardasha","kind":"tiles","name":"antardasha","required":true},{"description":"Pratyantardasha (antara) planet name inside that Antardasha, case-insensitive.","enum":["Ketu","Venus","Sun","Moon","Mars","Rahu","Jupiter","Saturn","Mercury"],"example":"Rahu","inQuery":false,"key":"pratyantardasha","kind":"tiles","name":"pratyantardasha","required":true},{"description":"Sookshma dasha planet name inside that Pratyantardasha, case-insensitive. Every full period contains all 9 lords, so a repeat such as saturn/saturn/saturn/saturn is valid.","enum":["Ketu","Venus","Sun","Moon","Mars","Rahu","Jupiter","Saturn","Mercury"],"example":"Jupiter","inQuery":false,"key":"sookshma","kind":"tiles","name":"sookshma","required":true},{"default":"general","description":"Which signification vocabulary the houseThemes map returns. \"general\" gives the classical bhava significations (self, wealth, siblings, home, and so on). \"finance\" gives the money reading of the same twelve bhavas, so house 2 returns income and savings, 5 speculation and risk appetite, 8 sudden money and leverage, 11 gains and profits, and 12 expenses and capital outflow. Use \"finance\" for wealth, income, business and market timing questions in Krishnamurti Paddhati, where the significator house groups 2, 6, 10, 11 for earned income and 5, 8, 11 for speculation are read against a running dasha. Defaults to \"general\".","enum":["general","finance"],"example":"general","fold":true,"inQuery":true,"key":"focus","kind":"tiles","name":"focus","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/vedic-astrology/dasha/sub/{mahadasha}/{antardasha}/{pratyantardasha}/{sookshma}","title":"Get all Prana dashas for a Mahadasha, Antardasha, Pratyantardasha and Sookshma"},"getPratyantardashas":{"fields":[{"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04","key":"date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00","key":"time","kind":"time","name":"time","required":true},{"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","example":28.6139,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","example":77.209,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"default":5.5,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time. Defaults to 5.5.","example":5.5,"key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"role":"location"},{"default":"lahiri","description":"Ayanamsa system used to place the birth Moon in its nakshatra, which sets every dasha start and end date. \"lahiri\" uses Lahiri/Chitrapaksha, the traditional Vedic standard, and is the default. \"kp-newcomb\" uses the KP-Newcomb dynamic formula, matching Krishnamurti Paddhati software. \"kp-old\" uses the Krishnamurti original table from KP Reader-1. \"raman\" uses the B.V. Raman ayanamsa, the second frame traditional Indian software commonly offers beside Lahiri. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. Switching frames shifts every dasha boundary by weeks, so pick the one your reference software uses.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"example":"lahiri","fold":true,"key":"ayanamsa","kind":"tiles","name":"ayanamsa","required":false},{"description":"Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.","example":24,"fold":true,"key":"ayanamsaValue","kind":"number","name":"ayanamsaValue","required":false},{"default":false,"description":"Set true to attach the KP significators of each period lord: its star lord, sub lord, occupied house, the houses it signifies at levels L1 to L4, and a strength grade. Off by default, so responses stay exactly as they are for clients that only need dates. Requires the birth latitude and longitude, since significators are read off a Placidus house chart, and uses the same ayanamsa frame selected above.","example":false,"fold":true,"key":"significators","kind":"toggle","name":"significators","required":false},{"default":"mean","description":"Lunar node type for Rahu and Ketu, used ONLY when \"significators\" is true. Dasha dates themselves come from the Moon and never move with this field. \"mean\" uses the smooth mean node (traditional default). \"true\" uses the osculating node, which swings up to 1.5 degrees either side of mean over a 173-day cycle and can therefore change which house or star a node falls in. Defaults to \"mean\".","enum":["mean","true"],"example":"mean","fold":true,"key":"nodeType","kind":"tiles","name":"nodeType","required":false},{"description":"Mahadasha planet name, case-insensitive (e.g. saturn, Saturn, SATURN all work). Valid: Ketu, Venus, Sun, Moon, Mars, Rahu, Jupiter, Saturn, Mercury.","enum":["Ketu","Venus","Sun","Moon","Mars","Rahu","Jupiter","Saturn","Mercury"],"example":"Saturn","inQuery":false,"key":"mahadasha","kind":"tiles","name":"mahadasha","required":true},{"description":"Antardasha (bhukti) planet name inside that Mahadasha, case-insensitive. Every Mahadasha contains all 9 lords, so a repeat such as saturn/saturn is valid.","enum":["Ketu","Venus","Sun","Moon","Mars","Rahu","Jupiter","Saturn","Mercury"],"example":"Venus","inQuery":false,"key":"antardasha","kind":"tiles","name":"antardasha","required":true},{"default":"general","description":"Which signification vocabulary the houseThemes map returns. \"general\" gives the classical bhava significations (self, wealth, siblings, home, and so on). \"finance\" gives the money reading of the same twelve bhavas, so house 2 returns income and savings, 5 speculation and risk appetite, 8 sudden money and leverage, 11 gains and profits, and 12 expenses and capital outflow. Use \"finance\" for wealth, income, business and market timing questions in Krishnamurti Paddhati, where the significator house groups 2, 6, 10, 11 for earned income and 5, 8, 11 for speculation are read against a running dasha. Defaults to \"general\".","enum":["general","finance"],"example":"general","fold":true,"inQuery":true,"key":"focus","kind":"tiles","name":"focus","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/vedic-astrology/dasha/sub/{mahadasha}/{antardasha}","title":"Get all Pratyantardashas (antara periods) for a Mahadasha and Antardasha"},"getRandomCrystal":{"fields":[],"groups":[],"hasLang":true,"method":"GET","opensOnLoad":true,"path":"/crystals/random","title":"Random crystal"},"getRandomHexagram":{"fields":[],"groups":[],"hasLang":true,"method":"GET","opensOnLoad":true,"path":"/iching/hexagrams/random","title":"Random hexagram"},"getRandomSymbols":{"fields":[{"default":1,"description":"Number of random symbols to return (1-10). Default: 1.","example":1,"fold":true,"inQuery":true,"key":"count","kind":"number","max":10,"min":1,"name":"count","required":false}],"groups":[{}],"hasLang":false,"method":"GET","opensOnLoad":true,"path":"/dreams/symbols/random","title":"Random dream symbols"},"getRashi":{"fields":[{"description":"Rashi ID slug. One of: mesha, vrishabha, mithun, karka, simha, kanya, tula, vrischika, dhanu, makar, kumbha, meen.","enum":["mesha","vrishabha","mithun","karka","simha","kanya","tula","vrischika","dhanu","makar","kumbha","meen"],"example":"mesha","inQuery":false,"key":"id","kind":"tiles","label":"Rashi","name":"id","required":true}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":false,"path":"/vedic-astrology/rashis/{id}","title":"Get Rashi by ID"},"getReading":{"fields":[{"description":"Birth date of the person in YYYY-MM-DD format. This is the anchor for all biorhythm cycle calculations.","example":"1990-07-15","key":"birthDate","kind":"date","name":"birthDate","required":true},{"description":"Date to calculate the reading for in YYYY-MM-DD format. Defaults to today (UTC) if omitted.","example":"2026-04-10","fold":true,"key":"targetDate","kind":"date","name":"targetDate","required":false}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/biorhythm/reading","title":"Get biorhythm reading"},"getRitucharya":{"fields":[{"description":"The date to resolve, in YYYY-MM-DD format. The season is read at midday UTC on this date, because a season boundary is an instant and a calendar day has to be reduced to one; on a day that carries a boundary, the half the midday falls in is the answer. Within about two months of either end of the supported span, a date whose season opens or closes outside that span answers 400.","example":"2026-03-01","key":"date","kind":"date","name":"date","required":true},{"default":"sutrasthana-6","description":"Which six-season division the year is cut into. \"sutrasthana-6\" is the standard set of sisira, vasanta, grisma, varsa, sarad and hemanta, and is the default. \"vimana-8\" is the alternate division in which three seasons of extreme character alternate with three of moderate character and pravrt, the season of the first rains, replaces sisira. The alternate is not a relabelling: five of the six boundaries move, and because its verse gives no solar-month boundaries the month allocation is a RoxyAPI convention, stated in the response.","enum":["sutrasthana-6","vimana-8"],"example":"sutrasthana-6","fold":true,"key":"ritucharyaScheme","kind":"tiles","name":"ritucharyaScheme","required":false},{"default":"sayana","description":"Which zodiac the solar-month boundaries are measured in. \"sayana\" is the tropical reading, which is what published almanacs use for seasons and is the default. \"nirayana\" is the sidereal reading in the Lahiri frame, which runs about 24 days later. The gap is the size of the ayanamsa, so near a boundary the two answer with different seasons for the same date, which is why the value is echoed in every response.","enum":["sayana","nirayana"],"example":"sayana","fold":true,"key":"rituZodiac","kind":"tiles","name":"rituZodiac","required":false},{"default":"northern","description":"Which half of the world the season names are stated for. Defaults to \"northern\", which is the half the primary text describes. It is NEVER inferred from a latitude: a silent flip would change the answer without the caller asking, and no classical text handles the southern case at all. Passing \"southern\" rotates the six season names by three places, following a modern almanac rather than a verse, and the response says so and states what was not rotated with them.","enum":["northern","southern"],"example":"northern","fold":true,"key":"hemisphere","kind":"tiles","name":"hemisphere","required":false}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/ayurveda/ritucharya","title":"Ayurveda seasonal regimen"},"getSephirah":{"fields":[{"description":"Sephirah identifier, one of keter, chokhmah, binah, chesed, gevurah, tiferet, netzach, hod, yesod, malkuth, daat. Matching folds case and punctuation.","enum":["keter","chokhmah","binah","chesed","gevurah","tiferet","netzach","hod","yesod","malkuth","daat"],"example":"tiferet","inQuery":false,"key":"id","kind":"tiles","label":"Sephirah","name":"id","required":true},{"default":"classical","description":"Which reading assigns a sphere to each sephirah. The two were compared row by row and agree on all ten, so the answer is the same either way; the parameter exists so a caller knows which one produced it rather than assuming.","enum":["classical","golden-dawn"],"example":"classical","fold":true,"inQuery":true,"key":"sephirotSystem","kind":"tiles","name":"sephirotSystem","required":false},{"default":"sefer-yetzirah-gra","description":"Which reading assigns the element, planet or sign to each letter. The seven double letters are the contested column and the four readings genuinely disagree on them; the twelve simple letters run in natural zodiacal order in all four. The golden-dawn member does NOT exchange He and Tzade, which is a later change from a different author.","enum":["sefer-yetzirah-gra","sefer-yetzirah-short","sefer-yetzirah-saadia","golden-dawn"],"example":"sefer-yetzirah-gra","fold":true,"inQuery":true,"key":"letterAttribution","kind":"tiles","name":"letterAttribution","required":false}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":false,"path":"/kabbalah/sephirot/{id}","title":"Get one sephirah"},"getShemName":{"fields":[{"description":"Index of the name, 1 to 72.","example":27,"inQuery":false,"key":"number","kind":"number","max":72,"min":1,"name":"number","required":true}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":false,"path":"/kabbalah/names/{number}","title":"Get one of the 72 names"},"getSookshmaDashas":{"fields":[{"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04","key":"date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00","key":"time","kind":"time","name":"time","required":true},{"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","example":28.6139,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","example":77.209,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"default":5.5,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time. Defaults to 5.5.","example":5.5,"key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"role":"location"},{"default":"lahiri","description":"Ayanamsa system used to place the birth Moon in its nakshatra, which sets every dasha start and end date. \"lahiri\" uses Lahiri/Chitrapaksha, the traditional Vedic standard, and is the default. \"kp-newcomb\" uses the KP-Newcomb dynamic formula, matching Krishnamurti Paddhati software. \"kp-old\" uses the Krishnamurti original table from KP Reader-1. \"raman\" uses the B.V. Raman ayanamsa, the second frame traditional Indian software commonly offers beside Lahiri. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. Switching frames shifts every dasha boundary by weeks, so pick the one your reference software uses.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"example":"lahiri","fold":true,"key":"ayanamsa","kind":"tiles","name":"ayanamsa","required":false},{"description":"Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.","example":24,"fold":true,"key":"ayanamsaValue","kind":"number","name":"ayanamsaValue","required":false},{"default":false,"description":"Set true to attach the KP significators of each period lord: its star lord, sub lord, occupied house, the houses it signifies at levels L1 to L4, and a strength grade. Off by default, so responses stay exactly as they are for clients that only need dates. Requires the birth latitude and longitude, since significators are read off a Placidus house chart, and uses the same ayanamsa frame selected above.","example":false,"fold":true,"key":"significators","kind":"toggle","name":"significators","required":false},{"default":"mean","description":"Lunar node type for Rahu and Ketu, used ONLY when \"significators\" is true. Dasha dates themselves come from the Moon and never move with this field. \"mean\" uses the smooth mean node (traditional default). \"true\" uses the osculating node, which swings up to 1.5 degrees either side of mean over a 173-day cycle and can therefore change which house or star a node falls in. Defaults to \"mean\".","enum":["mean","true"],"example":"mean","fold":true,"key":"nodeType","kind":"tiles","name":"nodeType","required":false},{"description":"Mahadasha planet name, case-insensitive. Valid: Ketu, Venus, Sun, Moon, Mars, Rahu, Jupiter, Saturn, Mercury.","enum":["Ketu","Venus","Sun","Moon","Mars","Rahu","Jupiter","Saturn","Mercury"],"example":"Saturn","inQuery":false,"key":"mahadasha","kind":"tiles","name":"mahadasha","required":true},{"description":"Antardasha (bhukti) planet name inside that Mahadasha, case-insensitive.","enum":["Ketu","Venus","Sun","Moon","Mars","Rahu","Jupiter","Saturn","Mercury"],"example":"Venus","inQuery":false,"key":"antardasha","kind":"tiles","name":"antardasha","required":true},{"description":"Pratyantardasha (antara) planet name inside that Antardasha, case-insensitive.","enum":["Ketu","Venus","Sun","Moon","Mars","Rahu","Jupiter","Saturn","Mercury"],"example":"Rahu","inQuery":false,"key":"pratyantardasha","kind":"tiles","name":"pratyantardasha","required":true},{"default":"general","description":"Which signification vocabulary the houseThemes map returns. \"general\" gives the classical bhava significations (self, wealth, siblings, home, and so on). \"finance\" gives the money reading of the same twelve bhavas, so house 2 returns income and savings, 5 speculation and risk appetite, 8 sudden money and leverage, 11 gains and profits, and 12 expenses and capital outflow. Use \"finance\" for wealth, income, business and market timing questions in Krishnamurti Paddhati, where the significator house groups 2, 6, 10, 11 for earned income and 5, 8, 11 for speculation are read against a running dasha. Defaults to \"general\".","enum":["general","finance"],"example":"general","fold":true,"inQuery":true,"key":"focus","kind":"tiles","name":"focus","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/vedic-astrology/dasha/sub/{mahadasha}/{antardasha}/{pratyantardasha}","title":"Get all Sookshma dashas for a Mahadasha, Antardasha and Pratyantardasha"},"getSubDashas":{"fields":[{"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04","key":"date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00","key":"time","kind":"time","name":"time","required":true},{"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","example":28.6139,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","example":77.209,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"default":5.5,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time. Defaults to 5.5.","example":5.5,"key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"role":"location"},{"default":"lahiri","description":"Ayanamsa system used to place the birth Moon in its nakshatra, which sets every dasha start and end date. \"lahiri\" uses Lahiri/Chitrapaksha, the traditional Vedic standard, and is the default. \"kp-newcomb\" uses the KP-Newcomb dynamic formula, matching Krishnamurti Paddhati software. \"kp-old\" uses the Krishnamurti original table from KP Reader-1. \"raman\" uses the B.V. Raman ayanamsa, the second frame traditional Indian software commonly offers beside Lahiri. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. Switching frames shifts every dasha boundary by weeks, so pick the one your reference software uses.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"example":"lahiri","fold":true,"key":"ayanamsa","kind":"tiles","name":"ayanamsa","required":false},{"description":"Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.","example":24,"fold":true,"key":"ayanamsaValue","kind":"number","name":"ayanamsaValue","required":false},{"default":false,"description":"Set true to attach the KP significators of each period lord: its star lord, sub lord, occupied house, the houses it signifies at levels L1 to L4, and a strength grade. Off by default, so responses stay exactly as they are for clients that only need dates. Requires the birth latitude and longitude, since significators are read off a Placidus house chart, and uses the same ayanamsa frame selected above.","example":false,"fold":true,"key":"significators","kind":"toggle","name":"significators","required":false},{"default":"mean","description":"Lunar node type for Rahu and Ketu, used ONLY when \"significators\" is true. Dasha dates themselves come from the Moon and never move with this field. \"mean\" uses the smooth mean node (traditional default). \"true\" uses the osculating node, which swings up to 1.5 degrees either side of mean over a 173-day cycle and can therefore change which house or star a node falls in. Defaults to \"mean\".","enum":["mean","true"],"example":"mean","fold":true,"key":"nodeType","kind":"tiles","name":"nodeType","required":false},{"description":"Mahadasha planet name, case-insensitive (e.g., jupiter, Jupiter, JUPITER all work). Valid: Ketu, Venus, Sun, Moon, Mars, Rahu, Jupiter, Saturn, Mercury.","enum":["Ketu","Venus","Sun","Moon","Mars","Rahu","Jupiter","Saturn","Mercury"],"example":"Jupiter","inQuery":false,"key":"mahadasha","kind":"tiles","name":"mahadasha","required":true},{"default":"general","description":"Which signification vocabulary the houseThemes map returns. \"general\" gives the classical bhava significations (self, wealth, siblings, home, and so on). \"finance\" gives the money reading of the same twelve bhavas, so house 2 returns income and savings, 5 speculation and risk appetite, 8 sudden money and leverage, 11 gains and profits, and 12 expenses and capital outflow. Use \"finance\" for wealth, income, business and market timing questions in Krishnamurti Paddhati, where the significator house groups 2, 6, 10, 11 for earned income and 5, 8, 11 for speculation are read against a running dasha. Defaults to \"general\".","enum":["general","finance"],"example":"general","fold":true,"inQuery":true,"key":"focus","kind":"tiles","name":"focus","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/vedic-astrology/dasha/sub/{mahadasha}","title":"Get all Antardashas (sub-periods) for a specific Mahadasha"},"getSymbolLetterCounts":{"fields":[],"groups":[],"hasLang":false,"method":"GET","opensOnLoad":true,"path":"/dreams/symbols/letters","title":"Symbol counts by letter"},"getTrecena":{"fields":[{"description":"Trecena number, 1 to 20. Trecena 1 opens on 1 Imix, trecena 2 on 1 Ix, and each subsequent period opens thirteen signs further round the twenty.","example":1,"inQuery":false,"key":"number","kind":"number","name":"number","required":true}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":false,"path":"/mesoamerican-astrology/mayan/trecenas/{number}","title":"Get one Mayan trecena"},"getTreeOfLife":{"fields":[{"default":"kircher","description":"Which arrangement of the twenty two paths. The 1652 arrangement, in which Malkuth carries three paths, is the only one with a published table that letters every path, so it is the only member.","enum":["kircher"],"example":"kircher","fold":true,"inQuery":true,"key":"treeVariant","kind":"tiles","name":"treeVariant","required":false},{"default":"classical","description":"Which reading assigns a sphere to each sephirah. The two were compared row by row and agree on all ten, so the answer is the same either way; the parameter exists so a caller knows which one produced it rather than assuming.","enum":["classical","golden-dawn"],"example":"classical","fold":true,"inQuery":true,"key":"sephirotSystem","kind":"tiles","name":"sephirotSystem","required":false},{"default":"sefer-yetzirah-gra","description":"Which reading assigns the element, planet or sign to each letter. The seven double letters are the contested column and the four readings genuinely disagree on them; the twelve simple letters run in natural zodiacal order in all four. The golden-dawn member does NOT exchange He and Tzade, which is a later change from a different author.","enum":["sefer-yetzirah-gra","sefer-yetzirah-short","sefer-yetzirah-saadia","golden-dawn"],"example":"sefer-yetzirah-gra","fold":true,"inQuery":true,"key":"letterAttribution","kind":"tiles","name":"letterAttribution","required":false}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":true,"path":"/kabbalah/tree","title":"Get the Tree of Life"},"getTrigram":{"fields":[{"description":"Trigram number (1-8) or English name (Heaven, Earth, Thunder, Wind, Water, Fire, Mountain, Lake).","example":"Heaven","inQuery":false,"key":"id","kind":"text","name":"id","required":true,"source":{"lang":true,"path":"/iching/trigrams"}}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":false,"path":"/iching/trigrams/{id}","title":"Get trigram by number or name"},"getUpagrahaPositions":{"fields":[{"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04","key":"date","kind":"date","name":"date","required":true},{"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00","key":"time","kind":"time","name":"time","required":true},{"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","example":28.6139,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","example":77.209,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"default":5.5,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time. Defaults to 5.5.","example":5.5,"key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"role":"location"},{"default":"lahiri","description":"Sidereal frame (ayanamsa) the chart is cast in. \"lahiri\" is Lahiri/Chitrapaksha, the traditional Vedic standard used by most software, and is the default. \"raman\" is the B.V. Raman ayanamsa from Hindu Predictive Astrology, about 1.45 degrees below Lahiri. \"kp-newcomb\" and \"kp-old\" are the two Krishnamurti Paddhati frames. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"example":"lahiri","fold":true,"key":"ayanamsa","kind":"tiles","name":"ayanamsa","required":false},{"description":"Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.","example":24,"fold":true,"key":"ayanamsaValue","kind":"number","name":"ayanamsaValue","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":false,"method":"POST","opensOnLoad":false,"path":"/vedic-astrology/upagraha","title":"Get upagraha (sub-planet) positions"},"getUpcomingMoonPhases":{"fields":[{"description":"Start date in YYYY-MM-DD format. Defaults to today if omitted.","example":"2025-12-18","inQuery":true,"key":"startDate","kind":"date","name":"startDate","required":false},{"default":8,"description":"Number of upcoming moon phase transitions to return (1-20). Defaults to 8.","example":8,"fold":true,"inQuery":true,"key":"count","kind":"number","max":20,"min":1,"name":"count","required":false}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":true,"path":"/astrology/moon-phase/upcoming","title":"Get upcoming moon phases"},"getUsageStats":{"fields":[],"groups":[],"hasLang":false,"method":"GET","opensOnLoad":true,"path":"/usage","title":"Get API usage statistics"},"getVedicDailyReading":{"fields":[{"description":"Birth date in YYYY-MM-DD format. Fixes the Janma Rashi and Janma Nakshatra every part of this reading is counted from, and the natal Ashtakavarga the bindu gate reads.","example":"1984-11-03","key":"birthDate","kind":"date","name":"birthDate","required":true},{"description":"Birth time in HH:MM:SS format (24-hour). The Moon moves about half a degree an hour, so an error here moves the Janma Rashi and Janma Nakshatra and therefore every gochara house count, the tarabala and the chandrabala in this response.","example":"01:35:00","key":"birthTime","kind":"time","name":"birthTime","required":true},{"description":"Birth location latitude in decimal degrees. Sets the natal house cusps behind the Ashtakavarga scorecard and the KP significators, and the sunrise that opens the panchanga day.","example":28.8944,"key":"latitude","kind":"number","max":90,"min":-90,"name":"latitude","required":true,"role":"location"},{"description":"Birth location longitude in decimal degrees. Affects local sidereal time for the natal cusps and the sunrise the reading is composed at.","example":76.5894,"key":"longitude","kind":"number","max":180,"min":-180,"name":"longitude","required":true,"role":"location"},{"default":5.5,"description":"Timezone: IANA name (e.g. \"Asia/Kolkata\", \"America/New_York\") OR decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). IANA strings are resolved to the DST-correct offset for the date being read. Interprets the birth time and the civil date below. Defaults to 5.5.","example":5.5,"key":"timezone","kind":"number","max":14,"min":-14,"name":"timezone","required":false,"role":"location"},{"description":"Civil date to read, in YYYY-MM-DD format. Defaults to today (UTC). The panchanga day it names runs from sunrise at the birth coordinates to the next sunrise, not from midnight, so a reading for this date covers the night that follows it.","example":"2026-06-21","fold":true,"key":"date","kind":"date","name":"date","required":false},{"default":"mean","description":"Lunar node type for Rahu and Ketu. \"mean\" uses the smooth mean node, which is the traditional Vedic default and what printed panchangs use. \"true\" uses the osculating node, which swings up to 1.5 degrees either side of mean and can therefore move a node into a different rashi and change its gochara house. Defaults to \"mean\".","enum":["mean","true"],"example":"mean","fold":true,"key":"nodeType","kind":"tiles","name":"nodeType","required":false},{"default":"general","description":"Which signification vocabulary the houseThemes map returns. \"general\" gives the classical bhava significations (self, wealth, siblings, home, and so on). \"finance\" gives the money reading of the same twelve bhavas, so house 2 returns income and savings, 5 speculation and risk appetite, 8 sudden money and leverage, 11 gains and profits, and 12 expenses and capital outflow. Use \"finance\" for wealth, income, business and market timing questions in Krishnamurti Paddhati, where the significator house groups 2, 6, 10, 11 for earned income and 5, 8, 11 for speculation are read against a running dasha. Defaults to \"general\".","enum":["general","finance"],"example":"general","fold":true,"inQuery":true,"key":"focus","kind":"tiles","name":"focus","required":false}],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/vedic-astrology/daily","title":"Daily Reading"},"getWeeklyHoroscope":{"fields":[{"description":"Zodiac sign, case-insensitive (e.g., aries, Aries, ARIES all work).","enum":["aries","taurus","gemini","cancer","leo","virgo","libra","scorpio","sagittarius","capricorn","aquarius","pisces"],"example":"aries","inQuery":false,"key":"sign","kind":"tiles","name":"sign","required":true},{"description":"Any date inside the target week, in YYYY-MM-DD format. The forecast covers the Monday to Sunday week containing it. Defaults to the current period in the timezone parameter.","example":"2026-04-03","fold":true,"inQuery":true,"key":"date","kind":"date","name":"date","required":false},{"city":true,"description":"Selects which period counts as current when date is omitted. Defaults to UTC, so the forecast rolls over at 00:00 UTC on each Monday. Pass the timezone of the end user to roll over on their local clock instead. Ignored when date is set. Accepts an IANA name (e.g. \"America/New_York\"), decimal hours (e.g. 5.5 for IST), or a fixed UTC offset (e.g. \"-05:00\").","example":"America/New_York","fold":true,"inQuery":true,"key":"timezone","kind":"text","name":"timezone","required":false,"viewerZone":true}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":false,"path":"/astrology/horoscope/{sign}/weekly","title":"Weekly horoscope by zodiac sign"},"getYearlyHoroscope":{"fields":[{"description":"Zodiac sign, case-insensitive (e.g., aries, Aries, ARIES all work).","enum":["aries","taurus","gemini","cancer","leo","virgo","libra","scorpio","sagittarius","capricorn","aquarius","pisces"],"example":"aries","inQuery":false,"key":"sign","kind":"tiles","name":"sign","required":true},{"description":"Calendar year to forecast, 1900 to 2100. Defaults to the current year in the timezone parameter.","example":2026,"fold":true,"inQuery":true,"key":"year","kind":"number","max":2100,"min":1900,"name":"year","required":false},{"city":true,"description":"Selects which year counts as current when year is omitted. Defaults to UTC, so the forecast rolls over at 00:00 UTC on January 1. Pass the timezone of the end user to roll over on their local clock instead. Ignored when year is set. Accepts an IANA name (e.g. \"America/New_York\"), decimal hours (e.g. 5.5 for IST), or a fixed UTC offset (e.g. \"-05:00\").","example":"America/New_York","fold":true,"inQuery":true,"key":"timezone","kind":"text","name":"timezone","required":false,"viewerZone":true}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":false,"path":"/astrology/horoscope/{sign}/yearly","title":"Yearly horoscope by zodiac sign"},"getYoga":{"fields":[{"description":"Yoga identifier (lowercase, hyphenated)","enum":["gajakesari","sunapha","anapha","dhurdhura","kemadruma","chandramangala","adhi","chatussagara","vasumathi","rajalakshana","vanchanachorabheethi","sakata","amala","parvata","kahala","vesi","vasi","obhayachari","hamsa","malavya","sasa","ruchaka","bhadra","budhaaditya","mahabhagya","pushkala","lakshmi","gauri","bharathi","chapa","sreenatha","lagnamalika","dhanamalika","vikramamalika","sukhamalika","putramalika","satrumalika","kalatramalika","randhramalika","bhagyamalika","karmamalika","labhamalika","vrayamalika","sankha","bheri","mridanga","parijatha","gaja","kalanidhi","amsavatara","hariharabrahma","kusuma","matsya","kurma","devendra","makuta","chandika","jaya","vidyut","gandharva","siva","vishnu","brahma","indra","ravi","garuda","go","gola","thrilochana","kulavardhana","yupa","ishu","sakti","danda","nav","kuta","chhatra","chapa-2","ardhachandra","chandra","gada","sakata-2","vihaga","vajra","yava","sringhataka","hala","kamala","vapee","samudra","vallaki","damni","pasa","kedara","sula","yuga","gola-2","rajju","musala","nala","srik","mala","sarpa","duryoga","daridra","harsha","sarala","vimala","sareerasoukhya","dehapushti","dehakashta","rogagrastha","krisanga","krisanga-2","dehasthoulya","dehasthoulya-2","dehasthoulya-3","sadasanchara","dhana","dhana-2","dhana-3","dhana-4","dhana-5","dhana-6","dhana-7","dhana-8","dhana-9","dhana-10","dhana-11","bahudravyarjana","swaveeryaddhana","swaveeryaddhana-2","swaveeryaddhana-3","madhyavayasidhana","anthyavayasidhana","balyadhana","bhratrumooladdhanaprapti","bhratrumooladdhanaprapti-2","matrumooladdhana","putramooladdhana","satrumooladdhana","kalatramooladdhana","amarananthadhana","ayatnadhanalabha","daridra-2","daridra-3","daridra-4","daridra-5","daridra-6","daridra-7","daridra-8","daridra-9","daridra-10","daridra-11","yukthisamanwithavagmi","yukthisamanwithavagmi-2","parihasaka","asatyavadi","jada","bhaskara","marud","saraswathi","budha","mooka","netranasa","andha","sumukha","sumukha-2","durmukha","durmukha-2","bhojanasoukhya","annadana","parannabhojana","sraddhannabhuktha","sarpaganda","vakchalana","vishaprayoga","bhratruvriddhi","sodaranasa","ekabhagini","dwadasasahodara","sapthasankhyasahodara","parakrama","yuddhapraveena","yuddhatpoorvadridhachitta","yuddhatpaschaddrudha","satkathadisravana","uttamagriha","vichitrasaudhaprakara","ayatnagrihaprapta","ayatnagrihaprapta-2","grihanasa","grihanasa-2","bandhupujya","bandhupujya-2","bandhubhisthyaktha","matrudeerghayur","matrudeerghayur-2","matrunasa","matrunasa-2","matrugami","sahodareesangama","kapata","kapata-2","kapata-3","nishkapata","nishkapata-2","matrusatrutwa","matrusneha","vahana","vahana-2","anapathya","sarpasapa","sarpasapa-2","sarpasapa-3","sarpasapa-4","pitrusapasutakshaya","matrusapasutakshaya","bhratrusapasutakshaya","pretasapa","bahuputra","bahuputra-2","dattaputra","dattaputra-2","aputra","ekaputra","suputra","kalanirdesatputra","kalanirdesatputra-2","kalanirdesatputranasa","kalanirdesatputranasa-2","buddhimaturya","theevrabuddhi","buddhijada","thrikalagnana","putrasukha","jara","jarajaputra","bahustree","satkalatra","bhagachumbana","bhagya","jananatpurvampitrumarana","dhatrutwa","apakeerti","raja","raja-2","raja-3","raja-4","raja-5","raja-6","raja-7","raja-8","raja-9","raja-10","raja-11","raja-12","raja-13","raja-14","raja-15","raja-16","raja-17","raja-18","raja-19","galakarna","vrana","sisnavyadhi","kalatrashanda","kushtaroga","kushtaroga-2","kshayaroga","bandhana","karascheda","sirachcheda","durmarana","yuddhemarana","sanghatakamarana","sanghatakamarana-2","peenasaroga","pittaroga","vikalangapatni","putrakalatraheena","bharyasahavyabhichara","vamsacheda","guhyaroga","angaheena","swetakushta","pisachagrastha","andha-2","andha-3","vatharoga","matibhramana","matibhramana-2","matibhramana-3","matibhramana-4","khalwata","nishturabhashi","rajabhrashta","raja-20","raja-21","gohanta"],"example":"gajakesari","inQuery":false,"key":"id","kind":"select","label":"Yoga","name":"id","required":true}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":false,"path":"/vedic-astrology/yoga/{id}","title":"Get yoga details by ID"},"getZodiacAnimal":{"fields":[{"description":"Animal id, case-insensitive and punctuation-insensitive. One of rat, ox, tiger, rabbit, dragon, snake, horse, goat, monkey, rooster, dog, pig. The sheep and the ram are the same animal as the goat and resolve to goat.","enum":["rat","ox","tiger","rabbit","dragon","snake","horse","goat","monkey","rooster","dog","pig"],"example":"rat","inQuery":false,"key":"id","kind":"tiles","label":"Animal","name":"id","required":true}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":false,"path":"/chinese-astrology/zodiac/animals/{id}","title":"Get one Chinese zodiac animal"},"getZodiacCompatibility":{"fields":[{"description":"First animal id, case-insensitive. One of rat, ox, tiger, rabbit, dragon, snake, horse, goat, monkey, rooster, dog, pig.","enum":["rat","ox","tiger","rabbit","dragon","snake","horse","goat","monkey","rooster","dog","pig"],"example":"rat","inQuery":false,"key":"sign1","kind":"tiles","name":"sign1","required":true},{"description":"Second animal id, case-insensitive. The relation is symmetric, so swapping the two returns the same relationship and the same score, with the reading written from the first sign point of view.","enum":["rat","ox","tiger","rabbit","dragon","snake","horse","goat","monkey","rooster","dog","pig"],"example":"dragon","inQuery":false,"key":"sign2","kind":"tiles","name":"sign2","required":true}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":false,"path":"/chinese-astrology/zodiac/compatibility/{sign1}/{sign2}","title":"Chinese zodiac compatibility"},"getZodiacSign":{"fields":[{"description":"Sign ID (lowercase, e.g., aries, taurus) or display name (case-insensitive, e.g., Aries, TAURUS).","example":"aries","inQuery":false,"key":"id","kind":"text","name":"id","required":true,"source":{"lang":true,"path":"/astrology/signs"}}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":false,"path":"/astrology/signs/{id}","title":"Get zodiac sign details"},"listAngelNumbers":{"fields":[{"default":20,"description":"Maximum items to return per page. Range: 1-50, default 20.","example":20,"inQuery":true,"key":"limit","kind":"number","max":50,"min":1,"name":"limit","required":false,"role":"hidden-default"},{"default":0,"description":"Number of items to skip for pagination. Default 0.","example":0,"inQuery":true,"key":"offset","kind":"number","min":0,"name":"offset","required":false,"role":"hidden-default"},{"description":"Filter results by angel number pattern type. \"repeating\" returns numbers like 111, 444, 7777. \"sequential\" returns patterns like 1234. \"mirror\" returns palindrome or alternating patterns like 1212, 717. \"master\" returns 11, 22, 33. \"root\" returns single digits 0-9. \"compound\" returns mixed sequences with no pure pattern like 911, 1122.","enum":["repeating","sequential","mirror","master","root","compound"],"example":"repeating","inQuery":true,"key":"type","kind":"tiles","name":"type","required":false}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":true,"path":"/angel-numbers/numbers","title":"List all angel numbers"},"listAvasthas":{"fields":[{"description":"Return only the states of one system: \"baladi\" (5), \"jagradadi\" (3) or \"deeptadi\" (9). Omit for all 17.","enum":["baladi","jagradadi","deeptadi"],"example":"deeptadi","inQuery":true,"key":"system","kind":"tiles","name":"system","required":false}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":true,"path":"/vedic-astrology/avasthas","title":"List all 17 avastha states"},"listAztecDaySigns":{"fields":[{"default":20,"description":"Maximum items to return per page. Range: 1-20, default 20.","example":20,"inQuery":true,"key":"limit","kind":"number","max":20,"min":1,"name":"limit","required":false,"role":"hidden-default"},{"default":0,"description":"Number of items to skip for pagination. Default 0.","example":0,"inQuery":true,"key":"offset","kind":"number","min":0,"name":"offset","required":false,"role":"hidden-default"}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":true,"path":"/mesoamerican-astrology/aztec/day-signs","title":"List the 20 Aztec day signs"},"listAztecTrecenas":{"fields":[{"default":20,"description":"Maximum items to return per page. Range: 1-20, default 20.","example":20,"inQuery":true,"key":"limit","kind":"number","max":20,"min":1,"name":"limit","required":false,"role":"hidden-default"},{"default":0,"description":"Number of items to skip for pagination. Default 0.","example":0,"inQuery":true,"key":"offset","kind":"number","min":0,"name":"offset","required":false,"role":"hidden-default"}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":true,"path":"/mesoamerican-astrology/aztec/trecenas","title":"List the 20 Aztec trecenas"},"listBaguaSectors":{"fields":[{"default":9,"description":"Maximum items to return per page. Range: 1-9, default 9.","example":9,"inQuery":true,"key":"limit","kind":"number","max":9,"min":1,"name":"limit","required":false,"role":"hidden-default"},{"default":0,"description":"Number of items to skip for pagination. Default 0.","example":0,"inQuery":true,"key":"offset","kind":"number","min":0,"name":"offset","required":false,"role":"hidden-default"}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":true,"path":"/feng-shui/bagua","title":"List Bagua sectors"},"listCards":{"fields":[{"default":20,"description":"Maximum items to return per page. Range: 1-100, default 20.","example":20,"inQuery":true,"key":"limit","kind":"number","max":100,"min":1,"name":"limit","required":false,"role":"hidden-default"},{"default":0,"description":"Number of items to skip for pagination. Default 0.","example":0,"inQuery":true,"key":"offset","kind":"number","min":0,"name":"offset","required":false,"role":"hidden-default"},{"description":"Filter by arcana type. Major arcana (0-21) represents life lessons and spiritual themes. Minor arcana (Ace-King in 4 suits) represents daily situations and practical matters.","enum":["major","minor"],"example":"major","inQuery":true,"key":"arcana","kind":"tiles","name":"arcana","required":false},{"description":"Filter minor arcana by suit. Cups=emotions/relationships, Wands=creativity/passion, Swords=intellect/conflict, Pentacles=material/finances. Only applies to minor arcana cards.","disabledWhen":{"field":"arcana","value":"major"},"enum":["cups","wands","swords","pentacles"],"example":"cups","inQuery":true,"key":"suit","kind":"tiles","name":"suit","required":false},{"description":"Filter by card number. Major Arcana: 0 (The Fool) through 21 (The World). Minor Arcana: 1 (Ace) through 14 (King). Combine with arcana or suit filters for precise results.","example":1,"inQuery":true,"key":"number","kind":"number","max":21,"min":0,"name":"number","required":false}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":true,"path":"/tarot/cards","title":"List all 78 tarot cards"},"listCountries":{"fields":[{"default":50,"description":"Maximum items to return per page. Range: 1-250, default 50.","example":50,"inQuery":true,"key":"limit","kind":"number","max":250,"min":1,"name":"limit","required":false,"role":"hidden-default"},{"default":0,"description":"Number of items to skip for pagination. Default 0.","example":0,"inQuery":true,"key":"offset","kind":"number","min":0,"name":"offset","required":false,"role":"hidden-default"}],"groups":[{}],"hasLang":false,"method":"GET","opensOnLoad":true,"path":"/location/countries","title":"List all countries"},"listCrystalColors":{"fields":[],"groups":[],"hasLang":true,"method":"GET","opensOnLoad":true,"path":"/crystals/colors","title":"List crystal colors"},"listCrystalPlanets":{"fields":[],"groups":[],"hasLang":true,"method":"GET","opensOnLoad":true,"path":"/crystals/planets","title":"List crystal planets"},"listCrystals":{"fields":[{"description":"Filter by chakra association, case-insensitive. Valid values: Root, Sacral, Solar Plexus, Heart, Throat, Third Eye, Crown.","enum":["Root","Sacral","Solar Plexus","Heart","Throat","Third Eye","Crown"],"example":"Heart","inQuery":true,"key":"chakra","kind":"tiles","name":"chakra","required":false},{"description":"Filter by zodiac sign, case-insensitive. Valid values: aries, taurus, gemini, cancer, leo, virgo, libra, scorpio, sagittarius, capricorn, aquarius, pisces.","enum":["aries","taurus","gemini","cancer","leo","virgo","libra","scorpio","sagittarius","capricorn","aquarius","pisces"],"example":"pisces","inQuery":true,"key":"zodiac","kind":"tiles","name":"zodiac","required":false},{"description":"Filter by elemental association, case-insensitive. Valid values: Earth, Water, Fire, Air, Storm.","enum":["Earth","Water","Fire","Air","Storm"],"example":"Water","inQuery":true,"key":"element","kind":"tiles","name":"element","required":false},{"description":"Filter by crystal color (partial match, case-insensitive). E.g., \"pink\", \"green\", \"blue\", \"purple\". Use GET /colors for valid values.","example":"pink","inQuery":true,"key":"color","kind":"text","name":"color","required":false,"source":{"lang":true,"path":"/crystals/colors"}},{"description":"Filter by planetary association (partial match, case-insensitive). E.g., \"Venus\", \"Moon\", \"Jupiter\". Use GET /planets for valid values.","example":"Venus","inQuery":true,"key":"planet","kind":"text","name":"planet","required":false,"source":{"lang":true,"path":"/crystals/planets"}},{"default":20,"description":"Maximum items to return per page. Range: 1-100, default 20.","example":20,"inQuery":true,"key":"limit","kind":"number","max":100,"min":1,"name":"limit","required":false,"role":"hidden-default"},{"default":0,"description":"Number of items to skip for pagination. Default 0.","example":0,"inQuery":true,"key":"offset","kind":"number","min":0,"name":"offset","required":false,"role":"hidden-default"}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":true,"path":"/crystals","title":"List all crystals"},"listDevatas":{"fields":[{"default":45,"description":"Maximum items to return per page. Range: 1-45, default 45.","example":45,"inQuery":true,"key":"limit","kind":"number","max":45,"min":1,"name":"limit","required":false,"role":"hidden-default"},{"default":0,"description":"Number of items to skip for pagination. Default 0.","example":0,"inQuery":true,"key":"offset","kind":"number","min":0,"name":"offset","required":false,"role":"hidden-default"}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":true,"path":"/vastu/devatas","title":"List the 45 devatas"},"listDikpalaDirections":{"fields":[{"default":8,"description":"Maximum items to return per page. Range: 1-8, default 8.","example":8,"inQuery":true,"key":"limit","kind":"number","max":8,"min":1,"name":"limit","required":false,"role":"hidden-default"},{"default":0,"description":"Number of items to skip for pagination. Default 0.","example":0,"inQuery":true,"key":"offset","kind":"number","min":0,"name":"offset","required":false,"role":"hidden-default"}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":true,"path":"/vastu/directions","title":"List the eight directions"},"listDoshas":{"fields":[{"default":3,"description":"Maximum items to return per page. Range: 1-3, default 3.","example":3,"inQuery":true,"key":"limit","kind":"number","max":3,"min":1,"name":"limit","required":false,"role":"hidden-default"},{"default":0,"description":"Number of items to skip for pagination. Default 0.","example":0,"inQuery":true,"key":"offset","kind":"number","min":0,"name":"offset","required":false,"role":"hidden-default"}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":true,"path":"/ayurveda/doshas","title":"List the three doshas"},"listFiveElements":{"fields":[{"default":5,"description":"Maximum items to return per page. Range: 1-5, default 5.","example":5,"inQuery":true,"key":"limit","kind":"number","max":5,"min":1,"name":"limit","required":false,"role":"hidden-default"},{"default":0,"description":"Number of items to skip for pagination. Default 0.","example":0,"inQuery":true,"key":"offset","kind":"number","min":0,"name":"offset","required":false,"role":"hidden-default"}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":true,"path":"/chinese-astrology/elements","title":"List the five elements"},"listFlyingStars":{"fields":[{"default":9,"description":"Maximum items to return per page. Range: 1-9, default 9.","example":9,"inQuery":true,"key":"limit","kind":"number","max":9,"min":1,"name":"limit","required":false,"role":"hidden-default"},{"default":0,"description":"Number of items to skip for pagination. Default 0.","example":0,"inQuery":true,"key":"offset","kind":"number","min":0,"name":"offset","required":false,"role":"hidden-default"}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":true,"path":"/feng-shui/flying-stars/stars","title":"List the nine flying stars"},"listGematriaCiphers":{"fields":[],"groups":[],"hasLang":true,"method":"GET","opensOnLoad":true,"path":"/kabbalah/ciphers","title":"List gematria ciphers"},"listGunas":{"fields":[{"default":10,"description":"Maximum items to return per page. Range: 1-10, default 10.","example":10,"inQuery":true,"key":"limit","kind":"number","max":10,"min":1,"name":"limit","required":false,"role":"hidden-default"},{"default":0,"description":"Number of items to skip for pagination. Default 0.","example":0,"inQuery":true,"key":"offset","kind":"number","min":0,"name":"offset","required":false,"role":"hidden-default"}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":true,"path":"/ayurveda/qualities","title":"List the twenty qualities"},"listHaabMonths":{"fields":[{"default":19,"description":"Maximum items to return per page. Range: 1-19, default 19.","example":19,"inQuery":true,"key":"limit","kind":"number","max":19,"min":1,"name":"limit","required":false,"role":"hidden-default"},{"default":0,"description":"Number of items to skip for pagination. Default 0.","example":0,"inQuery":true,"key":"offset","kind":"number","min":0,"name":"offset","required":false,"role":"hidden-default"}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":true,"path":"/mesoamerican-astrology/mayan/haab-months","title":"List the 19 Haab periods"},"listHebrewLetters":{"fields":[{"default":"sefer-yetzirah-gra","description":"Which reading assigns the element, planet or sign to each letter. The seven double letters are the contested column and the four readings genuinely disagree on them; the twelve simple letters run in natural zodiacal order in all four. The golden-dawn member does NOT exchange He and Tzade, which is a later change from a different author.","enum":["sefer-yetzirah-gra","sefer-yetzirah-short","sefer-yetzirah-saadia","golden-dawn"],"example":"sefer-yetzirah-gra","fold":true,"inQuery":true,"key":"letterAttribution","kind":"tiles","name":"letterAttribution","required":false}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":true,"path":"/kabbalah/letters","title":"List the Hebrew letters"},"listHexagrams":{"fields":[{"default":20,"description":"Maximum items to return per page. Range: 1-64, default 20.","example":20,"inQuery":true,"key":"limit","kind":"number","max":64,"min":1,"name":"limit","required":false,"role":"hidden-default"},{"default":0,"description":"Number of items to skip for pagination. Default 0.","example":0,"inQuery":true,"key":"offset","kind":"number","min":0,"name":"offset","required":false,"role":"hidden-default"}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":true,"path":"/iching/hexagrams","title":"List all 64 hexagrams"},"listLanguages":{"fields":[],"groups":[],"hasLang":false,"method":"GET","opensOnLoad":true,"path":"/languages","title":"List supported response languages"},"listMayanDaySigns":{"fields":[{"default":"madrid-codex","description":"Which reading of the world direction and colour to serve for a day sign. The two published assignments differ by exactly one quarter turn on all twenty signs, so neither is a rounding of the other and a silent pick would be a school choice. \"madrid-codex\" is the codex reading and the default; \"landa\" is the sixteenth century assignment recorded beside it.","enum":["madrid-codex","landa"],"example":"madrid-codex","fold":true,"inQuery":true,"key":"directionScheme","kind":"tiles","name":"directionScheme","required":false},{"default":20,"description":"Maximum items to return per page. Range: 1-20, default 20.","example":20,"inQuery":true,"key":"limit","kind":"number","max":20,"min":1,"name":"limit","required":false,"role":"hidden-default"},{"default":0,"description":"Number of items to skip for pagination. Default 0.","example":0,"inQuery":true,"key":"offset","kind":"number","min":0,"name":"offset","required":false,"role":"hidden-default"}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":true,"path":"/mesoamerican-astrology/mayan/day-signs","title":"List the 20 Mayan day signs"},"listNakshatras":{"fields":[],"groups":[],"hasLang":true,"method":"GET","opensOnLoad":true,"path":"/vedic-astrology/nakshatras","title":"List all 27 Nakshatras"},"listNinePeriods":{"fields":[{"description":"Date to resolve the current period for, in YYYY-MM-DD format. Defaults to today in UTC. Useful for asking which period a building was completed in. A date landing exactly on the Li Chun day a period opens is placed in the outgoing period.","example":"2026-08-23","inQuery":true,"key":"date","kind":"date","name":"date","required":false}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":true,"path":"/feng-shui/periods","title":"List the nine periods"},"listPlanetMeanings":{"fields":[],"groups":[],"hasLang":true,"method":"GET","opensOnLoad":true,"path":"/astrology/planet-meanings","title":"Get all planet meanings"},"listRasas":{"fields":[{"default":6,"description":"Maximum items to return per page. Range: 1-6, default 6.","example":6,"inQuery":true,"key":"limit","kind":"number","max":6,"min":1,"name":"limit","required":false,"role":"hidden-default"},{"default":0,"description":"Number of items to skip for pagination. Default 0.","example":0,"inQuery":true,"key":"offset","kind":"number","min":0,"name":"offset","required":false,"role":"hidden-default"}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":true,"path":"/ayurveda/tastes","title":"List the six tastes"},"listRashis":{"fields":[],"groups":[],"hasLang":true,"method":"GET","opensOnLoad":true,"path":"/vedic-astrology/rashis","title":"List all 12 Rashis"},"listShemNames":{"fields":[{"default":20,"description":"Maximum items to return per page. Range: 1-72, default 20.","example":20,"inQuery":true,"key":"limit","kind":"number","max":72,"min":1,"name":"limit","required":false,"role":"hidden-default"},{"default":0,"description":"Number of items to skip for pagination. Default 0.","example":0,"inQuery":true,"key":"offset","kind":"number","min":0,"name":"offset","required":false,"role":"hidden-default"},{"description":"Ecliptic longitude in degrees, 0 inclusive to 360 exclusive, measured from 0 Aries. Returns the single name governing that degree instead of the list. 360 is rejected because it is the same point as 0 and the arcs are half open at the top.","example":131.18,"inQuery":true,"key":"longitude","kind":"number","max":360,"min":0,"name":"longitude","required":false}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":true,"path":"/kabbalah/names","title":"List the 72 names"},"listSolarTerms":{"fields":[{"description":"Solar year, 1900 to 2100. The year opens at Li Chun rather than on 1 January, so its last two terms fall in the following January.","example":2026,"inQuery":false,"key":"year","kind":"number","max":2100,"min":1900,"name":"year","required":true}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":false,"path":"/chinese-astrology/calendar/solar-terms/{year}","title":"List the 24 solar terms"},"listTrecenas":{"fields":[{"default":20,"description":"Maximum items to return per page. Range: 1-20, default 20.","example":20,"inQuery":true,"key":"limit","kind":"number","max":20,"min":1,"name":"limit","required":false,"role":"hidden-default"},{"default":0,"description":"Number of items to skip for pagination. Default 0.","example":0,"inQuery":true,"key":"offset","kind":"number","min":0,"name":"offset","required":false,"role":"hidden-default"}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":true,"path":"/mesoamerican-astrology/mayan/trecenas","title":"List the 20 Mayan trecenas"},"listTrigrams":{"fields":[],"groups":[],"hasLang":true,"method":"GET","opensOnLoad":true,"path":"/iching/trigrams","title":"List all 8 trigrams"},"listYogas":{"fields":[{"description":"Filter the catalog to one Nabhasa family: asraya (3), dala (2), akriti (20) or sankhya (7). Omit for the full catalog. `classical` is accepted but matches nothing here, because it is a detection-verdict value for single-combination yogas rather than a catalog grouping.","enum":["classical","asraya","dala","akriti","sankhya"],"example":"akriti","inQuery":true,"key":"family","kind":"tiles","name":"family","required":false}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":true,"path":"/vedic-astrology/yoga","title":"List all planetary yogas"},"listZodiacAnimals":{"fields":[{"default":12,"description":"Maximum items to return per page. Range: 1-12, default 12.","example":12,"inQuery":true,"key":"limit","kind":"number","max":12,"min":1,"name":"limit","required":false,"role":"hidden-default"},{"default":0,"description":"Number of items to skip for pagination. Default 0.","example":0,"inQuery":true,"key":"offset","kind":"number","min":0,"name":"offset","required":false,"role":"hidden-default"}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":true,"path":"/chinese-astrology/zodiac/animals","title":"List the 12 Chinese zodiac animals"},"listZodiacSigns":{"fields":[],"groups":[],"hasLang":true,"method":"GET","opensOnLoad":true,"path":"/astrology/signs","title":"Get all zodiac signs"},"lookupAuspiciousDays":{"fields":[{"description":"Activity to choose a date for. One of wedding, travel, moving-house, opening-business, signing-contracts, construction, groundbreaking, burial, medical-treatment, praying. Matching folds case and punctuation, so moving-house and MOVING_HOUSE both resolve.","enum":["wedding","travel","moving-house","opening-business","signing-contracts","construction","groundbreaking","burial","medical-treatment","praying"],"example":"wedding","key":"activity","kind":"tiles","name":"activity","required":true},{"description":"First date of the range to search, inclusive.","example":"2026-03-01","key":"startDate","kind":"date","name":"startDate","required":true},{"description":"Last date of the range to search, inclusive. The range may not exceed 93 days.","example":"2026-04-30","key":"endDate","kind":"date","name":"endDate","required":true},{"description":"Zodiac animal to protect. Days that clash with this animal are dropped from the results, which is how a date is chosen around the people attending rather than in the abstract. One of rat, ox, tiger, rabbit, dragon, snake, horse, goat, monkey, rooster, dog, pig.","enum":["rat","ox","tiger","rabbit","dragon","snake","horse","goat","monkey","rooster","dog","pig"],"example":"rat","fold":true,"key":"avoidAnimal","kind":"tiles","name":"avoidAnimal","required":false}],"groups":[{}],"hasLang":true,"method":"POST","opensOnLoad":false,"path":"/chinese-astrology/calendar/auspicious-days","title":"Find auspicious days"},"lookupHexagram":{"fields":[{"description":"Six-digit binary pattern (0=yin/broken, 1=yang/solid) from bottom to top.","example":"111111","inQuery":true,"key":"lines","kind":"text","name":"lines","required":true}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":false,"path":"/iching/hexagrams/lookup","title":"Lookup hexagram by line pattern"},"searchCities":{"fields":[{"description":"Place to search for, written the way a person would. Accepts a bare city (berlin), a city plus country (berlin germany), a comma-qualified place (richfield, utah), a fully qualified place (richfield, utah, united states), or a historic name (bombay, peking, constantinople). Commas are optional, and a qualifier the dataset spells differently, such as USA for United States, still resolves. Matched against city name, alternate names, state or province, and country. Add the state or country whenever the name is common, since that is what separates the six Springfields, and Richfield, Utah from Richfield, Minnesota.","example":"berlin","inQuery":true,"key":"q","kind":"text","name":"q","required":true},{"default":10,"description":"Maximum items to return per page. Range: 1-50, default 10.","example":10,"inQuery":true,"key":"limit","kind":"number","max":50,"min":1,"name":"limit","required":false,"role":"hidden-default"},{"default":0,"description":"Number of items to skip for pagination. Default 0.","example":0,"inQuery":true,"key":"offset","kind":"number","min":0,"name":"offset","required":false,"role":"hidden-default"}],"groups":[{}],"hasLang":false,"method":"GET","opensOnLoad":false,"path":"/location/search","title":"Search cities worldwide"},"searchCrystals":{"fields":[{"description":"Search query (2-50 characters). Matches against crystal names, keywords, descriptions, and meaning fields. Case-insensitive partial matching.","example":"love","inQuery":true,"key":"q","kind":"text","name":"q","required":true},{"default":20,"description":"Maximum items to return per page. Range: 1-50, default 20.","example":20,"inQuery":true,"key":"limit","kind":"number","max":50,"min":1,"name":"limit","required":false,"role":"hidden-default"},{"default":0,"description":"Number of items to skip for pagination. Default 0.","example":0,"inQuery":true,"key":"offset","kind":"number","min":0,"name":"offset","required":false,"role":"hidden-default"}],"groups":[{}],"hasLang":true,"method":"GET","opensOnLoad":false,"path":"/crystals/search","title":"Search crystals"},"searchDreamSymbols":{"fields":[{"description":"Search query to match against symbol names and meanings. Case-insensitive.","example":"water","inQuery":true,"key":"q","kind":"text","name":"q","required":false},{"description":"Filter symbols by starting letter (a-z). Case-insensitive.","example":"a","inQuery":true,"key":"letter","kind":"text","name":"letter","required":false,"source":{"path":"/dreams/symbols/letters"}},{"default":20,"description":"Maximum items to return per page. Range: 1-50, default 20.","example":20,"inQuery":true,"key":"limit","kind":"number","max":50,"min":1,"name":"limit","required":false,"role":"hidden-default"},{"default":0,"description":"Number of items to skip for pagination. Default 0.","example":0,"inQuery":true,"key":"offset","kind":"number","min":0,"name":"offset","required":false,"role":"hidden-default"}],"groups":[{}],"hasLang":false,"method":"GET","opensOnLoad":true,"path":"/dreams/symbols","title":"List and search dream symbols"}},"version":1}