Human Design bodygraph (public, no key)
curl -X POST 'https://api.astroway.info/v1/public/human-design' \ -H 'Content-Type: application/json' \ -d '{"date":"1990-03-15","time":"14:30:00","timezoneOffset":2,"latitude":50.45,"longitude":30.52}'Type, strategy, authority, profile, defined centres, channels and gates. Same input and same engine as the authed POST /human-design, served anonymously under the public rate limit. Responses carry the free-tier _footer watermark. Centre identifiers are PascalCase with no separator and are stable: Head, Ajna, Throat, G, Heart, SolarPlexus, Spleen, Sacral, Root; channels[].centerA and centerB use the same nine. localized carries type, strategy, authority and the centre names in the requested language, keyed by the same identifiers, so a caller reads localized.centers.SolarPlexus and never matches on a translated string. The English values above it are the stable ones and never change. Channel and gate names are prose rather than a closed set and stay English.
Parameters
Section titled “ Parameters ”Header Parameters
Section titled “Header Parameters ”BCP-47 language (e.g. uk, en, de). Set it once on your HTTP client as its default; for a single call, ?lang= overrides it. Unknown or inactive codes fall back to uk.
Query Parameters
Section titled “Query Parameters ”Example
enLanguage for this call, overriding Accept-Language. The canonical per-call form: a page that renders in one language passes it here rather than reconfiguring its client. Unknown or inactive codes fall back to uk.
Comma-separated dotted paths, relative to data, to keep in the response. A path is applied to every element of an array, so planets.name means the name of each planet. Paths that match nothing come back in _fields_unmatched; a list where nothing matches at all is a 400, because an empty object would be a confident wrong answer.
Example
planets.name,planets.longitudeRound every non-integer number in the response to this many decimal places. Integers are left alone, because an id is not a measurement. Ecliptic longitudes ship with fourteen decimals by default; 2 is about a tenth of an arcminute.
Example
4Request Body required
Section titled “Request Body required ”Birth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss), latitude and longitude in decimal degrees. The short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD; pass the full names. timezoneOffset is hours from UTC and defaults to 0, meaning UTC; send timezone instead (an IANA name such as Europe/Kyiv, or auto) and the offset for that date is worked out, summer time included. city is a display label only: nothing here geocodes it, so it never stands in for coordinates. houseSystem is a single Swiss Ephemeris letter, P by default; a name such as “Placidus” is refused, and the case matters because I and i are two different Sunshine systems.
object
Hours from UTC at the given moment, not minutes. Fractional zones are hours too: 5.5 for India, 5.75 for Nepal, -3.5 for Newfoundland. Defaults to 0, meaning UTC. Ignored when timezone is sent.
IANA zone name such as Europe/Kyiv, or auto to look the zone up from latitude and longitude. The server takes the offset that zone kept at this local date and time, summer time included, and uses it in place of timezoneOffset. A clock time that happened twice takes the first occurrence; one skipped when clocks went forward takes the offset from before the change. Abbreviations such as EST are refused. Before 1970 the tz database is not reliable for every place, so send timezoneOffset when the local clock is known.
Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either.
Example
{ "date": "1990-03-15", "time": "14:30:00", "timezoneOffset": 2, "latitude": 50.45, "longitude": 30.52}Responses
Section titled “ Responses ”OK
object
object
object
object
object
object
object
object
object
object
Type, strategy, authority and centre names in the requested language. Centres key by the same identifiers as centers[].name.
object
object
Free-tier watermark, present on every public response.
Example
{ "ok": true, "data": { "input": { "name": "", "date": "1990-05-15", "time": "15:30:00", "timezoneOffset": 4, "latitude": 50.45, "longitude": 30.52, "houseSystem": "P", "city": "", "cosmogram": false }, "type": "Projector", "strategy": "Wait for the Invitation", "notSelfTheme": "Bitterness", "authority": "Emotional (Solar Plexus)", "profile": { "profile": "6/3", "personalityLine": 6, "designLine": 3, "geometry": "Left Angle" }, "definition": "Split", "cross": { "name": "Left Angle Cross of Dedication", "type": "LAC", "gates": [ 23 ] }, "activations": [ { "planet": "Sun", "planetId": 0, "gate": 23, "line": 6, "color": 6, "tone": 2, "base": 2, "longitude": 54.37601980167181, "isPersonality": true } ], "personalityActivations": [ { "planet": "Sun", "planetId": 0, "gate": 23, "line": 6, "color": 6, "tone": 2, "base": 2, "longitude": 54.37601980167181, "isPersonality": true } ], "designActivations": [ { "planet": "Sun", "planetId": 0, "gate": 30, "line": 3, "color": 1, "tone": 1, "base": 1, "longitude": 326.37601741834976, "isPersonality": false } ], "centers": [ { "name": "Head", "defined": true, "open": false, "gates": [ 61 ], "activeGates": [ 61 ] } ], "channels": [ { "gate1": 13, "gate2": 33, "centerA": "G", "centerB": "Throat", "activatedBy": [ "personality" ] } ], "designJd": 2447937.835688273, "personalityJd": 2448026.9791666665, "localized": { "type": "Генератор", "strategy": "Чекай на сакральний відгук", "authority": "Емоційний (сонячне сплетіння)", "centers": { "Head": "Голова", "Ajna": "Аджна", "Throat": "Горло", "G": "G-центр", "Heart": "Серце (Его)", "SolarPlexus": "Сонячне сплетіння", "Sacral": "Сакральний центр", "Spleen": "Селезінка", "Root": "Корінь" }, "geometry": "Прямий кут", "defined": "визначений", "open": "відкритий" } }, "_footer": "Powered by astroway.api - get your own key at https://api.astroway.info"}Invalid input
Example
{ "ok": false, "error": { "code": "INVALID_FIELD", "message": "Unsupported fields: \"tz\", \"lat\", \"lng\". Rename them to \"timezoneOffset\", \"latitude\", \"longitude\". See details for what each one expects.", "details": [ { "path": "tz", "expected": "timezoneOffset", "message": "numeric hours from UTC, e.g. 5.75; a zone name goes in timezone" }, { "path": "lat", "expected": "latitude", "message": "decimal degrees, north positive" }, { "path": "lng", "expected": "longitude", "message": "decimal degrees, east positive" } ], "docs": "https://api.astroway.info/en/errors/#invalid_field" }}