---
title: "Resolve Place"
method: POST
path: "/api/v1/astrology/resolve-place"
tags: ["astrology-api"]
---

# Resolve Place

`POST /api/v1/astrology/resolve-place`

## Request

- Base URL: `https://api.stellara.natlex.it` (the document declares no server; this is the origin it was published from)
- URL: `https://api.stellara.natlex.it/api/v1/astrology/resolve-place`
- Auth: none declared

Place name -> coordinates + IANA timezone, and (optionally) a naive
local birth time -> tz-aware ``birth_datetime`` with the historically
correct UTC offset. Lets an agent go from "Warsaw, 14:30" to a valid
natal request without guessing coordinates or DST rules.

## Request body

- ResolvePlaceRequest
  - `place` string, required: Free-text place of birth, e.g. 'Warsaw, Poland' or 'Варшава'
  - `local_datetime` string, nullable: Local wall-clock birth time WITHOUT an offset: 'YYYY-MM-DDTHH:MM[:SS]' or 'YYYY-MM-DD' (date only = 12:00 assumed). The offset is derived from the place's IANA zone, including historical DST.

## Response `200`

Successful Response

- AstrologyResolvePlaceResponse: Place name (+ optional naive local time) -> coordinates, IANA zone and a ready-to-use tz-aware ``birth_datetime`` for the natal endpoints.
  - `query` string, required
  - `display_name` string, required
  - `latitude` number, required
  - `longitude` number, required
  - `timezone` string, required
  - `local_datetime` string, nullable
  - `utc_offset` string, nullable
  - `birth_datetime` string, nullable
  - `birth_datetime_utc` string, nullable
  - `time_assumed_noon` boolean
  - `local_time_ambiguity` string, nullable
  - `age_years` integer, nullable
  - `source` string, required

## Other responses

- `422`: Validation Error

---

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