Skip to content
AstroWay/api v2.201.6 · docs
all systems operational

Natal texts

GET /v1/natal-texts returns ready interpretation texts for chart placements. The texts are written and edited in advance; nothing is generated for your request.

GET /v1/natal-texts?keys=sun.aries,moon.h4,sun_moon.trine&lang=en HTTP/1.1
X-Api-Key: aw_live_...
  • keys: up to 64 distinct keys, comma separated.
    • planet in sign: sun.aries, also chiron.leo, ascendant.virgo;
    • planet in house: moon.h4;
    • aspect between two of Sun..Pluto: sun_moon.trine (conjunction, sextile, square, trine, opposition). Pair order does not matter, moon_sun becomes sun_moon.
  • lang: required, one of the site’s 20 languages.
{
"lang": "en",
"texts": {
"sun.aries": { "title": "Sun in Aries", "body": "Sun in Aries is will in its purest form, still hot as metal fresh from the furnace. …", "kind": "planet_in_sign" }
},
"missing": ["moon.h4", "sun_moon.trine"]
}

A text that does not exist in the requested language comes back in missing. We never substitute another language. body is plain text, paragraphs separated by a blank line.

Planet in sign: 144 texts in 20 languages. Planet in house and aspects are being written and will appear on this same endpoint.

/v1/natal-texts costs one ordinary call (10 credits) however many keys you ask for. Keyed responses are not cached by a CDN (Cache-Control: no-store), so store the texts on your side per key and language: a text changes only when it is edited.

Was this helpful?
Suggest an edit

Last updated: