Human Design Transit Timeline
Human Design transits over a date range. For each transiting body: every gate it enters and leaves (and optionally every line), with retrograde re-entries marked. With natal gates (a subject or a gate list): every window in which a transiting gate completes one of the person's channels.
Gates are fixed arcs of the 302° wheel, so each entry and exit is an exact degree crossing, found to about a second. Range cap, span brackets and cost guard as /predictive/transits/search.
Pricing (by requested span, decided before any compute): up to 1 year (367 days) = 5, up to 3 years (1097 days) = 10, up to 5 years (1828 days) = 15, up to 10 years (3654 days) = 25, up to 20 years (7306 days) = 40, up to 40 years (14611 days) = 70 credits. Plan limits: Explorer/PAYG 1 year, Pro 5 years, Startup 10 years, Scale and Enterprise 40 years. A span above your plan's limit is rejected with 400 search_span_limit naming the limit and the bracket that fits — nothing is charged. Any 4xx/5xx outcome is refunded, including a 429 compute_overload shed; rate-limit 429s are refused before anything is charged. Results are capped at 2500 stays per response (a gate stay counts 1, plus 1 per line stay inside it); past that every stay entered before truncation.resume_from is returned with truncated: true.
Deadline: 30 s of compute on every plan. A search that runs out of time returns the bodies it finished with truncated: true (reason deadline, the unsearched bodies in truncation.remaining); if none finished it returns 503 compute_timeout, and the credits are refunded.
Request
- Base URL: https://api.openephemeris.com
- URL: https://api.openephemeris.com/human-design/transit-timeline
- Auth: one of:
- HTTP bearer
- API key in header X-OpenEphemeris-API-Key
- API key in header X-API-Key
- API key in header X-Service-Key
Request body
Example request
{
"bodies": [
"Sun",
"Mars",
"Jupiter",
"Saturn",
"Pluto"
],
"end_date": "2027-01-01T00:00:00Z",
"natal_gates": [
30,
57,
20,
34,
10
],
"start_date": "2026-10-01T00:00:00Z"
}Response
Successful Response
Changes
No recorded changes to this operation across all 1 revision of this API.