Day-master strength

POST

/bazi/strength

curl -X POST https://api.astroway.info/v1/bazi/strength \
  -H "X-Api-Key: aw_live_..." \
  -H "Content-Type: application/json" \
  -d '{ "date": "1990-05-15", "time": "14:30:00", "timezoneOffset": 8 }'

const res = await fetch('https://api.astroway.info/v1/bazi/strength', {
  method: 'POST',
  headers: {
    'X-Api-Key': process.env.ASTROWAY_API_KEY,
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    "date": "1990-05-15",
    "time": "14:30:00",
    "timezoneOffset": 8
  }),
});
const { ok, data, error } = await res.json();
if (!ok) throw new Error(error.message);
console.log(data);

import os, requests

r = requests.post(
    'https://api.astroway.info/v1/bazi/strength',
    headers={'X-Api-Key': os.environ['ASTROWAY_API_KEY'], 'Content-Type': 'application/json'},
    json={
      'date': "1990-05-15",
      'time': "14:30:00",
      'timezoneOffset': 8
    },
)
result = r.json()
if not result['ok']:
    raise RuntimeError(result['error']['message'])
print(result['data'])

<?php
use GuzzleHttp\Client;

$client = new Client(['base_uri' => 'https://api.astroway.info/v1/']);
$r = $client->post('bazi/strength', [
    'headers' => ['X-Api-Key' => getenv('ASTROWAY_API_KEY')],
    'json' => [
        'date' => '1990-05-15',
        'time' => '14:30:00',
        'timezoneOffset' => 8,
    ],
]);
$result = json_decode($r->getBody(), true);
if (!$result['ok']) throw new \RuntimeException($result['error']['message']);
print_r($result['data']);

The support-and-suppress reading over the weighted hidden-stem count, with the three classical criteria (season, root, allies) reported unweighted and the favourable elements that follow. The caveat names both limits: the month is counted like any other branch, and the cut points are this API’s convention.

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

Request Body^required

application/json

object

date required

string

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

time

string

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

timezoneOffset

Ignored when timezone is sent.

number

>= -14 <= 14

timezone

IANA zone name such as Europe/Kyiv, or auto to look the zone up from latitude and longitude. The server takes the offset that zone kept at this local date and time, summer time included, and uses it in place of timezoneOffset. A clock time that happened twice takes the first occurrence; one skipped when clocks went forward takes the offset from before the change. Abbreviations such as EST are refused. Before 1970 the tz database is not reliable for every place, so send timezoneOffset when the local clock is known.

string

longitude

number

>= -180 <= 180

trueSolarTime

boolean

dayBoundary

string

Allowed values: 23:00 midnight

language

string

stageSchool

string

Allowed values: classical unified

includeFullTable

boolean

includeLuck

boolean

gender

string

Allowed values: male female

Example

{
  "date": "1990-05-15",
  "time": "14:30:00",
  "timezoneOffset": 8
}

Responses

200

Successful calculation

application/json

object

boolean

data

object

solarYear

number

nullable

pillars

Array<object>

nullable

object

name

string

nullable

stem

string

nullable

branch

string

nullable

pillar

string

nullable

dayMaster

object

stem

string

nullable

element

string

nullable

elementName

string

nullable

polarity

string

nullable

strength

object

framework

string

nullable

supportScore

number

nullable

drainScore

number

nullable

supportRatio

number

nullable

verdict

string

nullable

hasSeason

boolean

nullable

hasRoot

boolean

nullable

hasAllies

boolean

nullable

favourableElements

Array<string>

nullable

unfavourableElements

Array<string>

nullable

caveat

string

nullable

favourableElementNames

Array<string>

nullable

unfavourableElementNames

Array<string>

nullable

notes

Array

nullable

methodology

string

nullable

source

string

nullable

disclaimer

string

nullable

Example

{
  "ok": true,
  "data": {
    "solarYear": 1990,
    "pillars": [
      {
        "name": "year",
        "stem": "Geng",
        "branch": "Wu",
        "pillar": "Geng-Wu"
      },
      {
        "name": "month",
        "stem": "Xin",
        "branch": "Si",
        "pillar": "Xin-Si"
      },
      {
        "name": "day",
        "stem": "Geng",
        "branch": "Chen",
        "pillar": "Geng-Chen"
      },
      {
        "name": "hour",
        "stem": "Gui",
        "branch": "Wei",
        "pillar": "Gui-Wei"
      }
    ],
    "dayMaster": {
      "stem": "Geng",
      "element": "Metal",
      "elementName": "Метал",
      "polarity": "Ян"
    },
    "strength": {
      "framework": "扶抑 support-and-suppress",
      "supportScore": 3.9,
      "drainScore": 3.1,
      "supportRatio": 0.557,
      "verdict": "strong",
      "hasSeason": false,
      "hasRoot": true,
      "hasAllies": true,
      "favourableElements": [
        "Water",
        "Wood",
        "Fire"
      ],
      "unfavourableElements": [
        "Earth",
        "Metal"
      ],
      "caveat": "One framework of several, and the thresholds are ours. 扶抑 weighs support against drain; 調候, 通關, 病藥 and 專旺 read the same chart by other rules and can reach the opposite verdict, and a chart near the boundary is exactly where they part. Two limits worth stating plainly: the ratio counts the month branch exactly like the other three, where the tradition weighs the month above all, and the 0.55 / 0.45 cut points are a convention of this API rather than a canonical rule. The three classical criteria are reported unweighted beside the ratio, so a reader who weighs the month can reach their own verdict from the same inputs.",
      "favourableElementNames": [
        "Вода",
        "Дерево",
        "Вогонь"
      ],
      "unfavourableElementNames": [
        "Земля",
        "Метал"
      ]
    },
    "notes": [],
    "methodology": "扶抑 support-and-suppress over the weighted hidden-stem count. Everything producing or sharing the day master supports it; everything else drains it. The three classical criteria (得令 season, 得地 root, 得勢 allies) are reported unweighted beside the ratio so a reader can apply their own weighting.",
    "source": "子平真詮 (Shen Xiaozhan, Qing), public domain",
    "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

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

application/json

Example

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

Корисно?

Запропонувати правку

// Назад

Branch and stem interactions

Далі //

Day Master

Day-master strength

Authorizations

Parameters

Query Parameters

Example

Example

Request Body required

Example

Responses

200

Example

400

Example

401

Example

Request Body^required