# Muhurat: month view for one ceremony

`POST https://api.astroway.info/v1/vedic/muhurat/month`

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/<activity>: 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.

Group: Vedic. Auth: `X-Api-Key` header. Operation ID: `vedic_muhurat_month`.

## Parameters

| Name | In | Required | Type | Description |
|---|---|---|---|---|
| `fields` | query | no | 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. |
| `precision` | query | no | integer | 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. |
| `Idempotency-Key` | header | no | string | 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/. |

## Request body

| Field | Type | Required | Description |
|---|---|---|---|
| `activity` | "marriage" \| "vehicle-purchase" \| "business-start" \| "travel" \| "naming-ceremony" \| "surgery" \| "education-start" \| "investment" \| … | yes | Ceremony, one of the keys GET /muhurta/types lists (marriage, property-purchase for Griha Pravesh, vehicle-purchase, naming-ceremony, business-start ...). |
| `month` | string | yes | Calendar month, YYYY-MM. |
| `latitude` | number | no |  |
| `longitude` | number | no |  |
| `timezoneOffset` | number | no | 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. |
| `ayanamsaId` | number | no |  |
| `ayanamsa` | "fagan-bradley" \| "lahiri" \| "de-luce" \| "raman" \| "krishnamurti" \| "kp" \| "yukteshwar" \| "jn-bhasin" \| … | no | Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either. |

```json
{
  "activity": "marriage",
  "month": "2026-11",
  "latitude": 28.6139,
  "longitude": 77.209,
  "timezoneOffset": 5.5
}
```

## Responses

| Status | Meaning |
|---|---|
| 200 | Successful calculation |
| 400 | Validation error |
| 401 | Missing or invalid API key |

### Success fields, under `data`

| Field | Type | Required | Description |
|---|---|---|---|
| `activity` | string | no |  |
| `month` | string | no |  |
| `location` | object | no |  |
| `location.latitude` | number | no |  |
| `location.longitude` | number | no |  |
| `location.timezoneOffset` | number | no |  |
| `ayanamsa` | number | no |  |
| `days` | object[] | no |  |
| `goodDates` | string[] | no |  |
| `bestDate` | string | no |  |

## Example

```bash
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 }'
```

---

Rendered from https://api.astroway.info/v1/openapi.json. HTML page: https://api.astroway.info/docs/api/operations/vedic_muhurat_month/