---
title: "Western daily factors"
method: POST
path: "/v1/western/daily-factors"
tags: ["Western Astrology"]
---

# Western daily factors

`POST /v1/western/daily-factors`

## Request

- Base URL: `https://api.asterwise.com`
- URL: `https://api.asterwise.com/v1/western/daily-factors`
- Auth: HTTP bearer

Every Western factor for one person on one day, in one shape, with no weighting. Each factor carries its raw value and range, its frame, the verdict Lilly's rules give, the rule's source, the significations it touches and the time it holds. Covers every transit-to-natal aspect with its exact time, each transiting planet's sign, dignity and natal house, the Moon's phase, sign changes and void-of-course periods, the planetary hours, and the lord of the year from annual profections. Uranus, Neptune and Pluto carry no verdict because the classical texts give none.

## Request body

- WesternDailyFactorsRequest
  - `location` string, nullable: City name to resolve to lat/lon/tz automatically. Example: 'Mumbai' or 'New Delhi, India'. If provided, latitude, longitude and timezone are not required.
  - `name` string: Person name associated with the birth record
  - `date` string, required: Birth date in YYYY-MM-DD format
  - `time` string, nullable: Birth time in HH:MM 24-hour format. If omitted, the chart is cast for 06:00 local time (not a sunrise chart) and birth_time_provided is false: houses, the Ascendant, the sect and the Moon's exact degree are then approximate.
  - `latitude` number, nullable: Latitude. Required if location not provided.
  - `longitude` number, nullable: Longitude. Required if location not provided.
  - `timezone` string, nullable: IANA timezone. Required if location not provided (unless utc_offset is given). For dates before the zone adopted a standard time, the birthplace's local mean time (longitude / 15 hours) is used.
  - `utc_offset` string, nullable: Optional explicit UTC offset of the birth time, as ±HH:MM or ±HH:MM:SS (e.g. '+04:51:31' for Bombay mean time). Overrides the offset `timezone` would give. Use it when the birth record states the offset, or for historical local times the IANA database cannot represent.
  - `ayanamsa` 'lahiri' | 'raman' | 'kp' | 'tropical': Ignored on Western endpoints: positions are always tropical (no ayanamsa). Accepted so one birth object can be sent to Vedic and Western endpoints alike.
  - `house_system` 'placidus' | 'koch' | 'equal' | 'whole_sign': Natal house system for the natal_house of each transiting planet.
  - `target_date` string, nullable: Day to read (YYYY-MM-DD, civil day in target_timezone). Defaults to today in the birth timezone.
  - `target_timezone` string, nullable: IANA timezone of the day. Defaults to the birth timezone.
  - `target_latitude` number, nullable: Place for the planetary hours. Defaults to the birthplace.
  - `target_longitude` number, nullable: Longitude of that place, east positive. Defaults to the birthplace.

## Response `200`

Successful Response

- ApiResponseWesternDailyFactorsResponse
  - `success` boolean: True if the request succeeded
  - `message` string: Human-readable status message
  - `data` WesternDailyFactorsResponse, required
    - `birth_time_provided` boolean, required
    - `date` string, required
    - `timezone` string, required
    - `instant_utc` string, required: The moment used for the day's transit snapshot: local noon.
    - `house_system` string, required
    - `natal` object, required
    - `frames` object, required
    - `factors` DailyFactor[], required: Groups: aspect, transit, moon_phase, void_of_course, planetary_hour, profection.
      - `id` string, required: Stable factor id, e.g. gochar.saturn, tarabala.12, natal_contact.saturn.moon.
      - `group` string, required: gochar, sade_sati, chandra_ashtama, tarabala, chandrabala, dasha, dasha_transit, natal_contact, panchanga, moon_phase.
      - `name` string, required
      - `planet` string, nullable
      - `frame` 'from_moon' | 'from_lagna' | 'natal_planet' | 'natal_house' | 'none', required: What the houses or distances are counted from. See frames.
      - `value` object, required: The raw numbers and flags of this factor.
      - `ranges` object, required: The documented range of each numeric value, e.g. bindus [0, 8].
      - `verdict` 'favorable' | 'unfavorable' | 'neutral', nullable: What the classical rule says, or null when the texts give no single verdict.
      - `verdict_rule` string, nullable: Which rule produced the verdict, in words.
      - `rule_source` string, nullable: Text and chapter the rule comes from.
      - `significations` string[], required: Ids from /v1/astro/significations touched by this factor.
      - `time` FactorTime, required
        - `kind` 'state' | 'span' | 'instant', required: state: holds for the whole day; span: start to end; instant: one moment.
        - `start` string, nullable
        - `end` string, nullable
        - `start_utc` string, nullable
        - `end_utc` string, nullable
        - `at_utc` string, nullable
      - `depends_on_birth_time` boolean, required: True when an unknown birth time can change this factor.
    - `counts` object, required: How many factors carry each verdict. A count, not a score.
    - `note` string, required

## Other responses

- `401`: Authentication failed
- `403`: Authorization failed
- `404`: Resource not found
- `413`: Payload too large
- `422`: Validation error
- `429`: Rate limit exceeded
- `500`: Internal error
- `502`: Upstream provider error
- `503`: Service unavailable

---

[API](https://skmtc.dev/asterwise/apis/asterwise-api.md) · [All operations](https://skmtc.dev/asterwise/apis/asterwise-api/llms.txt) · [OpenAPI document](https://skmtc.dev/asterwise/apis/asterwise-api/revisions/3c4bbb1194e2?raw)