Перейти до вмісту
AstroWay/api v2.325.0 · docs
усі системи в нормі

Hindu calendar: lunar months, adhika and kshaya, eras

POST
/vedic/calendar/months
request.sh
curl -X POST https://api.astroway.info/v1/vedic/calendar/months \
-H "X-Api-Key: aw_live_..." \
-H "Content-Type: application/json" \
-d '{ "year": 2026, "latitude": 28.6139, "longitude": 77.209, "timezone": "Asia/Kolkata" }'

The lunar months touching the year: new moon, full moon, next new moon, the Sun’s sidereal sign at the opening new moon, adhika (no sankranti inside) and kshaya (two), and the purnimanta names of both pakshas. Plus the twelve sankrantis with their local moments and the eras: Shaka and Vikram Samvat from Chaitra, Vikram Samvat from Kartika (Gujarat), the sixty-year samvatsara name. 2026 has Adhika Jyeshtha (17 May to 15 June).

fields
string

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.

Example
planets.name,planets.longitude
precision
integer
<= 15

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.

Example
4
Idempotency-Key
string
>= 1 characters <= 255 characters /^[\x21-\x7E]+$/

Unique per logical operation, kept across retries. For 24 hours from the first request, a repeat with the same key, method, path, body and query string returns the stored response with Idempotent-Replayed: true and costs 0 credits. The same key with a different body or query string is a 409 IDEMPOTENCY_KEY_REUSED; a repeat while the first is still running is a 409 IDEMPOTENCY_IN_PROGRESS. Only 2xx responses are kept. See /idempotency/.

Example
01HXY2A7ZM0ABCDEF
Media type application/json

A Gregorian year and a place for the lunar months.

object
year required

Gregorian year, 1900 to 2100. Entries are those whose date falls in this year.

integer
>= 1900 <= 2100
latitude required

Latitude in decimal degrees, north positive. Between -66 and 66: further out the Sun does not rise on some days and a Hindu day has no start.

number
nullable >= -66 <= 66
longitude required

Longitude in decimal degrees, east positive.

number
nullable >= -180 <= 180
timezone

IANA zone name such as Asia/Kolkata, America/New_York or Europe/Kyiv, or auto (default) to look it up from the coordinates. Resolved day by day: each day is read on the offset that zone kept that day, so summer time is followed.

string
>= 1 characters <= 64 characters
timezoneOffset

A fixed offset in hours instead of a zone, for the whole year. Ignored when timezone is sent.

number
nullable >= -14 <= 14
ayanamsaId
number
nullable
ayanamsa

Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either.

string
Allowed values: fagan-bradley lahiri de-luce raman krishnamurti kp yukteshwar jn-bhasin true-citra djwhal-khul
Example
{
"year": 2026,
"latitude": 28.6139,
"longitude": 77.209,
"timezone": "Asia/Kolkata"
}

Successful calculation

Media type application/json
object
ok
boolean
data
object
year
number
nullable
place
object
latitude
number
nullable
longitude
number
nullable
timezone
string
nullable
timezoneOffset
nullable
ayanamsaId
number
nullable
months
Array<object>
nullable
object
name
string
nullable
index
number
nullable
adhika
boolean
nullable
kshayaOf
nullable
label
string
nullable
newMoon
string
nullable
fullMoon
string
nullable
nextNewMoon
string
nullable
sunSignAtNewMoon
string
nullable
purnimanta
object
shuklaPaksha
string
nullable
krishnaPaksha
string
nullable
adhika
Array<string>
nullable
kshaya
Array
nullable
eras
object
shaka
object
from
string
nullable
number
number
nullable
note
string
nullable
vikramChaitradi
object
from
string
nullable
number
number
nullable
note
string
nullable
vikramKartikadi
object
from
string
nullable
number
number
nullable
note
string
nullable
samvatsara
object
name
string
nullable
note
string
nullable
sankrantis
Array<object>
nullable
object
sign
string
nullable
at
string
nullable
rule
string
nullable
Example
{
"ok": true,
"data": {
"year": 2026,
"place": {
"latitude": 28.6139,
"longitude": 77.209,
"timezone": "Asia/Kolkata",
"timezoneOffset": null,
"ayanamsaId": 1
},
"months": [
{
"name": "Jyeshtha",
"index": 3,
"adhika": true,
"kshayaOf": null,
"label": "Adhika Jyeshtha",
"newMoon": "2026-05-17T01:31:00+05:30",
"fullMoon": "2026-05-31T14:15:00+05:30",
"nextNewMoon": "2026-06-15T08:24:00+05:30",
"sunSignAtNewMoon": "Vrishabha",
"purnimanta": {
"shuklaPaksha": "Adhika Jyeshtha",
"krishnaPaksha": "Adhika Jyeshtha"
}
}
],
"adhika": [
"Adhika Jyeshtha"
],
"kshaya": [],
"eras": {
"shaka": {
"from": "2026-03-19T06:53:00+05:30",
"number": 1948,
"note": "Shaka year from Chaitra (Chaitradi); before it, the year is one less."
},
"vikramChaitradi": {
"from": "2026-03-19T06:53:00+05:30",
"number": 2083,
"note": "Vikram Samvat counted from Chaitra, North India."
},
"vikramKartikadi": {
"from": "2026-11-09T12:32:00+05:30",
"number": 2083,
"note": "Vikram Samvat counted from Kartika, Gujarat: one less than the Chaitradi number until then."
},
"samvatsara": {
"name": "Parabhava",
"note": "Sixty-year cycle name from Chaitra (Ugadi) and Chithirai, as South Indian almanacs give it."
}
},
"sankrantis": [
{
"sign": "Makara",
"at": "2026-01-14T15:07:00+05:30"
}
],
"rule": "A month runs new moon to new moon and is named by the sidereal sign of the Sun at the opening new moon plus one (Sun in Meena: Chaitra). No sankranti inside: adhika, named after the month that follows. Two sankrantis: kshaya, and the next name is skipped."
}
}

Validation error

Media type application/json
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

Media type application/json
Example
{
"ok": false,
"error": {
"code": "INVALID_API_KEY",
"message": "Invalid API key"
}
}