Chart Element Interpretation

POST

/interpret/element

curl -X POST https://api.astroway.info/v1/interpret/element \
  -H "X-Api-Key: aw_live_..." \
  -H "Content-Type: application/json" \
  -d '{ "date": "1990-05-15", "time": "15:30:00", "timezone": "Europe/Kyiv", "latitude": 50.45, "longitude": 30.52, "language": "uk" }'

const res = await fetch('https://api.astroway.info/v1/interpret/element', {
  method: 'POST',
  headers: {
    'X-Api-Key': process.env.ASTROWAY_API_KEY,
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    "date": "1990-05-15",
    "time": "15:30:00",
    "timezone": "Europe/Kyiv",
    "latitude": 50.45,
    "longitude": 30.52,
    "language": "uk"
  }),
});
const { ok, data, error } = await res.json();
if (!ok) throw new Error(error.message);
console.log(data);

import os, requests

r = requests.post(
    'https://api.astroway.info/v1/interpret/element',
    headers={'X-Api-Key': os.environ['ASTROWAY_API_KEY'], 'Content-Type': 'application/json'},
    json={
      'date': "1990-05-15",
      'time': "15:30:00",
      'timezone': "Europe/Kyiv",
      'latitude': 50.45,
      'longitude': 30.52,
      'language': "uk"
    },
)
result = r.json()
if not result['ok']:
    raise RuntimeError(result['error']['message'])
print(result['data'])

<?php
use GuzzleHttp\Client;

$client = new Client(['base_uri' => 'https://api.astroway.info/v1/']);
$r = $client->post('interpret/element', [
    'headers' => ['X-Api-Key' => getenv('ASTROWAY_API_KEY')],
    'json' => [
        'date' => '1990-05-15',
        'time' => '15:30:00',
        'timezone' => 'Europe/Kyiv',
        'latitude' => 50.45,
        'longitude' => 30.52,
        'language' => 'uk',
    ],
]);
$result = json_decode($r->getBody(), true);
if (!$result['ok']) throw new \RuntimeException($result['error']['message']);
print_r($result['data']);

AI interpretation of a single chart element (planet/house/aspect) in context. Useful for chart-detail pages.

Authorizations

ApiKeyAuth

Parameters

Header Parameters

Accept-Language

string

Allowed values: uk en de ru pl es pt fr it nl cs ro hu el tr ar hi ja ko vi id

Target language for response text fields. RFC 7231 q-weighted. Falls back to ?lang= query param, then body.language, then source uk. Unknown codes silently fall through to uk.

Example

de

X-Provider

string

Allowed values: openai anthropic google groq mistral openrouter deepseek together

Bring your own model key: the LLM provider that should run this completion. Send together with X-Provider-Key or the request is refused: a key with no provider bills us for tokens you meant to pay for, and a provider with no key would look like it worked. The endpoint is fixed per provider on our side and is never taken from the request. There is no fallback to our own chain: if your key fails you get the provider’s status and message.

Example

anthropic

X-Provider-Key

string

Your own credential for X-Provider. Never logged, stored or cached: it travels in a header because the request body is hashed into two cache keys, and a BYOK turn bypasses both caches in each direction. A provider error that quotes the key back is redacted before it reaches our logs or your response. Such a turn costs 5 credits instead of the endpoint price, and only when a completion actually ran on your key.

Example

sk-ant-...

X-Provider-Model

string

<= 120 characters

Optional model id, overriding the default for that provider. Defaults: openai → gpt-4o-mini, anthropic → claude-sonnet-4-5, google → gemini-2.5-flash, groq → openai/gpt-oss-120b, mistral → mistral-large-latest, openrouter → meta-llama/llama-3.3-70b-instruct, deepseek → deepseek-chat, together → meta-llama/Llama-3.3-70B-Instruct-Turbo.

Example

claude-sonnet-4-5

Query Parameters

lang

string

Allowed values: uk en de ru pl es pt fr it nl cs ro hu el tr ar hi ja ko vi id

Alternative to Accept-Language for clients without header control.

Example

hi

fields

string

