@roxyapi/ui 0.51.0 → 0.51.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/components-catalog.json +153 -153
- package/dist/cdn/components/endpoint-form.js +4 -4
- package/dist/cdn/components/endpoint-form.js.map +3 -3
- package/dist/cdn/roxy-ui.js +74 -74
- package/dist/cdn/roxy-ui.js.map +3 -3
- package/dist/components/endpoint-form.d.ts +3 -9
- package/dist/components/endpoint-form.d.ts.map +1 -1
- package/dist/components/endpoint-form.js +1 -1
- package/dist/components/endpoint-form.js.map +3 -3
- package/dist/forms/labels/de.json +1 -1
- package/dist/forms/labels/en.json +1 -1
- package/dist/forms/labels/es.json +1 -1
- package/dist/forms/labels/fr.json +1 -1
- package/dist/forms/labels/hi.json +1 -1
- package/dist/forms/labels/pt.json +1 -1
- package/dist/forms/labels/ru.json +1 -1
- package/dist/forms/labels/tr.json +1 -1
- package/dist/forms.json +1 -1
- package/dist/index.cjs +57 -57
- package/dist/index.cjs.map +3 -3
- package/dist/index.js +59 -59
- package/dist/index.js.map +3 -3
- package/dist/schemas/get--ayurveda-doshas-id.json +1 -1
- package/dist/schemas/get--chinese-astrology-zodiac-animals-id.json +1 -1
- package/dist/schemas/get--chinese-astrology-zodiac-id-daily.json +1 -1
- package/dist/schemas/get--feng-shui-bagua-id.json +1 -1
- package/dist/schemas/get--human-design-centers-id.json +1 -1
- package/dist/schemas/get--kabbalah-letters-id.json +1 -1
- package/dist/schemas/get--kabbalah-sephirot-id.json +1 -1
- package/dist/schemas/get--mesoamerican-astrology-aztec-day-signs-id.json +1 -1
- package/dist/schemas/get--mesoamerican-astrology-mayan-day-signs-id.json +1 -1
- package/dist/schemas/get--mesoamerican-astrology-mayan-haab-months-id.json +1 -1
- package/dist/schemas/get--vastu-devatas-id.json +1 -1
- package/dist/schemas/get--vastu-directions-id.json +1 -1
- package/dist/schemas/get--vedic-astrology-avasthas-id.json +1 -1
- package/dist/schemas/get--vedic-astrology-nakshatras-id.json +1 -1
- package/dist/schemas/get--vedic-astrology-rashis-id.json +1 -1
- package/dist/schemas/get--vedic-astrology-yoga-id.json +1 -1
- package/dist/schemas/post--astrology-compatibility-score.json +1 -1
- package/dist/schemas/post--astrology-composite-chart.json +1 -1
- package/dist/schemas/post--astrology-relocation-chart.json +1 -1
- package/dist/schemas/post--astrology-synastry.json +1 -1
- package/dist/schemas/post--astrology-transit-aspects.json +1 -1
- package/dist/schemas/post--astrology-transits.json +1 -1
- package/dist/schemas/post--biorhythm-compatibility.json +1 -1
- package/dist/schemas/post--chinese-astrology-bazi-compatibility.json +1 -1
- package/dist/schemas/post--forecast-digest.json +1 -1
- package/dist/schemas/post--forecast-significant-dates.json +1 -1
- package/dist/schemas/post--forecast-timeline.json +1 -1
- package/dist/schemas/post--forecast-transits.json +1 -1
- package/dist/schemas/post--human-design-connection.json +1 -1
- package/dist/schemas/post--human-design-penta.json +1 -1
- package/dist/schemas/post--human-design-transit.json +1 -1
- package/dist/schemas/post--mesoamerican-astrology-mayan-compatibility.json +1 -1
- package/dist/schemas/post--numerology-compatibility.json +1 -1
- package/dist/schemas/post--tarot-spreads-custom.json +1 -1
- package/dist/schemas/post--vastu-entrance.json +1 -1
- package/dist/schemas/post--vastu-mandala.json +1 -1
- package/dist/schemas/post--vastu-plot.json +1 -1
- package/dist/schemas/post--vastu-rooms.json +1 -1
- package/dist/schemas/post--vedic-astrology-compatibility-dashakoot.json +1 -1
- package/dist/schemas/post--vedic-astrology-compatibility-papasamyam.json +1 -1
- package/dist/schemas/post--vedic-astrology-compatibility.json +1 -1
- package/dist/schemas/post--vedic-astrology-kp-daily-finance.json +1 -1
- package/dist/styles/themes/practitioner.css +5 -5
- package/dist/utils/field-schema.d.ts +18 -0
- package/dist/utils/field-schema.d.ts.map +1 -1
- package/dist/version.d.ts +1 -1
- package/package.json +1 -1
- package/src/components/endpoint-form.ts +19 -25
- package/src/styles/themes/practitioner.css +5 -5
- package/src/utils/field-schema.ts +61 -20
- package/src/version.ts +1 -1
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Get one dosha","fields":[{"key":"id","name":"id","inQuery":false,"kind":"tiles","required":true,"description":"Dosha identifier, case-insensitive. One of vata, pitta or kapha.","enum":["vata","pitta","kapha"],"example":"vata"}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Get one dosha","fields":[{"key":"id","name":"id","inQuery":false,"kind":"tiles","required":true,"description":"Dosha identifier, case-insensitive. One of vata, pitta or kapha.","enum":["vata","pitta","kapha"],"example":"vata","label":"Dosha"}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Get one Chinese zodiac animal","fields":[{"key":"id","name":"id","inQuery":false,"kind":"tiles","required":true,"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"}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Get one Chinese zodiac animal","fields":[{"key":"id","name":"id","inQuery":false,"kind":"tiles","required":true,"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","label":"Animal"}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Daily Chinese zodiac reading","fields":[{"key":"id","name":"id","inQuery":false,"kind":"tiles","required":true,"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"},{"key":"date","name":"date","inQuery":true,"kind":"date","required":false,"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},{"key":"timezone","name":"timezone","inQuery":true,"kind":"text","required":false,"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","city":true,"fold":true}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Daily Chinese zodiac reading","fields":[{"key":"id","name":"id","inQuery":false,"kind":"tiles","required":true,"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","label":"Animal"},{"key":"date","name":"date","inQuery":true,"kind":"date","required":false,"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},{"key":"timezone","name":"timezone","inQuery":true,"kind":"text","required":false,"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","city":true,"fold":true}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Look up a Bagua sector","fields":[{"key":"id","name":"id","inQuery":false,"kind":"tiles","required":true,"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"}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Look up a Bagua sector","fields":[{"key":"id","name":"id","inQuery":false,"kind":"tiles","required":true,"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","label":"Life area"}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Look up a Human Design center by id","fields":[{"key":"id","name":"id","inQuery":false,"kind":"tiles","required":true,"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"}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Look up a Human Design center by id","fields":[{"key":"id","name":"id","inQuery":false,"kind":"tiles","required":true,"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","label":"Center"}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Get one Hebrew letter","fields":[{"key":"id","name":"id","inQuery":false,"kind":"select","required":true,"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"},{"key":"letterAttribution","name":"letterAttribution","inQuery":true,"kind":"tiles","required":false,"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"],"default":"sefer-yetzirah-gra","example":"sefer-yetzirah-gra","fold":true}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Get one Hebrew letter","fields":[{"key":"id","name":"id","inQuery":false,"kind":"select","required":true,"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","label":"Letter"},{"key":"letterAttribution","name":"letterAttribution","inQuery":true,"kind":"tiles","required":false,"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"],"default":"sefer-yetzirah-gra","example":"sefer-yetzirah-gra","fold":true}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Get one sephirah","fields":[{"key":"id","name":"id","inQuery":false,"kind":"tiles","required":true,"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"},{"key":"sephirotSystem","name":"sephirotSystem","inQuery":true,"kind":"tiles","required":false,"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"],"default":"classical","example":"classical","fold":true},{"key":"letterAttribution","name":"letterAttribution","inQuery":true,"kind":"tiles","required":false,"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"],"default":"sefer-yetzirah-gra","example":"sefer-yetzirah-gra","fold":true}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Get one sephirah","fields":[{"key":"id","name":"id","inQuery":false,"kind":"tiles","required":true,"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","label":"Sephirah"},{"key":"sephirotSystem","name":"sephirotSystem","inQuery":true,"kind":"tiles","required":false,"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"],"default":"classical","example":"classical","fold":true},{"key":"letterAttribution","name":"letterAttribution","inQuery":true,"kind":"tiles","required":false,"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"],"default":"sefer-yetzirah-gra","example":"sefer-yetzirah-gra","fold":true}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Get one Aztec day sign","fields":[{"key":"id","name":"id","inQuery":false,"kind":"select","required":true,"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"}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Get one Aztec day sign","fields":[{"key":"id","name":"id","inQuery":false,"kind":"select","required":true,"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","label":"Day sign"}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Get one Mayan day sign","fields":[{"key":"id","name":"id","inQuery":false,"kind":"select","required":true,"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"},{"key":"directionScheme","name":"directionScheme","inQuery":true,"kind":"tiles","required":false,"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"],"default":"madrid-codex","example":"madrid-codex","fold":true}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Get one Mayan day sign","fields":[{"key":"id","name":"id","inQuery":false,"kind":"select","required":true,"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","label":"Day sign"},{"key":"directionScheme","name":"directionScheme","inQuery":true,"kind":"tiles","required":false,"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"],"default":"madrid-codex","example":"madrid-codex","fold":true}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Get one Haab period","fields":[{"key":"id","name":"id","inQuery":false,"kind":"select","required":true,"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"}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Get one Haab period","fields":[{"key":"id","name":"id","inQuery":false,"kind":"select","required":true,"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","label":"Haab period"}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Look up one devata","fields":[{"key":"id","name":"id","inQuery":false,"kind":"select","required":true,"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"}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Look up one devata","fields":[{"key":"id","name":"id","inQuery":false,"kind":"select","required":true,"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","label":"Devata"}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Look up one direction","fields":[{"key":"id","name":"id","inQuery":false,"kind":"tiles","required":true,"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"}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Look up one direction","fields":[{"key":"id","name":"id","inQuery":false,"kind":"tiles","required":true,"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","label":"Direction"}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Get avastha by ID","fields":[{"key":"id","name":"id","inQuery":false,"kind":"select","required":true,"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"}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Get avastha by ID","fields":[{"key":"id","name":"id","inQuery":false,"kind":"select","required":true,"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","label":"Avastha"}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Get Nakshatra by ID","fields":[{"key":"id","name":"id","inQuery":false,"kind":"select","required":true,"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"}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Get Nakshatra by ID","fields":[{"key":"id","name":"id","inQuery":false,"kind":"select","required":true,"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","label":"Nakshatra"}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Get Rashi by ID","fields":[{"key":"id","name":"id","inQuery":false,"kind":"tiles","required":true,"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"}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Get Rashi by ID","fields":[{"key":"id","name":"id","inQuery":false,"kind":"tiles","required":true,"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","label":"Rashi"}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Get yoga details by ID","fields":[{"key":"id","name":"id","inQuery":false,"kind":"select","required":true,"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"}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Get yoga details by ID","fields":[{"key":"id","name":"id","inQuery":false,"kind":"select","required":true,"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","label":"Yoga"}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Compatibility score","fields":[{"key":"person1.date","name":"date","group":"person1","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"person1.time","name":"time","group":"person1","kind":"time","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":"person1.latitude","name":"latitude","group":"person1","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128,"role":"location"},{"key":"person1.longitude","name":"longitude","group":"person1","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006,"role":"location"},{"key":"person1.timezone","name":"timezone","group":"person1","kind":"number","required":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.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"person1.nodeType","name":"nodeType","group":"person1","kind":"tiles","required":false,"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"],"default":"true","example":"true"},{"key":"person2.date","name":"date","group":"person2","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"person2.time","name":"time","group":"person2","kind":"time","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":"person2.latitude","name":"latitude","group":"person2","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128,"role":"location"},{"key":"person2.longitude","name":"longitude","group":"person2","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006,"role":"location"},{"key":"person2.timezone","name":"timezone","group":"person2","kind":"number","required":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.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"person2.nodeType","name":"nodeType","group":"person2","kind":"tiles","required":false,"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"],"default":"true","example":"true"}],"hasLang":true,"groups":[{"key":"person1","location":{"fields":["person1.latitude","person1.longitude","person1.timezone"],"required":true}},{"key":"person2","location":{"fields":["person2.latitude","person2.longitude","person2.timezone"],"required":true}}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Compatibility score","fields":[{"key":"person1.date","name":"date","group":"person1","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"person1.time","name":"time","group":"person1","kind":"time","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":"person1.latitude","name":"latitude","group":"person1","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128,"role":"location"},{"key":"person1.longitude","name":"longitude","group":"person1","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006,"role":"location"},{"key":"person1.timezone","name":"timezone","group":"person1","kind":"number","required":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.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"person1.nodeType","name":"nodeType","group":"person1","kind":"tiles","required":false,"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"],"default":"true","example":"true"},{"key":"person2.date","name":"date","group":"person2","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"person2.time","name":"time","group":"person2","kind":"time","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":"person2.latitude","name":"latitude","group":"person2","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128,"role":"location"},{"key":"person2.longitude","name":"longitude","group":"person2","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006,"role":"location"},{"key":"person2.timezone","name":"timezone","group":"person2","kind":"number","required":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.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"person2.nodeType","name":"nodeType","group":"person2","kind":"tiles","required":false,"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"],"default":"true","example":"true"}],"hasLang":true,"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}}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Composite Chart","fields":[{"key":"person1.date","name":"date","group":"person1","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"person1.time","name":"time","group":"person1","kind":"time","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":"person1.latitude","name":"latitude","group":"person1","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128,"role":"location"},{"key":"person1.longitude","name":"longitude","group":"person1","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006,"role":"location"},{"key":"person1.timezone","name":"timezone","group":"person1","kind":"number","required":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.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"person1.nodeType","name":"nodeType","group":"person1","kind":"tiles","required":false,"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"],"default":"true","example":"true"},{"key":"person2.date","name":"date","group":"person2","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"person2.time","name":"time","group":"person2","kind":"time","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":"person2.latitude","name":"latitude","group":"person2","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128,"role":"location"},{"key":"person2.longitude","name":"longitude","group":"person2","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006,"role":"location"},{"key":"person2.timezone","name":"timezone","group":"person2","kind":"number","required":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.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"person2.nodeType","name":"nodeType","group":"person2","kind":"tiles","required":false,"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"],"default":"true","example":"true"},{"key":"houseSystem","name":"houseSystem","kind":"tiles","required":false,"description":"House system for the composite chart. Placidus (default), Whole Sign, Equal, or Koch.","enum":["placidus","whole-sign","equal","koch"],"default":"placidus","example":"placidus","fold":true}],"hasLang":true,"groups":[{"key":"person1","location":{"fields":["person1.latitude","person1.longitude","person1.timezone"],"required":true}},{"key":"person2","location":{"fields":["person2.latitude","person2.longitude","person2.timezone"],"required":true}},{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Composite Chart","fields":[{"key":"person1.date","name":"date","group":"person1","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"person1.time","name":"time","group":"person1","kind":"time","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":"person1.latitude","name":"latitude","group":"person1","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128,"role":"location"},{"key":"person1.longitude","name":"longitude","group":"person1","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006,"role":"location"},{"key":"person1.timezone","name":"timezone","group":"person1","kind":"number","required":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.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"person1.nodeType","name":"nodeType","group":"person1","kind":"tiles","required":false,"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"],"default":"true","example":"true"},{"key":"person2.date","name":"date","group":"person2","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"person2.time","name":"time","group":"person2","kind":"time","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":"person2.latitude","name":"latitude","group":"person2","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128,"role":"location"},{"key":"person2.longitude","name":"longitude","group":"person2","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006,"role":"location"},{"key":"person2.timezone","name":"timezone","group":"person2","kind":"number","required":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.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"person2.nodeType","name":"nodeType","group":"person2","kind":"tiles","required":false,"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"],"default":"true","example":"true"},{"key":"houseSystem","name":"houseSystem","kind":"tiles","required":false,"description":"House system for the composite chart. Placidus (default), Whole Sign, Equal, or Koch.","enum":["placidus","whole-sign","equal","koch"],"default":"placidus","example":"placidus","fold":true}],"hasLang":true,"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}},{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Generate relocation chart","fields":[{"key":"date","name":"date","kind":"date","required":true,"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":"time","name":"time","kind":"time","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":"timezone","name":"timezone","kind":"number","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.","min":-14,"max":14,"example":-10,"role":"location"},{"key":"birthLatitude","name":"latitude","group":"birth","kind":"number","required":true,"description":"Birthplace latitude in decimal degrees (-90 to 90). Used for the original natal angles and houses that the relocated chart is compared against.","min":-90,"max":90,"example":21.3069,"role":"location"},{"key":"birthLongitude","name":"longitude","group":"birth","kind":"number","required":true,"description":"Birthplace longitude in decimal degrees (-180 to 180). Positive East, negative West.","min":-180,"max":180,"example":-157.8583,"role":"location"},{"key":"relocationLatitude","name":"latitude","group":"relocation","kind":"number","required":true,"description":"New location latitude in decimal degrees (-90 to 90). The relocated Ascendant and house cusps are most sensitive to north-south movement.","min":-90,"max":90,"example":40.7167,"role":"location"},{"key":"relocationLongitude","name":"longitude","group":"relocation","kind":"number","required":true,"description":"New location longitude in decimal degrees (-180 to 180). The relocated Midheaven shifts roughly one degree per degree of longitude moved.","min":-180,"max":180,"example":-74.006,"role":"location"},{"key":"houseSystem","name":"houseSystem","kind":"tiles","required":false,"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"],"default":"placidus","example":"placidus","fold":true}],"hasLang":true,"groups":[{},{"key":"birth","location":{"fields":["birthLatitude","birthLongitude","timezone"],"required":true}},{"key":"relocation","location":{"fields":["relocationLatitude","relocationLongitude"],"required":true}}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Generate relocation chart","fields":[{"key":"date","name":"date","kind":"date","required":true,"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":"time","name":"time","kind":"time","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":"timezone","name":"timezone","kind":"number","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.","min":-14,"max":14,"example":-10,"role":"location"},{"key":"birthLatitude","name":"latitude","group":"birth","kind":"number","required":true,"description":"Birthplace latitude in decimal degrees (-90 to 90). Used for the original natal angles and houses that the relocated chart is compared against.","min":-90,"max":90,"example":21.3069,"label":"Birth latitude","role":"location"},{"key":"birthLongitude","name":"longitude","group":"birth","kind":"number","required":true,"description":"Birthplace longitude in decimal degrees (-180 to 180). Positive East, negative West.","min":-180,"max":180,"example":-157.8583,"label":"Birth longitude","role":"location"},{"key":"relocationLatitude","name":"latitude","group":"relocation","kind":"number","required":true,"description":"New location latitude in decimal degrees (-90 to 90). The relocated Ascendant and house cusps are most sensitive to north-south movement.","min":-90,"max":90,"example":40.7167,"label":"Relocation latitude","role":"location"},{"key":"relocationLongitude","name":"longitude","group":"relocation","kind":"number","required":true,"description":"New location longitude in decimal degrees (-180 to 180). The relocated Midheaven shifts roughly one degree per degree of longitude moved.","min":-180,"max":180,"example":-74.006,"label":"Relocation longitude","role":"location"},{"key":"houseSystem","name":"houseSystem","kind":"tiles","required":false,"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"],"default":"placidus","example":"placidus","fold":true}],"hasLang":true,"groups":[{},{"key":"birth","label":"Birth","location":{"fields":["birthLatitude","birthLongitude","timezone"],"required":true}},{"key":"relocation","label":"Relocation","location":{"fields":["relocationLatitude","relocationLongitude"],"required":true}}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Calculate synastry","fields":[{"key":"person1.date","name":"date","group":"person1","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"person1.time","name":"time","group":"person1","kind":"time","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":"person1.latitude","name":"latitude","group":"person1","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128,"role":"location"},{"key":"person1.longitude","name":"longitude","group":"person1","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006,"role":"location"},{"key":"person1.timezone","name":"timezone","group":"person1","kind":"number","required":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.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"person1.nodeType","name":"nodeType","group":"person1","kind":"tiles","required":false,"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"],"default":"true","example":"true"},{"key":"person1.name","name":"name","group":"person1","kind":"text","required":false,"description":"Optional display name for this person. Included in the response for easy identification.","example":"Alex"},{"key":"person2.date","name":"date","group":"person2","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"person2.time","name":"time","group":"person2","kind":"time","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":"person2.latitude","name":"latitude","group":"person2","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128,"role":"location"},{"key":"person2.longitude","name":"longitude","group":"person2","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006,"role":"location"},{"key":"person2.timezone","name":"timezone","group":"person2","kind":"number","required":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.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"person2.nodeType","name":"nodeType","group":"person2","kind":"tiles","required":false,"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"],"default":"true","example":"true"},{"key":"person2.name","name":"name","group":"person2","kind":"text","required":false,"description":"Optional display name for this person. Included in the response for easy identification.","example":"Alex"},{"key":"houseSystem","name":"houseSystem","kind":"tiles","required":false,"description":"House system for both natal charts. Placidus (default), Whole Sign, Equal, or Koch.","enum":["placidus","whole-sign","equal","koch"],"default":"placidus","example":"placidus","fold":true}],"hasLang":true,"groups":[{"key":"person1","location":{"fields":["person1.latitude","person1.longitude","person1.timezone"],"required":true}},{"key":"person2","location":{"fields":["person2.latitude","person2.longitude","person2.timezone"],"required":true}},{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Calculate synastry","fields":[{"key":"person1.date","name":"date","group":"person1","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"person1.time","name":"time","group":"person1","kind":"time","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":"person1.latitude","name":"latitude","group":"person1","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128,"role":"location"},{"key":"person1.longitude","name":"longitude","group":"person1","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006,"role":"location"},{"key":"person1.timezone","name":"timezone","group":"person1","kind":"number","required":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.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"person1.nodeType","name":"nodeType","group":"person1","kind":"tiles","required":false,"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"],"default":"true","example":"true"},{"key":"person1.name","name":"name","group":"person1","kind":"text","required":false,"description":"Optional display name for this person. Included in the response for easy identification.","example":"Alex"},{"key":"person2.date","name":"date","group":"person2","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"person2.time","name":"time","group":"person2","kind":"time","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":"person2.latitude","name":"latitude","group":"person2","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128,"role":"location"},{"key":"person2.longitude","name":"longitude","group":"person2","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006,"role":"location"},{"key":"person2.timezone","name":"timezone","group":"person2","kind":"number","required":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.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"person2.nodeType","name":"nodeType","group":"person2","kind":"tiles","required":false,"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"],"default":"true","example":"true"},{"key":"person2.name","name":"name","group":"person2","kind":"text","required":false,"description":"Optional display name for this person. Included in the response for easy identification.","example":"Alex"},{"key":"houseSystem","name":"houseSystem","kind":"tiles","required":false,"description":"House system for both natal charts. Placidus (default), Whole Sign, Equal, or Koch.","enum":["placidus","whole-sign","equal","koch"],"default":"placidus","example":"placidus","fold":true}],"hasLang":true,"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}},{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Transit Aspects","fields":[{"key":"natalChart.date","name":"date","group":"natalChart","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"natalChart.time","name":"time","group":"natalChart","kind":"time","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":"natalChart.latitude","name":"latitude","group":"natalChart","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128,"role":"location"},{"key":"natalChart.longitude","name":"longitude","group":"natalChart","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006,"role":"location"},{"key":"natalChart.timezone","name":"timezone","group":"natalChart","kind":"number","required":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.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"natalChart.nodeType","name":"nodeType","group":"natalChart","kind":"tiles","required":false,"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"],"default":"true","example":"true"},{"key":"transitDate","name":"transitDate","kind":"date","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","fold":true},{"key":"transitTime","name":"transitTime","kind":"time","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","fold":true},{"key":"planets","name":"planets","kind":"array","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":"aspectTypes","name":"aspectTypes","kind":"array","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":"minStrength","name":"minStrength","kind":"number","required":false,"description":"Minimum aspect strength threshold (0-100). Higher values return only tighter, more potent aspects. Useful for filtering out wide-orb aspects.","min":0,"max":100,"example":50,"fold":true},{"key":"houseSystem","name":"houseSystem","kind":"tiles","required":false,"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"],"default":"placidus","example":"placidus","fold":true}],"hasLang":true,"groups":[{"key":"natalChart","location":{"fields":["natalChart.latitude","natalChart.longitude","natalChart.timezone"],"required":true}},{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Transit Aspects","fields":[{"key":"natalChart.date","name":"date","group":"natalChart","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"natalChart.time","name":"time","group":"natalChart","kind":"time","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":"natalChart.latitude","name":"latitude","group":"natalChart","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128,"role":"location"},{"key":"natalChart.longitude","name":"longitude","group":"natalChart","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006,"role":"location"},{"key":"natalChart.timezone","name":"timezone","group":"natalChart","kind":"number","required":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.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"natalChart.nodeType","name":"nodeType","group":"natalChart","kind":"tiles","required":false,"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"],"default":"true","example":"true"},{"key":"transitDate","name":"transitDate","kind":"date","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","fold":true},{"key":"transitTime","name":"transitTime","kind":"time","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","fold":true},{"key":"planets","name":"planets","kind":"array","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":"aspectTypes","name":"aspectTypes","kind":"array","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":"minStrength","name":"minStrength","kind":"number","required":false,"description":"Minimum aspect strength threshold (0-100). Higher values return only tighter, more potent aspects. Useful for filtering out wide-orb aspects.","min":0,"max":100,"example":50,"fold":true},{"key":"houseSystem","name":"houseSystem","kind":"tiles","required":false,"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"],"default":"placidus","example":"placidus","fold":true}],"hasLang":true,"groups":[{"key":"natalChart","label":"Natal Chart","location":{"fields":["natalChart.latitude","natalChart.longitude","natalChart.timezone"],"required":true}},{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Calculate planetary transits","fields":[{"key":"date","name":"date","kind":"date","required":false,"description":"Transit date in YYYY-MM-DD format (defaults to current date)","example":"2025-12-19","fold":true},{"key":"time","name":"time","kind":"time","required":false,"description":"Transit time in HH:MM:SS format (defaults to current time)","example":"12:00:00","fold":true},{"key":"timezone","name":"timezone","kind":"number","required":false,"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. Defaults to 0 (UTC).","min":-14,"max":14,"default":0,"example":0,"city":true,"fold":true},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"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"],"default":"true","example":"true","fold":true},{"key":"natalChart.date","name":"date","group":"natalChart","kind":"date","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"},{"key":"natalChart.time","name":"time","group":"natalChart","kind":"time","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"},{"key":"natalChart.latitude","name":"latitude","group":"natalChart","kind":"number","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.","min":-90,"max":90,"example":40.7128,"role":"location"},{"key":"natalChart.longitude","name":"longitude","group":"natalChart","kind":"number","required":false,"description":"Natal birth longitude in decimal degrees, positive east and negative west. Example: New York -74.0060, London -0.1276, Sydney 151.2093.","min":-180,"max":180,"example":-74.006,"role":"location"},{"key":"natalChart.timezone","name":"timezone","group":"natalChart","kind":"number","required":false,"description":"Natal timezone: decimal hours OR IANA name (e.g. \"America/New_York\"). IANA resolved to the DST-correct offset for the natal date.","min":-14,"max":14,"example":"America/New_York","role":"location"}],"hasLang":true,"groups":[{},{"key":"natalChart","location":{"fields":["natalChart.latitude","natalChart.longitude","natalChart.timezone"],"required":false}}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Calculate planetary transits","fields":[{"key":"date","name":"date","kind":"date","required":false,"description":"Transit date in YYYY-MM-DD format (defaults to current date)","example":"2025-12-19","fold":true},{"key":"time","name":"time","kind":"time","required":false,"description":"Transit time in HH:MM:SS format (defaults to current time)","example":"12:00:00","fold":true},{"key":"timezone","name":"timezone","kind":"number","required":false,"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. Defaults to 0 (UTC).","min":-14,"max":14,"default":0,"example":0,"city":true,"fold":true},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"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"],"default":"true","example":"true","fold":true},{"key":"natalChart.date","name":"date","group":"natalChart","kind":"date","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"},{"key":"natalChart.time","name":"time","group":"natalChart","kind":"time","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"},{"key":"natalChart.latitude","name":"latitude","group":"natalChart","kind":"number","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.","min":-90,"max":90,"example":40.7128,"role":"location"},{"key":"natalChart.longitude","name":"longitude","group":"natalChart","kind":"number","required":false,"description":"Natal birth longitude in decimal degrees, positive east and negative west. Example: New York -74.0060, London -0.1276, Sydney 151.2093.","min":-180,"max":180,"example":-74.006,"role":"location"},{"key":"natalChart.timezone","name":"timezone","group":"natalChart","kind":"number","required":false,"description":"Natal timezone: decimal hours OR IANA name (e.g. \"America/New_York\"). IANA resolved to the DST-correct offset for the natal date.","min":-14,"max":14,"example":"America/New_York","role":"location"}],"hasLang":true,"groups":[{},{"key":"natalChart","label":"Natal Chart","location":{"fields":["natalChart.latitude","natalChart.longitude","natalChart.timezone"],"required":false}}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Calculate compatibility","fields":[{"key":"person1.birthDate","name":"birthDate","group":"person1","kind":"date","required":true,"description":"Birth date of person 1 in YYYY-MM-DD format.","example":"1990-07-15"},{"key":"person2.birthDate","name":"birthDate","group":"person2","kind":"date","required":true,"description":"Birth date of person 2 in YYYY-MM-DD format.","example":"1992-03-22"},{"key":"targetDate","name":"targetDate","kind":"date","required":false,"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","fold":true}],"hasLang":true,"groups":[{"key":"person1"},{"key":"person2"},{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Calculate compatibility","fields":[{"key":"person1.birthDate","name":"birthDate","group":"person1","kind":"date","required":true,"description":"Birth date of person 1 in YYYY-MM-DD format.","example":"1990-07-15"},{"key":"person2.birthDate","name":"birthDate","group":"person2","kind":"date","required":true,"description":"Birth date of person 2 in YYYY-MM-DD format.","example":"1992-03-22"},{"key":"targetDate","name":"targetDate","kind":"date","required":false,"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","fold":true}],"hasLang":true,"groups":[{"key":"person1","label":"Person 1"},{"key":"person2","label":"Person 2"},{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Calculate BaZi compatibility","fields":[{"key":"personA.date","name":"date","group":"personA","kind":"date","required":true,"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":"personA.time","name":"time","group":"personA","kind":"time","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":"personA.timezone","name":"timezone","group":"personA","kind":"number","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.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"personA.latitude","name":"latitude","group":"personA","kind":"number","required":false,"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.","min":-90,"max":90,"default":0,"example":0,"role":"location"},{"key":"personA.longitude","name":"longitude","group":"personA","kind":"number","required":false,"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\".","min":-180,"max":180,"example":116.4,"role":"location"},{"key":"personA.dayBoundary","name":"dayBoundary","group":"personA","kind":"tiles","required":false,"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"],"default":"split-zi","example":"split-zi"},{"key":"personA.yearBoundary","name":"yearBoundary","group":"personA","kind":"tiles","required":false,"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"],"default":"li-chun","example":"li-chun"},{"key":"personA.hourClock","name":"hourClock","group":"personA","kind":"tiles","required":false,"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"],"default":"clock","example":"clock"},{"key":"personB.date","name":"date","group":"personB","kind":"date","required":true,"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":"personB.time","name":"time","group":"personB","kind":"time","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":"personB.timezone","name":"timezone","group":"personB","kind":"number","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.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"personB.latitude","name":"latitude","group":"personB","kind":"number","required":false,"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.","min":-90,"max":90,"default":0,"example":0,"role":"location"},{"key":"personB.longitude","name":"longitude","group":"personB","kind":"number","required":false,"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\".","min":-180,"max":180,"example":116.4,"role":"location"},{"key":"personB.dayBoundary","name":"dayBoundary","group":"personB","kind":"tiles","required":false,"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"],"default":"split-zi","example":"split-zi"},{"key":"personB.yearBoundary","name":"yearBoundary","group":"personB","kind":"tiles","required":false,"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"],"default":"li-chun","example":"li-chun"},{"key":"personB.hourClock","name":"hourClock","group":"personB","kind":"tiles","required":false,"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"],"default":"clock","example":"clock"}],"hasLang":true,"groups":[{"key":"personA","location":{"fields":["personA.latitude","personA.longitude","personA.timezone"],"required":true}},{"key":"personB","location":{"fields":["personB.latitude","personB.longitude","personB.timezone"],"required":true}}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Calculate BaZi compatibility","fields":[{"key":"personA.date","name":"date","group":"personA","kind":"date","required":true,"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":"personA.time","name":"time","group":"personA","kind":"time","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":"personA.timezone","name":"timezone","group":"personA","kind":"number","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.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"personA.latitude","name":"latitude","group":"personA","kind":"number","required":false,"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.","min":-90,"max":90,"default":0,"example":0,"role":"location"},{"key":"personA.longitude","name":"longitude","group":"personA","kind":"number","required":false,"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\".","min":-180,"max":180,"example":116.4,"role":"location"},{"key":"personA.dayBoundary","name":"dayBoundary","group":"personA","kind":"tiles","required":false,"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"],"default":"split-zi","example":"split-zi"},{"key":"personA.yearBoundary","name":"yearBoundary","group":"personA","kind":"tiles","required":false,"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"],"default":"li-chun","example":"li-chun"},{"key":"personA.hourClock","name":"hourClock","group":"personA","kind":"tiles","required":false,"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"],"default":"clock","example":"clock"},{"key":"personB.date","name":"date","group":"personB","kind":"date","required":true,"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":"personB.time","name":"time","group":"personB","kind":"time","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":"personB.timezone","name":"timezone","group":"personB","kind":"number","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.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"personB.latitude","name":"latitude","group":"personB","kind":"number","required":false,"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.","min":-90,"max":90,"default":0,"example":0,"role":"location"},{"key":"personB.longitude","name":"longitude","group":"personB","kind":"number","required":false,"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\".","min":-180,"max":180,"example":116.4,"role":"location"},{"key":"personB.dayBoundary","name":"dayBoundary","group":"personB","kind":"tiles","required":false,"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"],"default":"split-zi","example":"split-zi"},{"key":"personB.yearBoundary","name":"yearBoundary","group":"personB","kind":"tiles","required":false,"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"],"default":"li-chun","example":"li-chun"},{"key":"personB.hourClock","name":"hourClock","group":"personB","kind":"tiles","required":false,"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"],"default":"clock","example":"clock"}],"hasLang":true,"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}}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Forecast digest","fields":[{"key":"birthData.date","name":"date","group":"birthData","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Anchors the natal chart and the Vimshottari dasha sequence.","example":"1990-07-15"},{"key":"birthData.time","name":"time","group":"birthData","kind":"time","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"},{"key":"birthData.timezone","name":"timezone","group":"birthData","kind":"number","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.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"birthData.latitude","name":"latitude","group":"birthData","kind":"number","required":false,"description":"Birth latitude in decimal degrees. Optional and does not affect the timeline. Defaults to 0.","min":-90,"max":90,"default":0,"example":0,"role":"location"},{"key":"birthData.longitude","name":"longitude","group":"birthData","kind":"number","required":false,"description":"Birth longitude in decimal degrees. Optional and does not affect the timeline. Defaults to 0.","min":-180,"max":180,"default":0,"example":0,"role":"location"},{"key":"startDate","name":"startDate","kind":"date","required":false,"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","fold":true},{"key":"domains","name":"domains","kind":"array","required":false,"description":"Which forecast domains to include before rolling up the windows. Defaults to all three.","example":["western","vedic","biorhythm"],"fold":true},{"key":"minSignificance","name":"minSignificance","kind":"number","required":false,"description":"Drop events scoring below this significance threshold from 0 to 100 before the rollup. Defaults to 0.","min":0,"max":100,"example":0,"fold":true},{"key":"domainWeights.western","name":"western","group":"domainWeights","kind":"number","required":false,"description":"Multiplier for this domain significance. 1 leaves it unchanged, above 1 promotes the domain, below 1 demotes it.","min":0,"max":100,"example":1.5,"fold":true},{"key":"domainWeights.vedic","name":"vedic","group":"domainWeights","kind":"number","required":false,"description":"Multiplier for this domain significance. 1 leaves it unchanged, above 1 promotes the domain, below 1 demotes it.","min":0,"max":100,"example":1.5,"fold":true},{"key":"domainWeights.biorhythm","name":"biorhythm","group":"domainWeights","kind":"number","required":false,"description":"Multiplier for this domain significance. 1 leaves it unchanged, above 1 promotes the domain, below 1 demotes it.","min":0,"max":100,"example":1.5,"fold":true},{"key":"top","name":"top","kind":"number","required":false,"description":"Number of highest-significance events to surface per window. Defaults to 3, capped at 20.","min":0,"max":20,"example":3,"fold":true}],"hasLang":true,"groups":[{"key":"birthData","location":{"fields":["birthData.latitude","birthData.longitude","birthData.timezone"],"required":true}},{},{"key":"domainWeights","fold":true}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Forecast digest","fields":[{"key":"birthData.date","name":"date","group":"birthData","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Anchors the natal chart and the Vimshottari dasha sequence.","example":"1990-07-15"},{"key":"birthData.time","name":"time","group":"birthData","kind":"time","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"},{"key":"birthData.timezone","name":"timezone","group":"birthData","kind":"number","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.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"birthData.latitude","name":"latitude","group":"birthData","kind":"number","required":false,"description":"Birth latitude in decimal degrees. Optional and does not affect the timeline. Defaults to 0.","min":-90,"max":90,"default":0,"example":0,"role":"location"},{"key":"birthData.longitude","name":"longitude","group":"birthData","kind":"number","required":false,"description":"Birth longitude in decimal degrees. Optional and does not affect the timeline. Defaults to 0.","min":-180,"max":180,"default":0,"example":0,"role":"location"},{"key":"startDate","name":"startDate","kind":"date","required":false,"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","fold":true},{"key":"domains","name":"domains","kind":"array","required":false,"description":"Which forecast domains to include before rolling up the windows. Defaults to all three.","example":["western","vedic","biorhythm"],"fold":true},{"key":"minSignificance","name":"minSignificance","kind":"number","required":false,"description":"Drop events scoring below this significance threshold from 0 to 100 before the rollup. Defaults to 0.","min":0,"max":100,"example":0,"fold":true},{"key":"domainWeights.western","name":"western","group":"domainWeights","kind":"number","required":false,"description":"Multiplier for this domain significance. 1 leaves it unchanged, above 1 promotes the domain, below 1 demotes it.","min":0,"max":100,"example":1.5,"fold":true},{"key":"domainWeights.vedic","name":"vedic","group":"domainWeights","kind":"number","required":false,"description":"Multiplier for this domain significance. 1 leaves it unchanged, above 1 promotes the domain, below 1 demotes it.","min":0,"max":100,"example":1.5,"fold":true},{"key":"domainWeights.biorhythm","name":"biorhythm","group":"domainWeights","kind":"number","required":false,"description":"Multiplier for this domain significance. 1 leaves it unchanged, above 1 promotes the domain, below 1 demotes it.","min":0,"max":100,"example":1.5,"fold":true},{"key":"top","name":"top","kind":"number","required":false,"description":"Number of highest-significance events to surface per window. Defaults to 3, capped at 20.","min":0,"max":20,"example":3,"fold":true}],"hasLang":true,"groups":[{"key":"birthData","label":"Birth Data","location":{"fields":["birthData.latitude","birthData.longitude","birthData.timezone"],"required":true}},{},{"key":"domainWeights","label":"Domain Weights","fold":true}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Significant dates","fields":[{"key":"birthData.date","name":"date","group":"birthData","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Anchors the natal chart and the Vimshottari dasha sequence.","example":"1990-07-15"},{"key":"birthData.time","name":"time","group":"birthData","kind":"time","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"},{"key":"birthData.timezone","name":"timezone","group":"birthData","kind":"number","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.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"birthData.latitude","name":"latitude","group":"birthData","kind":"number","required":false,"description":"Birth latitude in decimal degrees. Optional and does not affect the timeline. Defaults to 0.","min":-90,"max":90,"default":0,"example":0,"role":"location"},{"key":"birthData.longitude","name":"longitude","group":"birthData","kind":"number","required":false,"description":"Birth longitude in decimal degrees. Optional and does not affect the timeline. Defaults to 0.","min":-180,"max":180,"default":0,"example":0,"role":"location"},{"key":"startDate","name":"startDate","kind":"date","required":false,"description":"First day of the window in YYYY-MM-DD format. Defaults to today in UTC.","example":"2026-06-01","fold":true},{"key":"endDate","name":"endDate","kind":"date","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","fold":true},{"key":"domains","name":"domains","kind":"array","required":false,"description":"Which forecast domains to consider before filtering by significance. Defaults to all three.","example":["western","vedic","biorhythm"],"fold":true},{"key":"minSignificance","name":"minSignificance","kind":"number","required":false,"description":"Significance floor from 0 to 100 for what counts as a significant date. Defaults to 70.","min":0,"max":100,"example":70,"fold":true},{"key":"domainWeights.western","name":"western","group":"domainWeights","kind":"number","required":false,"description":"Multiplier for this domain significance. 1 leaves it unchanged, above 1 promotes the domain, below 1 demotes it.","min":0,"max":100,"example":1.5,"fold":true},{"key":"domainWeights.vedic","name":"vedic","group":"domainWeights","kind":"number","required":false,"description":"Multiplier for this domain significance. 1 leaves it unchanged, above 1 promotes the domain, below 1 demotes it.","min":0,"max":100,"example":1.5,"fold":true},{"key":"domainWeights.biorhythm","name":"biorhythm","group":"domainWeights","kind":"number","required":false,"description":"Multiplier for this domain significance. 1 leaves it unchanged, above 1 promotes the domain, below 1 demotes it.","min":0,"max":100,"example":1.5,"fold":true}],"hasLang":true,"groups":[{"key":"birthData","location":{"fields":["birthData.latitude","birthData.longitude","birthData.timezone"],"required":true}},{},{"key":"domainWeights","fold":true}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Significant dates","fields":[{"key":"birthData.date","name":"date","group":"birthData","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Anchors the natal chart and the Vimshottari dasha sequence.","example":"1990-07-15"},{"key":"birthData.time","name":"time","group":"birthData","kind":"time","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"},{"key":"birthData.timezone","name":"timezone","group":"birthData","kind":"number","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.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"birthData.latitude","name":"latitude","group":"birthData","kind":"number","required":false,"description":"Birth latitude in decimal degrees. Optional and does not affect the timeline. Defaults to 0.","min":-90,"max":90,"default":0,"example":0,"role":"location"},{"key":"birthData.longitude","name":"longitude","group":"birthData","kind":"number","required":false,"description":"Birth longitude in decimal degrees. Optional and does not affect the timeline. Defaults to 0.","min":-180,"max":180,"default":0,"example":0,"role":"location"},{"key":"startDate","name":"startDate","kind":"date","required":false,"description":"First day of the window in YYYY-MM-DD format. Defaults to today in UTC.","example":"2026-06-01","fold":true},{"key":"endDate","name":"endDate","kind":"date","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","fold":true},{"key":"domains","name":"domains","kind":"array","required":false,"description":"Which forecast domains to consider before filtering by significance. Defaults to all three.","example":["western","vedic","biorhythm"],"fold":true},{"key":"minSignificance","name":"minSignificance","kind":"number","required":false,"description":"Significance floor from 0 to 100 for what counts as a significant date. Defaults to 70.","min":0,"max":100,"example":70,"fold":true},{"key":"domainWeights.western","name":"western","group":"domainWeights","kind":"number","required":false,"description":"Multiplier for this domain significance. 1 leaves it unchanged, above 1 promotes the domain, below 1 demotes it.","min":0,"max":100,"example":1.5,"fold":true},{"key":"domainWeights.vedic","name":"vedic","group":"domainWeights","kind":"number","required":false,"description":"Multiplier for this domain significance. 1 leaves it unchanged, above 1 promotes the domain, below 1 demotes it.","min":0,"max":100,"example":1.5,"fold":true},{"key":"domainWeights.biorhythm","name":"biorhythm","group":"domainWeights","kind":"number","required":false,"description":"Multiplier for this domain significance. 1 leaves it unchanged, above 1 promotes the domain, below 1 demotes it.","min":0,"max":100,"example":1.5,"fold":true}],"hasLang":true,"groups":[{"key":"birthData","label":"Birth Data","location":{"fields":["birthData.latitude","birthData.longitude","birthData.timezone"],"required":true}},{},{"key":"domainWeights","label":"Domain Weights","fold":true}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Cross-domain forecast timeline","fields":[{"key":"birthData.date","name":"date","group":"birthData","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Anchors the natal chart and the Vimshottari dasha sequence.","example":"1990-07-15"},{"key":"birthData.time","name":"time","group":"birthData","kind":"time","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"},{"key":"birthData.timezone","name":"timezone","group":"birthData","kind":"number","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.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"birthData.latitude","name":"latitude","group":"birthData","kind":"number","required":false,"description":"Birth latitude in decimal degrees. Optional and does not affect the timeline. Defaults to 0.","min":-90,"max":90,"default":0,"example":0,"role":"location"},{"key":"birthData.longitude","name":"longitude","group":"birthData","kind":"number","required":false,"description":"Birth longitude in decimal degrees. Optional and does not affect the timeline. Defaults to 0.","min":-180,"max":180,"default":0,"example":0,"role":"location"},{"key":"startDate","name":"startDate","kind":"date","required":false,"description":"First day of the forecast window in YYYY-MM-DD format. Defaults to today in UTC.","example":"2026-06-01","fold":true},{"key":"endDate","name":"endDate","kind":"date","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","fold":true},{"key":"domains","name":"domains","kind":"array","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":"minSignificance","name":"minSignificance","kind":"number","required":false,"description":"Drop events scoring below this significance threshold from 0 to 100. Defaults to 0, keeping all events.","min":0,"max":100,"example":0,"fold":true},{"key":"domainWeights.western","name":"western","group":"domainWeights","kind":"number","required":false,"description":"Multiplier for this domain significance. 1 leaves it unchanged, above 1 promotes the domain, below 1 demotes it.","min":0,"max":100,"example":1.5,"fold":true},{"key":"domainWeights.vedic","name":"vedic","group":"domainWeights","kind":"number","required":false,"description":"Multiplier for this domain significance. 1 leaves it unchanged, above 1 promotes the domain, below 1 demotes it.","min":0,"max":100,"example":1.5,"fold":true},{"key":"domainWeights.biorhythm","name":"biorhythm","group":"domainWeights","kind":"number","required":false,"description":"Multiplier for this domain significance. 1 leaves it unchanged, above 1 promotes the domain, below 1 demotes it.","min":0,"max":100,"example":1.5,"fold":true}],"hasLang":true,"groups":[{"key":"birthData","location":{"fields":["birthData.latitude","birthData.longitude","birthData.timezone"],"required":true}},{},{"key":"domainWeights","fold":true}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Cross-domain forecast timeline","fields":[{"key":"birthData.date","name":"date","group":"birthData","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Anchors the natal chart and the Vimshottari dasha sequence.","example":"1990-07-15"},{"key":"birthData.time","name":"time","group":"birthData","kind":"time","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"},{"key":"birthData.timezone","name":"timezone","group":"birthData","kind":"number","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.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"birthData.latitude","name":"latitude","group":"birthData","kind":"number","required":false,"description":"Birth latitude in decimal degrees. Optional and does not affect the timeline. Defaults to 0.","min":-90,"max":90,"default":0,"example":0,"role":"location"},{"key":"birthData.longitude","name":"longitude","group":"birthData","kind":"number","required":false,"description":"Birth longitude in decimal degrees. Optional and does not affect the timeline. Defaults to 0.","min":-180,"max":180,"default":0,"example":0,"role":"location"},{"key":"startDate","name":"startDate","kind":"date","required":false,"description":"First day of the forecast window in YYYY-MM-DD format. Defaults to today in UTC.","example":"2026-06-01","fold":true},{"key":"endDate","name":"endDate","kind":"date","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","fold":true},{"key":"domains","name":"domains","kind":"array","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":"minSignificance","name":"minSignificance","kind":"number","required":false,"description":"Drop events scoring below this significance threshold from 0 to 100. Defaults to 0, keeping all events.","min":0,"max":100,"example":0,"fold":true},{"key":"domainWeights.western","name":"western","group":"domainWeights","kind":"number","required":false,"description":"Multiplier for this domain significance. 1 leaves it unchanged, above 1 promotes the domain, below 1 demotes it.","min":0,"max":100,"example":1.5,"fold":true},{"key":"domainWeights.vedic","name":"vedic","group":"domainWeights","kind":"number","required":false,"description":"Multiplier for this domain significance. 1 leaves it unchanged, above 1 promotes the domain, below 1 demotes it.","min":0,"max":100,"example":1.5,"fold":true},{"key":"domainWeights.biorhythm","name":"biorhythm","group":"domainWeights","kind":"number","required":false,"description":"Multiplier for this domain significance. 1 leaves it unchanged, above 1 promotes the domain, below 1 demotes it.","min":0,"max":100,"example":1.5,"fold":true}],"hasLang":true,"groups":[{"key":"birthData","label":"Birth Data","location":{"fields":["birthData.latitude","birthData.longitude","birthData.timezone"],"required":true}},{},{"key":"domainWeights","label":"Domain Weights","fold":true}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Western astrology forecast","fields":[{"key":"birthData.date","name":"date","group":"birthData","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Anchors the natal chart and the Vimshottari dasha sequence.","example":"1990-07-15"},{"key":"birthData.time","name":"time","group":"birthData","kind":"time","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"},{"key":"birthData.timezone","name":"timezone","group":"birthData","kind":"number","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.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"birthData.latitude","name":"latitude","group":"birthData","kind":"number","required":false,"description":"Birth latitude in decimal degrees. Optional and does not affect the timeline. Defaults to 0.","min":-90,"max":90,"default":0,"example":0,"role":"location"},{"key":"birthData.longitude","name":"longitude","group":"birthData","kind":"number","required":false,"description":"Birth longitude in decimal degrees. Optional and does not affect the timeline. Defaults to 0.","min":-180,"max":180,"default":0,"example":0,"role":"location"},{"key":"startDate","name":"startDate","kind":"date","required":false,"description":"First day of the transit window in YYYY-MM-DD format. Defaults to today in UTC.","example":"2026-06-01","fold":true},{"key":"endDate","name":"endDate","kind":"date","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","fold":true},{"key":"minSignificance","name":"minSignificance","kind":"number","required":false,"description":"Drop transit events scoring below this significance threshold from 0 to 100. Defaults to 0.","min":0,"max":100,"example":0,"fold":true}],"hasLang":true,"groups":[{"key":"birthData","location":{"fields":["birthData.latitude","birthData.longitude","birthData.timezone"],"required":true}},{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Western astrology forecast","fields":[{"key":"birthData.date","name":"date","group":"birthData","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Anchors the natal chart and the Vimshottari dasha sequence.","example":"1990-07-15"},{"key":"birthData.time","name":"time","group":"birthData","kind":"time","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"},{"key":"birthData.timezone","name":"timezone","group":"birthData","kind":"number","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.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"birthData.latitude","name":"latitude","group":"birthData","kind":"number","required":false,"description":"Birth latitude in decimal degrees. Optional and does not affect the timeline. Defaults to 0.","min":-90,"max":90,"default":0,"example":0,"role":"location"},{"key":"birthData.longitude","name":"longitude","group":"birthData","kind":"number","required":false,"description":"Birth longitude in decimal degrees. Optional and does not affect the timeline. Defaults to 0.","min":-180,"max":180,"default":0,"example":0,"role":"location"},{"key":"startDate","name":"startDate","kind":"date","required":false,"description":"First day of the transit window in YYYY-MM-DD format. Defaults to today in UTC.","example":"2026-06-01","fold":true},{"key":"endDate","name":"endDate","kind":"date","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","fold":true},{"key":"minSignificance","name":"minSignificance","kind":"number","required":false,"description":"Drop transit events scoring below this significance threshold from 0 to 100. Defaults to 0.","min":0,"max":100,"example":0,"fold":true}],"hasLang":true,"groups":[{"key":"birthData","label":"Birth Data","location":{"fields":["birthData.latitude","birthData.longitude","birthData.timezone"],"required":true}},{}],"opensOnLoad":false}
|