Prognostics

Transit Calendar

Changed on

List the exact moments of transit-to-natal aspects in a date range, one event per exact pass, so a retrograde triple pass gives three events.

post/transit-calendar

Request

  • Base URL: https://api.astroway.info/v1
  • URL: https://api.astroway.info/v1/transit-calendar
  • Auth: API key in header X-Api-Key

Query parameters

fieldsstring

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.

precisioninteger

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.

Request body

startDatestring required
endDatestring required
maxOrbnumber nullable

Accepted and echoed back, but it does not filter anything: every event is an exact hit, found by the sign change of the offset and refined by bisection, so its orb is 0. Must be in (0, 10] if sent.

aspectAnglesnumber[]

Subset of 0, 60, 90, 120, 180 (the default is all five). Other angles match nothing and answer 400.

transitPlanetIdsinteger[]

Transiting bodies, ids 0 and 2-9 (Sun, Mercury to Pluto; the Moon is excluded). Default: all nine.

Example request

{
  "natal": {
    "timezone": "Europe/Kyiv"
  }
}

Response

Successful calculation

okboolean

Example response

{
  "ok": true
}

Changes

  • ec98fcd88094Revision changes
    • warning

      changed the pattern of the request property ///// from ^\d{2}:\d{2}:\d{2}$ to ^\d{2}:\d{2}(:\d{2})?$

  • b64222844186Revision changes
    • info

      added the new optional query request parameter fields

    • info

      added the new optional query request parameter precision