Skip to main content

Western Events (date range)

asterwise_get_western_events

One timeline of everything that happens to a chart over 1 to 31 days, each event with its exact time. It holds the exact major aspects from the transiting planets to the natal planets and angles with Lilly's verdicts, tropical sign ingresses and stations, Moon sign changes, void-of-course periods, New and Full Moons and quarters, eclipses with their contacts, and the profection year turning on the birthday.

Parameters​

ParameterTypeRequiredDescription
birthobjectyesBirth data for Western astrology tools (tropical zodiac). Required fields: date, time, lat, lon. Optional fields: person_name, timezone, house_system.
response_formatenum: markdown, jsonnoOutput format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload.
from_datestring/nullnoFirst day, YYYY-MM-DD. Defaults to today in the birth timezone.
daysintegernoNumber of civil days, 1 to 31 (7 for a week, 30 for a month).
target_timezonestring/nullnoIANA timezone for the days and local times. Defaults to the birth timezone.

What it covers​

The backbone for calendars and notifications on the Western track, in time order, UTC and local. Uranus, Neptune and Pluto carry no verdict. No weighting.

Workflow​

BEFORE: asterwise_get_western_natal.
AFTER: asterwise_get_western_daily_factors — the full picture of one of the days.

Input​

birth — WesternBirthData. from_date (optional YYYY-MM-DD; defaults to today). days (1-31, default 7). target_timezone (optional IANA).

Output contract​

data.events[] — kind (aspect_exact|ingress|moon_sign|station|void_of_course|moon_phase|eclipse|profection_year), planet, title, time_utc, time_local, time_precision, detail{}, verdict, verdict_rule, rule_source, significations[], depends_on_birth_time
data.kinds{}

Response format​

response_format=json — structured data. response_format=markdown — readable report.

Compute class​

MEDIUM_COMPUTE

Errors​

INVALID_PARAMS (local): input validation failures; days outside 1-31.
INVALID_PARAMS (upstream): a bad date or an unknown timezone → 422, surfaces as MCP INTERNAL_ERROR with the API message.
INTERNAL_ERROR: Any upstream API failure → MCP INTERNAL_ERROR

Do not confuse with​

asterwise_get_western_transits_monthly — day snapshots, not a timeline of exact moments.

Connect​

Remote MCP endpoint: https://mcp.asterwise.com/mcp. Authenticate with Authorization: Bearer <API key> or OAuth. See the MCP setup guide.