Input schema (JSON)
{
"type": "object",
"examples": [
{
"personA": {
"date": "1990-07-15",
"time": "13:00:00",
"timezone": "America/New_York"
},
"personB": {
"date": "1990-07-15",
"time": "13:00:00",
"timezone": "America/New_York"
}
}
],
"required": [
"personA",
"personB"
],
"properties": {
"lang": {
"enum": [
"en",
"tr",
"de",
"es",
"hi",
"pt",
"fr",
"ru",
"zh-Hans",
"zh-Hant"
],
"type": "string",
"default": "en",
"example": "en",
"description": "Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns English."
},
"compact": {
"type": "boolean",
"default": false,
"description": "Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {\"__cols\":[names],\"__rows\":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens."
},
"personA": {
"type": "object",
"required": [
"date",
"time",
"timezone"
],
"properties": {
"date": {
"type": "string",
"format": "date",
"example": "1990-07-15",
"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."
},
"time": {
"type": "string",
"format": "time",
"example": "13:00:00",
"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."
},
"latitude": {
"type": "number",
"default": 0,
"example": 0,
"maximum": 90,
"minimum": -90,
"description": "Birth latitude in decimal degrees. Optional and does not affect the bodygraph, which depends only on ecliptic longitudes. Defaults to 0."
},
"nodeType": {
"enum": [
"mean",
"true"
],
"type": "string",
"default": "true",
"example": "true",
"description": "Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node activations. True is what professional Human Design software uses (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against, so leave it unset for a standard chart. It matters only when a node sits on a gate boundary, where the choice moves a node gate. Because a gate can be half of a channel, that can change the completed channels and, with them, whether a center reads defined or open, plus the definition, authority, profile or type. A chart where only one center disagrees is the usual shape, since the type and profile often survive unchanged. If another calculator disagrees on any of those, it is almost certainly using the mean node: pass \"mean\" to match it. Defaults to \"true\"."
},
"timezone": {
"anyOf": [
{
"type": "number",
"maximum": 14,
"minimum": -14
},
{
"type": "string"
}
],
"example": "America/New_York",
"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."
},
"longitude": {
"type": "number",
"default": 0,
"example": 0,
"maximum": 180,
"minimum": -180,
"description": "Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0."
}
},
"description": "Birth moment of the first person in the connection."
},
"personB": {
"type": "object",
"required": [
"date",
"time",
"timezone"
],
"properties": {
"date": {
"type": "string",
"format": "date",
"example": "1990-07-15",
"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."
},
"time": {
"type": "string",
"format": "time",
"example": "13:00:00",
"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."
},
"latitude": {
"type": "number",
"default": 0,
"example": 0,
"maximum": 90,
"minimum": -90,
"description": "Birth latitude in decimal degrees. Optional and does not affect the bodygraph, which depends only on ecliptic longitudes. Defaults to 0."
},
"nodeType": {
"enum": [
"mean",
"true"
],
"type": "string",
"default": "true",
"example": "true",
"description": "Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node activations. True is what professional Human Design software uses (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against, so leave it unset for a standard chart. It matters only when a node sits on a gate boundary, where the choice moves a node gate. Because a gate can be half of a channel, that can change the completed channels and, with them, whether a center reads defined or open, plus the definition, authority, profile or type. A chart where only one center disagrees is the usual shape, since the type and profile often survive unchanged. If another calculator disagrees on any of those, it is almost certainly using the mean node: pass \"mean\" to match it. Defaults to \"true\"."
},
"timezone": {
"anyOf": [
{
"type": "number",
"maximum": 14,
"minimum": -14
},
{
"type": "string"
}
],
"example": "America/New_York",
"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."
},
"longitude": {
"type": "number",
"default": 0,
"example": 0,
"maximum": 180,
"minimum": -180,
"description": "Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0."
}
},
"description": "Birth moment of the second person in the connection."
}
}
}