:::note
**TL;DR**
- A Human Design API turns a birth date, time, and timezone into structured type, strategy, authority, signature, not-self, and profile fields, no chart-drawing library required.
- The bodygraph combines Personality activations at birth with Design activations taken 88 degrees of solar arc earlier, and it depends only on ecliptic longitudes, so birth location does not change the result.
- Developer takeaway: one POST call returns the core identity as typed JSON you can render or feed to an agent, with no local setup.
- Build type, strategy, and authority features with the [Human Design API](/products/human-design-api "production-ready Human Design API with bodygraph, type, and profile").
:::

Human Design is one of the harder belief systems to compute correctly, and most builders stall at the same place: the math. You need precise planetary positions at two distinct moments, a 64-gate wheel mapped onto the I Ching, and a deterministic rule set that turns those positions into a type and an inner authority. A Human Design API removes that work. You send a birth moment, and you receive structured fields you can render, store, or hand to an AI agent. This post is the developer reference for the RoxyAPI Human Design API: what each endpoint returns, how the bodygraph is calculated, and the exact calls for type, strategy, and authority. For the conceptual primer on the chart itself, see the [bodygraph guide](/blogs/how-human-design-bodygraph-charts-work "how Human Design bodygraph charts work, centers, gates, and channels explained").

## What does a Human Design API return for a birth date and time?

A Human Design API returns the core identity computed from a birth date, time, and timezone. The fast endpoint, `POST /human-design/type`, returns six fields: type (Manifestor, Generator, Manifesting Generator, Projector, or Reflector), strategy (the aura strategy such as Inform or Wait a lunar cycle), authority (the inner decision-making authority such as Emotional, Sacral, or Lunar), signature, notSelf, and profile. These are the fields a type-and-authority feature actually needs, without the weight of a full chart payload.

You send three required fields, date, time, and timezone, and read typed JSON back. A verified call for a 1990-07-15 13:00:00 Europe/Berlin birth returns type Reflector, strategy Wait a lunar cycle, authority Lunar, signature Surprise, notSelf Disappointment, and profile 3/5. The values are deterministic: the same birth moment always returns the same identity, which makes results safe to cache in your own store. Because the calculation needs no chart image, you can render the output any way you like, from a simple badge to a full interactive graphic.

Ready to build this? The [Human Design API](/products/human-design-api "production-ready Human Design API with bodygraph, type, and profile") gives you type, strategy, and authority from one call, part of a single subscription covering 12 insight domains including Western astrology, Vedic, numerology, and tarot. [See pricing](/pricing "RoxyAPI pricing and plan tiers").

## How is the bodygraph calculated from birth data?

The bodygraph is calculated from two activation sets, not one. The Personality set comes from planetary positions at the exact birth moment. The Design set comes from positions taken 88 degrees of solar arc earlier, which lands roughly 88 days before birth. The API computes both, maps each planetary longitude onto its gate, and derives the defined centers, channels, type, and authority from the combined activations. This two-moment structure is what separates a real Human Design calculation from a single-chart approximation.

:::stat 88 degrees
**of solar arc** separate the Design activations from the Personality activations in every bodygraph. Positions are verified against NASA JPL Horizons. See [methodology](/methodology "RoxyAPI accuracy and verification methodology").
:::

A genuine, non-obvious detail: the bodygraph depends only on ecliptic longitudes, which are a function of date, time, and timezone alone. Birth latitude and longitude do not change any gate, center, or channel. The API accepts latitude and longitude as optional fields that default to 0, so you can omit them entirely and still get a correct chart.

## How do you get type, strategy, and authority from one API call?

You make one POST call to `POST /human-design/type` with date, time, and timezone. The cleanest pattern resolves the birth city to a DST-correct IANA timezone first, then passes that timezone into the Human Design call. Location is used only to look up the timezone here, because latitude and longitude do not affect the result, so they stay optional.

First resolve the timezone with a GET to location search:

```bash
curl -s -G "https://roxyapi.com/api/v2/location/search" \
  --data-urlencode "q=Berlin" \
  -H "X-API-Key: $ROXY_KEY"
```

Each returned city carries a `timezone` field (for Berlin, `Europe/Berlin`). Feed that into the type call:

```bash
curl -s -X POST "https://roxyapi.com/api/v2/human-design/type" \
  -H "Content-Type: application/json" \
  -H "X-API-Key: $ROXY_KEY" \
  -d '{"date":"1990-07-15","time":"13:00:00","timezone":"Europe/Berlin"}'
```

:::tabs
### curl
```bash
curl -s -X POST "https://roxyapi.com/api/v2/human-design/type" \
  -H "Content-Type: application/json" \
  -H "X-API-Key: $ROXY_KEY" \
  -d '{"date":"1990-07-15","time":"13:00:00","timezone":"Europe/Berlin"}'
```

### TypeScript
```typescript
const res = await fetch("https://roxyapi.com/api/v2/human-design/type", {
  method: "POST",
  headers: {
    "Content-Type": "application/json",
    "X-API-Key": process.env.ROXY_KEY!,
  },
  body: JSON.stringify({
    date: "1990-07-15",
    time: "13:00:00",
    timezone: "Europe/Berlin",
  }),
});
const data = await res.json();
console.log(data.type, data.strategy, data.authority);
```

