Upcoming
POST https://starsapi.com/api/v3/transit/vedic/upcoming
A forward-looking, chronologically-merged timeline of upcoming transit and panchang events. Aggregates sign ingress, retrograde stations, combustion windows, nakshatra transits, eclipses, and (when location is provided) panchang events like Ekadashi, Purnima, and Amavasya — all sorted by date into a single stream.
Powers forecast views, transit calendars, and per-user notification feeds.
Authentication
Required. See basic → Authentication.
Request body
Core parameters
| Field | Type | Required | Description |
|---|---|---|---|
window | string | No | Preset window: 7d, 30d, 3m, 6m, 12m. Default 30d. |
days | integer | No | Custom window in days (overrides window). Positive integer, capped at ~2 years. |
timezone | string | No | IANA timezone. Default UTC. |
from_date | string | No | Start date (YYYY-MM-DD). Default: today in the given timezone. |
event_types | string[] | No | Filter to specific event types. Default: all types. |
planet | string | No | Planet filter or all (default). |
include_moon | boolean | No | Include Moon ingress/nakshatra events. Default false (Moon transits are high-frequency). |
Location (enables panchang events)
Providing latitude and longitude enables panchang events
(Ekadashi, Purnima, Amavasya). Both must be provided together, or both omitted.
| Field | Type | Required | Description |
|---|---|---|---|
latitude | number | No | Observer latitude (−90…90). |
longitude | number | No | Observer longitude (−180…180). |
Panchang options
These only take effect when location is provided:
| Field | Type | Required | Description |
|---|---|---|---|
maas_system | string | No | purnimant (default, North Indian) or amant (South Indian). |
tradition | string | No | vaishnava (default) or smarta. Affects Ekadashi calculation. |
paksha | string | No | Filter Ekadashi by shukla or krishna paksha. Omit for both. |
Available event types
| Type | Category | Requires location | Description |
|---|---|---|---|
sign_ingress | Planetary | No | Planet enters a new sign. |
retrograde | Planetary | No | Planet turns retrograde or direct. |
combust | Planetary | No | Planet enters/exits combustion. |
nakshatra | Planetary | No | Planet enters a new nakshatra. |
eclipse | Astronomical | No | Solar or lunar eclipse. |
ekadashi | Panchang | Yes | Ekadashi tithi. |
purnima | Panchang | Yes | Full Moon (Purnima). |
amavasya | Panchang | Yes | New Moon (Amavasya). |
Response shape
query
Echo of all resolved parameters including computed to_date and active event_types.
events (chronological)
A flat array of event objects, sorted by date. Every event has at minimum:
| Field | Type | Description |
|---|---|---|
event_type | string | One of the event type keys above. |
date | string | Event date (YYYY-MM-DD). |
time | string | Event time (HH:MM:SS) in the requested timezone. |
description | string | Human-readable summary. |
Additional fields vary by event type: planetary events include planet
and sign/motion details; panchang events include paksha, tithi,
and Moon position; eclipses include type and subtype.
Use cases
- Transit calendar — render a month-view calendar with all transit events.
- Notification feed — power daily/weekly transit alerts for users.
- Panchang + transit integration — combine astronomical transits with religious observances in one view.
- Forecast reports — generate a “what’s coming” section for transit reports.
Errors
| HTTP | Code | Cause |
|---|---|---|
| 400 | INVALID_WINDOW | Unrecognised window value. |
| 400 | INVALID_EVENT_TYPE | No valid event types in event_types array. |
| 400 | INVALID_PARAM | Invalid maas_system, tradition, or paksha. |
| 400 | VALIDATION_ERROR | Latitude/longitude provided without the other. |
| 400 | INVALID_TIMEZONE | Numeric or non-IANA timezone. |
Plus standard auth errors.
See also
- Sign Ingress — detailed ingress data with duration
- Retrograde — detailed retrograde windows
- Eclipses — detailed eclipse data
- Moon Phases — detailed lunar phase data
- Transit overview