Comma-separated dotted paths, relative to data, to keep in the response. A path is applied to every element of an array, so planets.name means the name of each planet. Paths that match nothing come back in _fields_unmatched; a list where nothing matches at all is a 400, because an empty object would be a confident wrong answer.

Example

planets.name,planets.longitude

precision

integer

<= 15

Round every non-integer number in the response to this many decimal places. Integers are left alone, because an id is not a measurement. Ecliptic longitudes ship with fourteen decimals by default; 2 is about a tenth of an arcminute.

Example

Request Body^required

application/json

Birth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss), latitude and longitude in decimal degrees. The short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD; pass the full names. timezoneOffset is hours from UTC and defaults to 0, meaning UTC; send timezone instead (an IANA name such as Europe/Kyiv, or auto) and the offset for that date is worked out, summer time included. city is a display label only: nothing here geocodes it, so it never stands in for coordinates. houseSystem is a single Swiss Ephemeris letter, P by default; a name such as “Placidus” is refused, and the case matters because I and i are two different Sunshine systems.

object

date required

string

/^\d{4}-\d{2}-\d{2}$/

time required

string

/^\d{2}:\d{2}:\d{2}$/

timezoneOffset

Hours from UTC at the given moment, not minutes. Fractional zones are hours too: 5.5 for India, 5.75 for Nepal, -3.5 for Newfoundland. Defaults to 0, meaning UTC. Ignored when timezone is sent.

number

0 nullable >= -14 <= 14

timezone

IANA zone name such as Europe/Kyiv, or auto to look the zone up from latitude and longitude. The server takes the offset that zone kept at this local date and time, summer time included, and uses it in place of timezoneOffset. A clock time that happened twice takes the first occurrence; one skipped when clocks went forward takes the offset from before the change. Abbreviations such as EST are refused. Before 1970 the tz database is not reliable for every place, so send timezoneOffset when the local clock is known.

string

latitude required

number

>= -90 <= 90

longitude required

number

>= -180 <= 180

houseSystem

string

default: P

Allowed values: P K R C E W B M O A T V D F G H I i L N Q S U X Y

name

string

city

string

zodiacType

string

Allowed values: tropical sidereal

ayanamsaId

number

nullable

ayanamsa

Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either.

string

Allowed values: fagan-bradley lahiri de-luce raman krishnamurti kp yukteshwar jn-bhasin true-citra djwhal-khul

cosmogram

boolean

language

string

Allowed values: uk en de pl es pt fr it nl cs ro hu el tr ar hi ja ko vi id ru

disclaimer_inline

boolean

Example

{
  "date": "1990-05-15",
  "time": "15:30:00",
  "timezone": "Europe/Kyiv",
  "latitude": 50.45,
  "longitude": 30.52,
  "language": "uk"
}

Responses

200

Successful calculation

application/json

object

boolean

data

object

interpretation

string

nullable

disclaimer

string

nullable

model

string

nullable

language

string

nullable

element_balance

object

Fire

number

nullable

Earth

number

nullable

Air

number

nullable

Water

number

nullable

Example

{
  "ok": true,
  "data": {
    "interpretation": "Сатурн у власному знаку…",
    "disclaimer": "AI-generated interpretation for guidance only.",
    "model": "openai/gpt-oss-120b",
    "language": "uk",
    "element_balance": {
      "Fire": 1,
      "Earth": 6,
      "Air": 1,
      "Water": 5
    }
  }
}

400

Validation error

application/json

Example

{
  "ok": false,
  "error": {
    "code": "INVALID_INPUT",
    "message": "Validation failed: date: Date must be YYYY-MM-DD",
    "details": [
      {
        "path": "date",
        "message": "Date must be YYYY-MM-DD"
      }
    ]
  }
}

401

Missing or invalid API key

application/json

Example

{
  "ok": false,
  "error": {
    "code": "INVALID_API_KEY",
    "message": "Invalid API key"
  }
}

Корисно?

Запропонувати правку

// Назад

Transits Interpretation

Далі //

Specific Placement Interpretation

Chart Element Interpretation

Authorizations

Parameters

Header Parameters

Example

Example

Example

Example

Query Parameters

Example

Example

Example

Request Body required

Example

Responses

200

Example

400

Example

401

Example

Request Body^required