### Python
```python
import os, requests

res = requests.post(
    "https://roxyapi.com/api/v2/human-design/type",
    headers={
        "Content-Type": "application/json",
        "X-API-Key": os.environ["ROXY_KEY"],
    },
    json={"date": "1990-07-15", "time": "13:00:00", "timezone": "Europe/Berlin"},
)
data = res.json()
print(data["type"], data["strategy"], data["authority"])
```
:::

The typed SDKs wrap the same call: the TypeScript SDK `@roxyapi/sdk` exposes the `humanDesign` namespace and returns `{ data, error }`, and the Python SDK `roxy-sdk` returns dicts. The `timezone` field also accepts decimal hours, so `5.5` for IST or `-5` for EST works in place of an IANA name. Every request and response field is documented in the [Human Design API reference](/api-reference#tag/human-design "full Human Design API endpoint reference with request and response schemas").

## What is on the full bodygraph: centers, channels, gates?

The full bodygraph endpoint, `POST /human-design/bodygraph`, returns the complete chart structure. The Human Design bodygraph has 9 centers, 36 channels, and 64 gates, and the 64 gates correspond one to one with the 64 I Ching hexagrams. The response exposes eleven top-level keys: authority, centers, channels, definition, gates, incarnationCross, notSelf, profile, signature, strategy, and type. That single payload is enough to render a complete interactive chart.

The `centers` array tells you which of the nine centers are defined or open, the `channels` array gives the active connections between centers, and `gates` lists every activated gate across both the Personality and Design sets. The `definition` field describes how the defined centers connect (single, split, and so on), `type` and `strategy` come straight from the defined-center pattern, and `incarnationCross` names the four-gate cross formed by the Sun and Earth in both sets. Reading these arrays is what lets you draw the chart yourself rather than rely on a fixed image.

Because the 64 gates map directly onto the I Ching, a Human Design feature pairs naturally with hexagram lookups; RoxyAPI also ships an I Ching API in the same subscription, so the gate-to-hexagram bridge is one key away. The bodygraph response is the right call when you want to render the whole chart at once, while the type endpoint is the lighter choice when you only need the headline identity, both built on the same verified positions.

## How do you read profile lines and avoid wrong charts?

You read the profile with `POST /human-design/profile`, which returns `profile` (for example `5/1`), `personalityLine`, `designLine`, `personalityKeynote`, and `designKeynote`. The `personalityLine` is the conscious line drawn from the Personality Sun-Earth, and `designLine` is the unconscious line from the Design set. Together they form the two-number profile that anchors much of a Human Design reading, and the two keynote strings give you ready labels for each line so you can render the profile without maintaining your own copy table.

:::warning
The exact minute of birth matters. Profile lines and gate boundaries shift with the precise time, so an unresolved or wrong timezone moves the chart. An invalid timezone returns a 400 validation error, not a silently wrong answer, but a valid-but-incorrect offset (for example forgetting daylight saving) returns a wrong profile with no error. Resolve the city to a DST-correct IANA timezone with location search before you call, and pass that exact value.
:::

The same date, time, and timezone fields apply to every Human Design endpoint, so once you resolve the timezone once you can call type, profile, and bodygraph with the identical body. Treat the timezone resolution step as the single source of correctness for the whole feature. If your users only know their birth city, store the resolved IANA timezone alongside the date and time, never a raw numeric offset, so the chart stays correct even across daylight-saving boundaries.

## FAQ

**Is there a Human Design API?**

Yes. RoxyAPI ships a live Human Design API with 12 endpoints covering type, bodygraph, profile, centers, channels, gates, connection, penta, transit, and variables. It also offers a Remote MCP server, so AI agents can call it directly. It is part of one subscription that covers 12 insight domains under a single key.

**What does the Human Design API return?**

The fast type endpoint returns type, strategy, authority, signature, notSelf, and profile from a birth date, time, and timezone. The bodygraph endpoint adds centers, channels, gates, definition, and the incarnation cross. The profile endpoint returns the profile string plus the separate personality and design lines. Every field comes back as typed JSON.

**Do I need a birth location for a Human Design bodygraph?**

No. The bodygraph depends only on ecliptic longitudes, which are a function of date, time, and timezone. Birth latitude and longitude are optional and default to 0 because they do not change any gate, center, or channel. The only reason to look up a city is to resolve its DST-correct timezone.

**How accurate is the Human Design calculation?**

The underlying planetary positions are verified against NASA JPL Horizons, and the bodygraph correctly applies the 88-degrees-of-solar-arc offset for the Design activations. Accuracy at the gate and profile level depends on a correct birth time and timezone, since the exact minute shifts line and gate boundaries. A wrong offset returns a confidently wrong chart with no error, which is why timezone resolution is the step to get right.

**Can I use the Human Design API with AI agents or MCP?**

Yes. RoxyAPI exposes a Remote MCP server over Streamable HTTP, so it runs in seconds with Claude Code, Cursor, and VS Code with no local process to install or restart. An agent can call the type or bodygraph tool the same way it would call any other tool, and the response is the same structured JSON the REST endpoints return.

## Conclusion

A Human Design API gives you type, strategy, authority, and the full bodygraph as typed JSON from one birth moment, with the 88-degrees-of-solar-arc Design calculation handled for you and no dependence on birth location. Start building with the [Human Design API](/products/human-design-api "production-ready Human Design API with bodygraph, type, and profile") and review the [pricing](/pricing "RoxyAPI pricing and plan tiers") page; one key also covers Western astrology, Vedic, numerology, tarot, and eight more domains at one flat price.