HumanDesignExtendedRequest
Request for extended Human Design placements. Exactly one of `birth_datetime_utc` (an instant) or `birth_datetime_local` (a naive local wall-clock time the server converts using the birth coordinates and the historical-correction overlay) is required, as on `/human-design/chart`. `latitude` and `longitude` are both required (an omitted one is a 422, never defaulted to 0,0): the Vertex, the angles and the Hermetic Lots all depend on the birthplace.
Properties
| Name | Type | Description |
|---|---|---|
| birth_datetime_local | string | Naive local wall-clock birth datetime (YYYY-MM-DDTHH:MM:SS, no zone suffix), resolved by the server. Mutually exclusive with `birth_datetime_utc`. |
| birth_datetime_utc | string | Birth instant as an RFC 3339 datetime, e.g. '1987-07-15T14:01:00Z'. Mutually exclusive with `birth_datetime_local`. |
| bodies | array | Extended bodies to return, by name (case-insensitive). Omit for the whole extended roster. Only valid when `include` contains `bodies`. An unknown name is rejected and the valid names are listed. |
| include | array | Components to compute: `bodies`, `angles`, `lots`, `stars`, `kernel_bodies`. Each is priced separately. `kernel_bodies` is opt-in: the kernel-backed catalog (asteroids, centaurs and trans-Neptunian ob |
| kernel_bodies | array | Kernel-catalog bodies to return, by ACG name (case-insensitive), e.g. `Eris`, `Eros (asteroid)`. Omit for the whole kernel catalog. Only valid when `include` contains `kernel_bodies`. An unknown name |
| latitude | number | Birth latitude in decimal degrees, within [-90, 90]. Required. |
| longitude | number | Birth longitude in decimal degrees, within [-180, 180]. Required. |
| star_groups | array | Fixed-star groups to return (names from `GET /catalogs/fixed-stars/groups`). Only valid when `include` contains `stars`, which needs `star_groups`, `star_names` or both. Priced per distinct group. |
| star_names | array | Fixed stars to return by catalog slug (case-insensitive; spaces read as underscores), e.g. `rigil_kentaurus`, `rasalhague`, `elnath`, `altair`. Slugs are listed at `GET /catalogs/fixed-stars`. Only va |
| timezone | object | Zone that governs `birth_datetime_local`. Optional — when omitted the zone is looked up from `latitude`/`longitude`. |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://artifacts.apis.io/openephemeris-com/json-schema/openephemeris-com-human-design-extended-request-schema.json",
"title": "HumanDesignExtendedRequest",
"description": "Request for extended Human Design placements. Exactly one of `birth_datetime_utc` (an instant) or `birth_datetime_local` (a naive local wall-clock time the server converts using the birth coordinates and the historical-correction overlay) is required, as on `/human-design/chart`. `latitude` and `longitude` are both required (an omitted one is a 422, never defaulted to 0,0): the Vertex, the angles and the Hermetic Lots all depend on the birthplace.",
"x-generated": "2026-11-10",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/openephemeris-com-human-design-api-openapi.yml#/components/schemas/HumanDesignExtendedRequest",
"properties": {
"birth_datetime_local": {
"description": "Naive local wall-clock birth datetime (YYYY-MM-DDTHH:MM:SS, no zone suffix), resolved by the server. Mutually exclusive with `birth_datetime_utc`.",
"title": "Birth Datetime Local",
"type": "string"
},
"birth_datetime_utc": {
"description": "Birth instant as an RFC 3339 datetime, e.g. '1987-07-15T14:01:00Z'. Mutually exclusive with `birth_datetime_local`.",
"format": "date-time",
"title": "Birth Datetime Utc",
"type": "string"
},
"bodies": {
"description": "Extended bodies to return, by name (case-insensitive). Omit for the whole extended roster. Only valid when `include` contains `bodies`. An unknown name is rejected and the valid names are listed.",
"items": {
"type": "string"
},
"maxItems": 64,
"title": "Bodies",
"type": "array"
},
"include": {
"default": [
"bodies"
],
"description": "Components to compute: `bodies`, `angles`, `lots`, `stars`, `kernel_bodies`. Each is priced separately. `kernel_bodies` is opt-in: the kernel-backed catalog (asteroids, centaurs and trans-Neptunian objects beyond the `bodies` roster, as named on the /acg endpoints, e.g. `Eros (asteroid)`); it is never included unless asked for.",
"items": {
"type": "string"
},
"maxItems": 5,
"title": "Include",
"type": "array"
},
"kernel_bodies": {
"description": "Kernel-catalog bodies to return, by ACG name (case-insensitive), e.g. `Eris`, `Eros (asteroid)`. Omit for the whole kernel catalog. Only valid when `include` contains `kernel_bodies`. An unknown name is rejected and the valid names are listed. Priced 1 credit per distinct body, capped at 20 (naming none costs the cap). Bodies with their own kernel cover 1600 to 2200 CE (the rest 1550 to 2650 CE); a birth whose Personality or Design instant falls outside a requested body's window is refused with a 422, never approximated. The Design instant is about 88 days before birth.",
"items": {
"type": "string"
},
"maxItems": 128,
"title": "Kernel Bodies",
"type": "array"
},
"latitude": {
"description": "Birth latitude in decimal degrees, within [-90, 90]. Required.",
"format": "double",
"title": "Latitude",
"type": "number"
},
"longitude": {
"description": "Birth longitude in decimal degrees, within [-180, 180]. Required.",
"format": "double",
"title": "Longitude",
"type": "number"
},
"star_groups": {
"description": "Fixed-star groups to return (names from `GET /catalogs/fixed-stars/groups`). Only valid when `include` contains `stars`, which needs `star_groups`, `star_names` or both. Priced per distinct group.",
"items": {
"type": "string"
},
"maxItems": 16,
"title": "Star Groups",
"type": "array"
},
"star_names": {
"description": "Fixed stars to return by catalog slug (case-insensitive; spaces read as underscores), e.g. `rigil_kentaurus`, `rasalhague`, `elnath`, `altair`. Slugs are listed at `GET /catalogs/fixed-stars`. Only valid when `include` contains `stars`. May be combined with `star_groups`: the result is the union, de-duplicated and in catalog order. An unknown slug is rejected with a 422 that lists the valid slugs. Priced 1 credit per distinct name, capped at 20.",
"items": {
"type": "string"
},
"maxItems": 256,
"title": "Star Names",
"type": "array"
},
"timezone": {
"$ref": "#/$defs/TimezoneInput",
"description": "Zone that governs `birth_datetime_local`. Optional — when omitted the zone is looked up from `latitude`/`longitude`."
}
},
"type": "object",
"$defs": {
"TimezoneInput": {
"additionalProperties": false,
"description": "Timezone input using IANA names or UTC offsets.",
"properties": {
"fold_preference": {
"description": "Which occurrence to use when the naive local datetime falls in a fall-back fold (a repeated hour): 'earlier' (default — first occurrence) or 'later'. Only meaningful for naive datetimes; the response reports datetime_status=ambiguous_fold either way so the ambiguity can be surfaced to the user.",
"enum": [
"earlier",
"later"
],
"title": "Fold Preference",
"type": "string"
},
"iana_name": {
"anyOf": [
{
"maxLength": 128,
"type": "string"
}
],
"description": "IANA timezone name",
"title": "Iana Name"
},
"time_standard": {
"description": "How to interpret a naive local datetime when this zone is applied. 'auto' (default): resolve through the historical-correction overlay where one covers the region/era, then IANA tzdata. 'standard': force the zone's standard (non-daylight) offset — for callers who KNOW the recorded time was standard time regardless of what tzdata believes. 'daylight': force standard+1h. Forcing either marks the resolution tz_confidence=client_override. Ignored when the datetime carries its own Z/±HH:MM suffix or when utc_offset is used.",
"enum": [
"auto",
"standard",
"daylight"
],
"title": "Time Standard",
"type": "string"
},
"utc_offset": {
"anyOf": [
{
"type": "number"
}
],
"description": "UTC offset in hours",
"title": "Utc Offset"
}
},
"title": "TimezoneInput",
"type": "object"
}
}
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/json-schemas/openephemeris-com-human-design-extended-request"
curl "https://apis.io/api/v1/json-schemas?limit=25"
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.