Migrating from v1 to v2

​

Why Migrate

• Standard response envelope — consistent structure for every response
• camelCase fields — follows modern JSON conventions
• ISO 8601 dates — YYYY-MM-DD instead of DD-MMM-YY
• Machine-readable error codes — branch on errorCode instead of parsing messages
• New coordinates endpoint — generate charts from lat/lng without a geocoding key

​

Breaking Changes

​

Renamed Fields

​

Renamed Endpoints

​

Step-by-Step Migration

​

1. Update the base URL

- https://api.humandesignapi.nl/v1/bodygraphs
+ https://api.humandesignapi.nl/v2/charts

​

2. Change the authentication header

- HD-Api-Key: YOUR_API_KEY
+ Authorization: Bearer YOUR_API_KEY

​

3. Update the date format

- "birthdate": "15-Jan-90"
+ "birthdate": "1990-01-15"

​

4. Update response parsing

- const chart = await response.json();
- console.log(chart.type);
+ const result = await response.json();
+ const chart = result.data;
+ console.log(chart.type);

​

5. Update field names to camelCase

- chart.channels_short
+ chart.channelsShort

- chart.incarnation_cross
+ chart.incarnationCross

- chart.not_self_theme
+ chart.notSelfTheme

- chart.activations.design.north_node
+ chart.activations.design.northNode

​

Complete Before and After

curl -X POST https://api.humandesignapi.nl/v1/bodygraphs/simple \
  -H "Content-Type: application/json" \
  -H "HD-Api-Key: YOUR_API_KEY" \
  -H "HD-Geocode-Key: YOUR_GEOCODE_KEY" \
  -d '{
    "birthdate": "15-Jan-90",
    "birthtime": "14:30",
    "location": "Amsterdam, The Netherlands"
  }'

curl -X POST https://api.humandesignapi.nl/v2/charts/simple \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "HD-Geocode-Key: YOUR_GEOCODE_KEY" \
  -d '{
    "birthdate": "1990-01-15",
    "birthtime": "14:30",
    "location": "Amsterdam, The Netherlands"
  }'

​

FAQ

​

Do I need a new API key?

​

Is v1 being deprecated?

​

Can I use v1 and v2 simultaneously?