Monthly Forecast

POST

/bazi/monthly

request.sh

curl -X POST https://api.astroway.info/v1/bazi/monthly \
  -H "X-Api-Key: aw_live_..." \
  -H "Content-Type: application/json" \
  -d '{ "natalDate": "1990-05-15", "targetYear": 2026, "targetMonth": 6 }'

▸ Спробувати POST /bazi/monthly

• Production

Same Sheng-Ke + branch-clash analysis as yearly, but applied to a specific calendar month. Month branch resolved via mid-month jieqi.

Authorizations

• ApiKeyAuth

Parameters

Query Parameters

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

Request Body ^required

Media type application/json

object

natalDate required

string

/^\d{4}-\d{2}-\d{2}$/

natalTime

string

/^\d{2}:\d{2}(:\d{2})?$/

natalTzOffset

number

>= -14 <= 14

targetYear required

integer

>= 1900 <= 2100

targetMonth required

integer

>= 1 <= 12

language

string

Example

{
  "natalDate": "1990-05-15",
  "targetYear": 2026,
  "targetMonth": 6
}

Responses

200

Successful calculation

Media type application/json

object

ok

boolean

data

object

natalDayMaster

object

stem

string

nullable

element

string

nullable

yin

boolean

nullable

targetYear

number

nullable

targetMonth

number

nullable

targetPillar

object

stem

string

nullable

branch

string

nullable

pillar

string

nullable

animal

string

nullable

elementFlow

object

stem

object

element

string

nullable

relation

string

nullable

flavor

string

nullable

branch

object

element

string

nullable

relation

string

nullable

flavor

string

nullable

branchInteractions

object

clashes

Array

nullable

notes

Array<string>

nullable

disclaimer

string

nullable

Example

{
  "ok": true,
  "data": {
    "natalDayMaster": {
      "stem": "Geng",
      "element": "Metal",
      "yin": false
    },
    "targetYear": 2026,
    "targetMonth": 6,
    "targetPillar": {
      "stem": "Jia",
      "branch": "Wu",
      "pillar": "Jia-Wu",
      "animal": "Horse"
    },
    "elementFlow": {
      "stem": {
        "element": "Wood",
        "relation": "wealth",
        "flavor": "wealth (财): material gain or expense year"
      },
      "branch": {
        "element": "Fire",
        "relation": "control",
        "flavor": "control / officer (官杀): pressure or authority year"
      }
    },
    "branchInteractions": {
      "clashes": []
    },
    "notes": [
      "Month branch determined by jieqi at mid-month (~15th). For exact day boundaries, pair with /v1/sun-times."
    ],
    "disclaimer": "BaZi pillars use the canonical 60-jiazi cycle, anchored at 1990-01-01 = Bing-Yin. Year and month boundaries are the exact Lichun and 節 instants from the ephemeris, stated in China Standard Time; pass time and timezoneOffset for births near a boundary. Day and hour follow the birthplace clock, with the day rolling at 23:00 local."
  }
}

400

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

401

Missing or invalid API key

Media type application/json

Example

{
  "ok": false,
  "error": {
    "code": "INVALID_API_KEY",
    "message": "Invalid API key"
  }
}