{"title":"Calculate the Human Design profile and line keynotes","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. The anchor for both the Personality activations at birth and the Design activations 88 degrees of solar arc earlier.","example":"1990-07-15"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Precision matters: the profile lines and gate boundaries shift with the exact minute of birth.","example":"13:00:00"},{"key":"timezone","name":"timezone","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 DST-correct offset for the birth date, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state on that date. Invalid timezones return 400 with a validation error.","min":-14,"max":14,"example":"America/New_York"},{"key":"latitude","name":"latitude","kind":"number","required":false,"description":"Birth latitude in decimal degrees. Optional and does not affect the bodygraph, which depends only on ecliptic longitudes. Defaults to 0.","min":-90,"max":90,"default":0,"example":0},{"key":"longitude","name":"longitude","kind":"number","required":false,"description":"Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.","min":-180,"max":180,"default":0,"example":0},{"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 activations. True is what professional Human Design software uses (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against, so leave it unset for a standard chart. It matters only when a node sits on a gate boundary, where the choice can move a node gate and, rarely, change the completed channels and therefore the type, authority or definition. If another calculator shows a different type, it is almost certainly using the mean node: pass \"mean\" to match it. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true"}],"hasLang":true}