AstroWay/api v2.130.2 · pl
wszystkie systemy w normie
// astrology api · POST /v1/profections

Annual Profections API

Annual profections are the simplest timing technique in the Hellenistic toolkit and one of the most used: the chart advances one house per year of life, and the ruler of the sign on that house becomes the lord of the year. One number in, one planet out, and the whole year has a signature.

Endpoint
POST /v1/profections
Koszt
20 kredytów
Opóźnienie
~48 ms
Poziom
Tier 2
// 01 / Co oblicza

Annual Profections API

The endpoint takes the birth data and a target date, counts completed years from the birth moment, and advances one whole sign from the ascendant for each of them. The response reports the age it counted, the zero-based index of the sign the year lands on, and the planet ruling that sign as lordOfYear, alongside the natal ascendant, MC, Sun and Moon so you can render the year against the chart without a second call. The house number itself follows directly from the age: the cycle is twelve years long, so the profected house is the age modulo twelve, plus one. Age 36 returns to the first house and therefore to the ascendant's own sign, which is why the sample chart, with an ascendant at 169.97 degrees in Virgo, reports signIndex 5 and Mercury as the lord of that year. Because the count runs from the birth moment rather than the calendar, the profection year turns on the birthday and not on the first of January.

// 02 / Zapytanie na żywo

POST/v1/profections

curl -X POST https://api.astroway.info/v1/profections \
  -H "X-Api-Key: aw_live_..." \
  -H "Content-Type: application/json" \
  -d '{
  "date": "1990-05-15",
  "time": "14:30:00",
  "timezoneOffset": 3,
  "latitude": 50.45,
  "longitude": 30.52,
  "targetDate": "2026-05-15"
}'
Odpowiedź (fragment)
{
  "ok": true,
  "data": {
    "age": 36,
    "signIndex": 5,
    "lordOfYear": "Mercury",
    "ascendant": 169.9680,
    "mc": 77.0743,
    "sun": 54.3760,
    "moon": 296.9047
  }
}
// 03 / Parametry

Parametry

nametypeWymagane
date string (YYYY-MM-DD) tak Birth date.
time string (HH:MM:SS) tak Local clock time at birth.
timezoneOffset number (hours) tak UTC offset in effect at the birth moment.
latitude number tak Birth-place latitude, decimal degrees (north positive).
longitude number tak Birth-place longitude, decimal degrees (east positive).
targetDate string (YYYY-MM-DD) tak The date whose profection year you want. Age is counted from the birth moment, so the year turns on the birthday, not on January 1.
// 04 / Kiedy używać

Kiedy używać

Use profections when you need a timing layer a reader can follow without an ephemeris. Each year has one ruling planet, so a yearly forecast, a birthday report or an AI narrative can be built around a single clear statement rather than a table of transits. It composes especially well with transits and returns: find the lord of the year here, then look at what is happening to that planet by transit, and you have the classical two-step reading in two calls. It also pairs with the solar return, which covers the same year from a different angle. The technique is deliberately coarse. It tells you which department of life is activated and who is in charge of it, not what happens on a given afternoon, so treat it as the frame you hang finer timing on.

// 05 / Uwagi

Uwagi

Whole-sign profections from the ascendant, one sign per completed year, with the traditional domicile rulers giving the lord of the year. Ages are counted from the birth moment, so the year turns on the birthday. The natal ascendant, MC, Sun and Moon come from the Swiss Ephemeris engine in the tropical zodiac and are returned in degrees.

Wypróbuj API Annual Profections

Zdobądź klucz i wykonaj pierwsze wywołanie w niecałą minutę.

99.9% SLA · plany płatne · 30d status →