Solar Return API

Request

A real request: the demonstration chart's return in 2027, at the birth place.

curl -X POST https://api.natalchart.ai/v1/solar-return \
  -H "Authorization: Bearer $NATALCHART_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"birth":{"date":"1991-09-06","time":"18:30","latitude":50.4501,"longitude":30.5234},"year":2027}'

Response

Part of the answer to that request: the main fields, with every list cut to its first three items.

{
  "year": 2027,
  "exactMomentUtc": "2027-09-06T08:29:55Z",
  "location": {
    "latitude": 50.4501,
    "longitude": 30.5234
  },
  "chart": "the full chart of that moment, in the shape of /v1/chart/full"
}

What comes back

• exactMomentUtc: the moment the Sun reaches its natal longitude again, in UTC.
• location: where the chart is cast; the birth place unless you send another.
• natalSun: the natal Sun's longitude the return is measured from.
• chart: the full chart for that moment and place, in the same shape as the natal chart endpoint.

Limits

• API Pro only. On the free key the endpoint answers 403 with a link to upgrade.
• A birth time is required.
• Tropical zodiac and Placidus houses, the same settings as the natal chart.
• Birth data is read, used and forgotten: request bodies are never stored.

In an AI assistant

Through the MCP server at https://www.natalchart.ai/mcp, assistants call the solar_return tool and read the year ahead from a computed chart.

The rest of the API

The same key opens the whole astrology API: natal charts, daily transits, synastry, transits for a period, solar returns, best days and astrocartography. Every endpoint, field and error is in the documentation, and the pricing page says what counts as a request.

Questions