Legacy Endpoints & Compatibility

If you integrated before June 2026: you do not need to change anything. Every legacy endpoint below keeps working. There is no migration deadline, and none will be introduced without direct notice to affected developers.

New integrations should use the canonical endpoints — they are the ones our docs, playground, and examples teach.

Alias map

Legacy endpoint (still works)	Canonical equivalent
`POST /api/human-design`	`POST /api/chart`
`POST /api/v1/data`	`POST /api/chart`
`POST /api/v1/data-tooltip`	`POST /api/chart?include=tooltips`
`POST /api/v2/data`	`POST /api/chart`
`POST /api/v2/data-tooltip`	`POST /api/chart?include=tooltips`
`POST /api/v1/astrology`	`POST /api/astrology`
`POST /api/v1/astrology-tooltip`	`POST /api/astrology?include=tooltips`
`POST /api/v1/composite`	`POST /api/composite`
`POST /api/v1/composite-tooltip`	`POST /api/composite?include=tooltips`
`GET /api/transit-range`	`GET /api/transits/all`
`GET /api/transit/moon-range`	`GET /api/transits/moon`
`GET /api/transit-periods`	`GET /api/transits/periods`
`GET /api/v2/transit-chart`	`GET /api/transits/chart`
`GET /api/retrograde-periods`	`GET /api/retrogrades`
`POST /api/sage/query` (+ GET)	`POST /api/sage` (+ GET)
`POST /api/v1/saju`	`POST /api/bazi`
`GET /api/v1/locations`	`GET /api/locations`
`POST /api/v1/validate-location`	`POST /api/validate-location`

Legacy aliases return the same response shapes they always have. The canonical routes are the same handlers under cleaner paths — switching is a URL change only.

Known deprecation (with notice, not yet removed)

data.extras on Human Design chart responses (/api/chart, /api/v2/data) is deprecated. It is still returned today and will not be removed without direct email notice and a sunset period. New integrations should read astrology data (Chiron, asteroids, Lilith, angles, houses) from POST /api/astrology instead.

What we will never do silently

Remove or rename an endpoint
Change a response shape
Change meter costs (Chart requests or SAGE responses)
Invalidate working thd_ API keys

These are enforced by an automated compatibility harness on every change to the API.