Skip to content
AstroWay/api v2.325.0 · docs
all systems operational

Muhurat: month view for one ceremony

POST
/vedic/muhurat/month
request.sh
curl -X POST https://api.astroway.info/v1/vedic/muhurat/month \
-H "X-Api-Key: aw_live_..." \
-H "Content-Type: application/json" \
-d '{ "activity": "marriage", "month": "2026-11", "latitude": 28.6139, "longitude": 77.209, "timezoneOffset": 5.5 }'

Every day of month (YYYY-MM) judged for one activity (the keys of GET /muhurta/types) by the same sunrise-panchang scorer as /vedic/muhurat/: tithi, vara, nakshatra, yoga, karana factors, score, rating, suitable, barredBy (the factors with a negative weight), plus goodDates and bestDate. No lagna windows: the scanners compute none.

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

One ceremony, one month, one place. Every day of the month is judged at its sunrise by the same rules as the per-ceremony scanner.

object
activity required

Ceremony, one of the keys GET /muhurta/types lists (marriage, property-purchase for Griha Pravesh, vehicle-purchase, naming-ceremony, business-start …).

string
Allowed values: marriage vehicle-purchase business-start travel naming-ceremony surgery education-start investment property-purchase journey-long name-change general-auspicious
month required

Calendar month, YYYY-MM.

string
/^\d{4}-(0[1-9]|1[0-2])$/
latitude
number
0 nullable
longitude
number
0 nullable
timezoneOffset

Hours from UTC at the given moment, not minutes. Fractional zones are hours too: 5.5 for India, 5.75 for Nepal, -3.5 for Newfoundland. Defaults to 0, meaning UTC.

number
0 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
key additional
nullable
Example
{
"activity": "marriage",
"month": "2026-11",
"latitude": 28.6139,
"longitude": 77.209,
"timezoneOffset": 5.5
}

Successful calculation

Media type application/json
object
ok
boolean
data
object
activity
string
nullable
month
string
nullable
location
object
latitude
number
nullable
longitude
number
nullable
timezoneOffset
number
nullable
ayanamsa
number
nullable
days
Array<object>
nullable
object
date
string
nullable
weekday
number
nullable
weekdayName
string
nullable
panchang
object
tithi
number
nullable
tithiName
string
nullable
paksha
string
nullable
vara
number
nullable
varaName
string
nullable
nakshatra
number
nullable
nakshatraName
string
nullable
yoga
number
nullable
yogaName
string
nullable
karana
string
nullable
karanaIndex
number
nullable
pada
number
nullable
abhijitMuhurat
object
startTime
string
nullable
endTime
string
nullable
midHour
number
nullable
score
number
nullable
rating
string
nullable
factors
Array<object>
nullable
object
field
string
nullable
delta
number
nullable
note
string
nullable
suitable
boolean
nullable
barredBy
Array<object>
nullable
object
field
string
nullable
delta
number
nullable
note
string
nullable
goodDates
Array<string>
nullable
bestDate
string
nullable
Example
{
"ok": true,
"data": {
"activity": "marriage",
"month": "2026-11",
"location": {
"latitude": 28.6139,
"longitude": 77.209,
"timezoneOffset": 5.5
},
"ayanamsa": 24.23248633506398,
"days": [
{
"date": "2026-11-01",
"weekday": 0,
"weekdayName": "Ravivara",
"panchang": {
"tithi": 22,
"tithiName": "Saptami",
"paksha": "krishna",
"vara": 0,
"varaName": "Ravivara",
"nakshatra": 8,
"nakshatraName": "Pushya",
"yoga": 22,
"yogaName": "Sadhya",
"karana": "Bava",
"karanaIndex": 44,
"pada": 1
},
"abhijitMuhurat": {
"startTime": "11:42:29",
"endTime": "12:26:42",
"midHour": 12.0764228887856
},
"score": 0,
"rating": "average",
"factors": [
{
"field": "nakshatra",
"delta": 0,
"note": "Pushya: not in preferred set"
},
{
"field": "vara",
"delta": -2,
"note": "Ravivara: inauspicious weekday for marriage"
},
{
"field": "tithi",
"delta": 0,
"note": "Tithi Saptami (krishna): neutral"
},
{
"field": "yoga",
"delta": 1,
"note": "Yoga Sadhya: acceptable"
},
{
"field": "karana",
"delta": 1,
"note": "Karana Bava: movable, supportive"
}
],
"suitable": false,
"barredBy": [
{
"field": "vara",
"delta": -2,
"note": "Ravivara: inauspicious weekday for marriage"
}
]
}
],
"goodDates": [
"2026-11-02",
"2026-11-05",
"2026-11-06",
"2026-11-11",
"2026-11-12",
"2026-11-13",
"2026-11-25",
"2026-11-26"
],
"bestDate": "2026-11-25"
}
}

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"
}
}