Human Design Bodygraph API
Type, authority, profile, centers, channels, gates
Generate a complete Human Design bodygraph from a birth date, time, and timezone. Returns the energy type, strategy, inner authority, signature, not-self theme, profile, definition, incarnation cross, all nine centers with defined state and active gates, the defined channels, and all 26 planetary activations across the Personality and Design sides. The single endpoint for a full chart in one call, built for Human Design apps, readings, and coaching tools.
Location first, chart second
The Human Design Bodygraph API needs latitude, longitude, and timezone. Never ask users to type coordinates. Resolve a city with the Location endpoint first, then feed the result into the request. Timezone accepts a decimal offset or an IANA name.
1 Resolve the location
curl "https://roxyapi.com/api/v2/location/search?q=New York" \
-H "X-API-Key: YOUR_KEY"
# -> cities[0]: { latitude, longitude, timezone: "America/New_York" }2 Call the Human Design Bodygraph endpoint
# feed latitude, longitude and timezone from step 1
POST https://roxyapi.com/api/v2/human-design/bodygraphRequest
POST /api/v2/human-design/bodygraph
Parameters
| Parameter | Type | Description |
|---|---|---|
| langquery | string enum | Response language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English. Default en. |
Request body
| Field | Type | Description |
|---|---|---|
| date* | string (date) | 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* | string (time) | Birth time in 24-hour HH:MM:SS format. Precision matters: the profile lines and gate boundaries shift with the exact minute of birth. |
| timezone* | number or string | 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. |
| latitude | number | Birth latitude in decimal degrees. Optional and does not affect the bodygraph, which depends only on ecliptic longitudes. Defaults to 0. |
| longitude | number | Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0. |
Example request
{
"date": "1990-07-15",
"time": "13:00:00",
"timezone": "America/New_York"
}Response
Structured JSON with documented fields, verified against NASA JPL Horizons across 828 gold-standard tests. Not hallucinated text.
{
"type": "Manifestor",
"typeDescription": "An initiating, impactful aura built to start things and set them in motion. Informing others before acting removes resistance and brings peace.",
"aura": "string",
"strategy": "Inform",
"strategyDescription": "string",
"authority": "Emotional",
"authorityDescription": "string",
"signature": "Peace",
"notSelf": "Anger",
"profile": "5/1",
"profileKeynotes": {
"personalityLine": 5,
"designLine": 1,
"personality": "Heretic: a universalizing, practical force others project expectations onto.",
"design": "Investigator: builds a secure foundation through study before acting."
},
"profileDescription": "string",
"definition": "Split",
"definitionDescription": "string",
"sides": {},
"incarnationCross": {
"gates": [
51,
57,
61,
62
],
"angle": "Left Angle",
"angleCode": "LAX",
"name": "Left Angle Cross of the Clarion"
},
"centers": [
{
"id": "sacral",
"name": "Sacral",
"defined": true,
"motor": true,
"awareness": false,
"theme": "string",
"notSelfQuestion": "Is all this talking and doing an attempt to attract attention?",
"biology": "The adrenal glands.",
"gates": [
5,
14,
34
]
}
],
"channels": [
{
"gateA": 34,
"gateB": 20,
"name": "Charisma",
"circuit": "Individual",
"centers": [
"throat",
"sacral"
],
"description": "string",
"circuitDescription": "string"
}
],
"gates": [
{
"planet": "Sun",
"side": "personality",
"gate": 51,
"line": 5,
"gateName": "Shock",
"gateDescription": "string",
"lineMeaning": "string",
"planetDescription": "string",
"ichingHexagram": {
"number": 51,
"english": "The Arousing"
}
}
]
}Response fields
| Field | Type | Description |
|---|---|---|
| type* | string | Human Design energy type. One of Manifestor, Generator, Manifesting Generator, Projector, Reflector. |
| typeDescription* | string | What the aura of this type does and how it is designed to engage life. The grounding text for the type label, so a consuming agent does not have to supply the meaning itself. |
| aura* | string | The aura mechanic of the type: how the energy field itself operates, for example open and enveloping, or closed and repelling. |
| strategy* | string | The aura strategy for engaging life correctly for this type. |
| strategyDescription* | string | How to actually apply the strategy. The strategy field alone is a bare label such as Respond or Inform; this is the operating instruction behind it. |
| authority* | string | Inner authority for decision making. One of Emotional, Sacral, Splenic, Ego, Self-Projected, Mental, Lunar. |
| authorityDescription* | string | How the decision is made, the timing it requires, and the characteristic trap. Inner authority is the most actionable output of a Human Design chart, so this is the field to lean on when grounding a reading. |
| signature* | string | The signature feeling of living in alignment with the type. |
| notSelf* | string | The not-self theme, the recurring feeling that signals being out of alignment. |
| profile* | string | Profile in conscious/unconscious form from the Personality Sun line over the Design Sun line. |
| profileKeynotes* | object | The two line keynotes the profile is built from, conscious over unconscious, so the profile is readable without a separate lookup. |
| profileKeynotes.personalityLine* | number | Line number 1 to 6 of the conscious Personality Sun, the first digit of the profile. |
| profileKeynotes.designLine* | number | Line number 1 to 6 of the unconscious Design Sun, the second digit of the profile. |
| profileKeynotes.personality* | string | Keynote of the conscious Personality line. The half of the life role the person is aware of and can speak to. |
Show all fieldsShow fewer fields
| Field | Type | Description |
|---|---|---|
| profileKeynotes.design* | string | Keynote of the unconscious Design line. The half of the life role others see operating in the body, which the person does not directly experience. |
| profileDescription* | string | Meaning of the combined profile. A profile is not the sum of its two lines: 6/2 has its own meaning that neither the line 6 nor the line 2 keynote carries alone. |
| definition* | string | Definition type from the number of connected components among defined centers. One of None, Single, Split, Triple Split, Quadruple Split. |
| definitionDescription* | string | How energy flows through the defined centers in this configuration, and what the configuration needs. For a split, this is where the bridging gates of other people matter. |
| sides* | object | What the two chart sides are: personality is the conscious mind side, design is the unconscious body side computed 88 degrees of solar arc before birth. Returned once at the top level rather than repeated across all 26 activations. |
| incarnationCross* | object | The incarnation cross built from the four cardinal gates and the profile angle. |
| incarnationCross.gates* | array of number | The four cardinal gates of the cross: Personality Sun, Personality Earth, Design Sun, Design Earth. |
| incarnationCross.angle* | string | Cross angle. One of Right Angle, Juxtaposition, Left Angle. |
| incarnationCross.angleCode* | string | Short code for the angle. One of RAX, JXT, LAX. |
| incarnationCross.name* | string | Canonical published name of the incarnation cross, determined by the Personality Sun gate and the angle. Falls back to a name composed from the angle and the four gates if no canonical name exists. |
| incarnationCross.description | string | The life theme of the cross, synthesized from its four gates and the orientation the angle gives them. The same Sun gate under a different angle is a genuinely different theme: Right Angle is personal destiny, Left Angle is worked out through other people, Juxtaposition is a fixed fate. |
| centers* | array of object | All nine centers with their defined state and active gates. |
| centers[].id* | string | Center identifier. One of head, ajna, throat, g, heart, sacral, solar-plexus, spleen, root. |
| centers[].name* | string | Display name of the center. |
| centers[].defined* | boolean | Whether the center is defined. A defined center is a consistent source of energy or awareness; an undefined center is open and conditioned by others. |
| centers[].motor* | boolean | Whether this is a motor center (energy source). The four motors are Heart, Sacral, Solar Plexus, and Root. |
| centers[].awareness* | boolean | Whether this is an awareness center. The three awareness centers are Ajna, Solar Plexus, and Spleen. |
| centers[].theme* | string | Theme text describing the center in its current defined or undefined state. |
| centers[].notSelfQuestion* | string | The conditioning trap of this center when it is open. Returned on every center so a consumer can surface it the moment `defined` is false, which is where the not-self operates. |
| centers[].biology* | string | The gland, organ, or system this center corresponds to in the body. |
| centers[].gates* | array of number | Active gate numbers that sit in this center. |
| channels* | array of object | The defined channels where both gates are activated. |
| channels[].gateA* | number | First gate of the channel. |
| channels[].gateB* | number | Second gate of the channel. |
| channels[].name* | string | Name of the defined channel. |
| channels[].circuit* | string | Circuit family of the channel. One of Individual, Collective, Tribal. |
| channels[].centers* | array of string | The two centers this channel connects and defines. |
| channels[].description* | string | What this channel wires between its two centers and the nature of the energy it carries. |
| channels[].circuitDescription* | string | What the circuit family of this channel governs. |
| gates* | array of object | All 26 activations, 13 Personality and 13 Design. |
| gates[].planet* | string | Activating body. One of Sun, Earth, Moon, North Node, South Node, Mercury, Venus, Mars, Jupiter, Saturn, Uranus, Neptune, Pluto. |
| gates[].side* | string | Chart side. personality is the conscious birth-moment activation, design is the unconscious activation 88 degrees of solar arc before birth. |
| gates[].gate* | number | Human Design gate number from 1 to 64 that this activation falls in. |
| gates[].line* | number | Line number from 1 to 6 within the gate, setting the line keynote and the profile. |
| gates[].gateName* | string | Human Design keynote name of the gate, describing its bodygraph function. |
| gates[].gateDescription* | string | Bodygraph function of the gate: what it does in the center it sits in and the channel it forms. This is NOT the meaning of the I-Ching hexagram that shares its number. They share a number, not a definition. |
| gates[].lineMeaning* | string | Meaning of this gate at this specific line, one of 384. The finest interpretive layer in the chart and the one that makes a reading specific rather than generic. This is not the six abstract line archetypes: gate 41 line 3 carries its own meaning that neither the gate keynote nor the line-3 archetype holds alone. |
| gates[].planetDescription* | string | What this planetary activation contributes in Human Design specifically, which is not its meaning in western astrology. |
| gates[].ichingHexagram* | object | Cross-reference to the I-Ching hexagram that shares this gate number. |
| gates[].ichingHexagram.number* | number | I-Ching hexagram number, identical to the gate number it corresponds to. |
| gates[].ichingHexagram.english* | string | English name of the corresponding I-Ching hexagram. |
Supported options
lang
Call it in your language in seconds.
Every snippet is generated from the live OpenAPI spec, so method names, parameters, and fields always match production.
import { createRoxy } from '@roxyapi/sdk'
const roxy = createRoxy(process.env.ROXY_API_KEY!)
const { data } = await roxy.humanDesign.generateBodygraph({ body: { date: '1990-07-15', time: '13:00:00', timezone: 'America/New_York' } })from roxy_sdk import create_roxy
roxy = create_roxy("YOUR_API_KEY")
result = roxy.human_design.generate_bodygraph(date='1990-07-15', time='13:00:00', timezone='America/New_York')use function RoxyAPI\Sdk\createRoxy;
$roxy = createRoxy(getenv('ROXY_API_KEY'));
$result = $roxy->humanDesign->generateBodygraph(date: '1990-07-15', time: '13:00:00', timezone: 'America/New_York');using RoxyApi;
var roxy = new RoxyClient(Environment.GetEnvironmentVariable("ROXY_API_KEY")!);
var result = await roxy.HumanDesign.Bodygraph.PostAsync(new() { /* request fields above */ });import roxyapi "github.com/RoxyAPI/sdk-go"
roxy, _ := roxyapi.NewRoxy(os.Getenv("ROXY_API_KEY"))
resp, _ := roxy.HumanDesign.GenerateBodygraph(ctx, nil, roxyapi.GenerateBodygraphJSONRequestBody{ /* request fields above */ })curl -X POST "https://roxyapi.com/api/v2/human-design/bodygraph" \
-H "X-API-Key: YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{"date":"1990-07-15","time":"13:00:00","timezone":"America/New_York"}'Prefer to try before you write code? Run this Human Design endpoint live in the API playground and inspect a real production response.
More Human Design Bodygraph endpoints
The Human Design Bodygraph API bundles these related endpoints under one key.
Calculate Human Design type, authority and profile
Calculate the core Human Design identity from a birth moment: the energy type, the aura strategy, the inner authority, the signature and not-self themes, and the profile. The fast lookup for type-and-authority features without the full bodygraph payload. Verified against NASA JPL Horizons positions.
Try it liveCalculate the Human Design profile and line keynotes
Calculate the Human Design profile for a birth moment: the conscious Personality Sun line over the unconscious Design Sun line, with the keynote for each. The profile is the geometry of the life role, for example 5/1 the Heretic Investigator. Verified against NASA JPL Horizons positions.
Try it liveGenerate Human Design transit overlay - Current planetary activations on a natal bodygraph
Overlay the current or any given planetary positions on a natal Human Design bodygraph to see which channels the transit temporarily completes. Returns the 13 transiting body activations with gate and line, the channels the transit completes beyond the natal definition split into personal channels where the transit supplies the partner gate of a natal gate and educational channels where the transit supplies both gates, the natally open centers those channels temporarily define, and a short factual summary. A transit is a single moment, so there is no Design side. When date and time are omitted the overlay is computed for now in UTC. Built for daily Human Design apps, transit widgets, and notification tools.
Try it liveCalculate Human Design Variables - The four arrows and Color, Tone, Base substructure
Calculate the four Human Design Variable arrows for a birth moment: Determination and Environment on the design side, Perspective and Motivation on the personality side. Each arrow returns its Color, Tone, and Base numbers from the hexagram-line substructure, the left or right direction set by the Tone, and the sourced Color and direction labels. This is the advanced Rave Variables and Primary Health System layer beneath Type, Strategy, Authority, and Profile. Color, Tone, and Base shift with tiny differences in birth time, so each arrow carries a confidence flag that turns false near a Color or Tone boundary, and a precise birth time is essential. Built for Human Design apps offering PHS, diet, environment, and Rave Psychology readings.
Try it liveRemote MCP for AI agents
Every Human Design endpoint is a callable tool on the Remote MCP server over Streamable HTTP. No local setup, no Docker. Claude, ChatGPT, Cursor, and any MCP client auto-discover the tools and ground their answers in verified data.
claude mcp add --transport http \
roxy-human-design https://roxyapi.com/mcp/human-design \
--header "X-API-Key: YOUR_KEY"Tool name for POST /human-design/bodygraph: post_human_design_bodygraph. Full MCP setup guide
What you can build
Spiritual and self-discovery apps: full bodygraph generation, type and authority readings, and profile insights for personal growth journeys
Dating and relationship platforms: type, authority, and profile compatibility context derived from two birth charts
AI chatbots and coaching assistants: bodygraph data via remote MCP tool calls for Human Design conversations and decision-making guidance
Practitioner and reading tools: activation columns, defined channels, and center analysis for professional Human Design charts
Wellness and mindfulness platforms: strategy and authority prompts that help users make aligned decisions
Content and editorial platforms: gate and center reference lookups for explainer pages and structured Human Design libraries
Drop-in UI components
Render Human Design Bodygraph API responses without building charts yourself. These open source, framework-agnostic web components take the typed response and draw it, in React, Vue, Svelte, Angular, plain HTML, and WordPress.
Related capabilities
Human Design Bodygraph API FAQ
What does the Human Design Bodygraph API return?
Generate a complete Human Design bodygraph from a birth date, time, and timezone. Every response is structured JSON with documented fields, not free text, so you map it straight into your product.
How do I authenticate with the Human Design Bodygraph API?
Pass your key in the X-API-Key header on every request. Keys are delivered instantly at checkout with no approval queue. Use a secret sk key server side, or mint a publishable pk key locked to your origins for browser and no-code use.
Does the Human Design Bodygraph API support multiple languages?
Yes. Append the lang query parameter to any endpoint for responses in English, German, Spanish, French, Hindi, Portuguese, Russian and Turkish. The translated payload includes the full interpretation text, not just field labels.
Do I need coordinates to call the Human Design Bodygraph API?
No. Call GET /location/search with a city name first, then pass latitude, longitude, and timezone from the first result into the request. Never ask users to type coordinates. Timezone accepts a decimal offset or an IANA name.
Is the Human Design Bodygraph API available over Remote MCP for AI agents?
Yes. Every endpoint is exposed as a callable tool on the Remote MCP server at https://roxyapi.com/mcp/human-design over Streamable HTTP, so Claude, ChatGPT, Cursor, and any MCP client auto-discover it with no local setup or Docker.
How is the Human Design Bodygraph API billed?
Flat pricing: 1 request equals 1 quota unit, REST and MCP identical, with no credit weighting or per-token markup. Every plan includes all 12 domains, so the Human Design Bodygraph API is included at no extra cost.
What lang values does the Human Design Bodygraph API accept?
The lang parameter accepts en, tr, de, es, hi, pt, fr, ru. Case-insensitive where it is a path value.
Start using Human Design Bodygraph API today.
Ship a Human Design bodygraph your users can trust. This week.
All 12 domains included with every plan. Every endpoint, MCP server, SDK, and starters.
Plans from $39/mo, starting at $2.70 per domain on annual billing. No credit card required for testing.
View Pricing & Get API Key