Eclipse Analysis
curl -X POST https://api.astroway.info/v1/eclipse-analysis \ -H "X-Api-Key: aw_live_..." \ -H "Content-Type: application/json" \ -d '{ "natal": { "date": "1990-05-15", "time": "14:30:00", "timezoneOffset": 3, "latitude": 50.45, "longitude": 30.52 }, "year": 2024, "point": { "lat": 50.45, "lng": 30.52 } }'const res = await fetch('https://api.astroway.info/v1/eclipse-analysis', { method: 'POST', headers: { 'X-Api-Key': process.env.ASTROWAY_API_KEY, 'Content-Type': 'application/json', }, body: JSON.stringify({ "natal": { "date": "1990-05-15", "time": "14:30:00", "timezoneOffset": 3, "latitude": 50.45, "longitude": 30.52 }, "year": 2024, "point": { "lat": 50.45, "lng": 30.52 } }),});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/eclipse-analysis', headers={'X-Api-Key': os.environ['ASTROWAY_API_KEY'], 'Content-Type': 'application/json'}, json={ 'natal': { 'date': "1990-05-15", 'time': "14:30:00", 'timezoneOffset': 3, 'latitude': 50.45, 'longitude': 30.52 }, 'year': 2024, 'point': { 'lat': 50.45, 'lng': 30.52 } },)result = r.json()if not result['ok']: raise RuntimeError(result['error']['message'])print(result['data'])<?phpuse GuzzleHttp\Client;
$client = new Client(['base_uri' => 'https://api.astroway.info/v1/']);$r = $client->post('eclipse-analysis', [ 'headers' => ['X-Api-Key' => getenv('ASTROWAY_API_KEY')], 'json' => [ 'natal' => [ 'date' => '1990-05-15', 'time' => '14:30:00', 'timezoneOffset' => 3, 'latitude' => 50.45, 'longitude' => 30.52, ], 'year' => 2024, 'point' => [ 'lat' => 50.45, 'lng' => 30.52, ], ],]);$result = json_decode($r->getBody(), true);if (!$result['ok']) throw new \RuntimeException($result['error']['message']);print_r($result['data']);Analyse the impact of upcoming eclipses on a natal chart: aspects to natal planets, house activations, and Saros series context.
Authorizations
Section titled “Authorizations ”Request Body required
Section titled “Request Body required ”Wrapper { natal: ChartInput } used by endpoints that take a base natal plus extra parameters in flat fields.
object
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. city is a display label only: nothing here geocodes it, so it never stands in for coordinates.
object
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.
Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either.
object
Example
{ "natal": { "date": "1990-05-15", "time": "14:30:00", "timezoneOffset": 3, "latitude": 50.45, "longitude": 30.52 }, "year": 2024, "point": { "lat": 50.45, "lng": 30.52 }}Responses
Section titled “ Responses ”Successful calculation
object
object
object
object
Example
{ "ok": true, "data": { "eclipses": [ { "type": "solar", "date": "2024-04-08", "longitude": 19.1, "aspects": [ { "natalPlanet": "Sun", "type": "conjunction", "orb": 4.9 } ], "activatedHouse": 10 } ] }}Validation error
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" } ] }}Missing or invalid API key
Example
{ "ok": false, "error": { "code": "INVALID_API_KEY", "message": "Invalid API key" }}