> ## Documentation Index
> Fetch the complete documentation index at: https://api.housera.ro/llms.txt
> Use this file to discover all available pages before exploring further.

# Location

> The coordinates, city, and street of a listing, and how Housera normalizes them.

Any listing has a precise location on the map. Searching on Housera starts from the map, so the coordinates are just as important as the price.

## Fields

<ParamField body="latitude" type="number" required>
  Latitude of the point, between -90 and 90. Example: `47.1752`.
</ParamField>

<ParamField body="longitude" type="number" required>
  Longitude of the point, between -180 and 180. Example: `27.5701`.
</ParamField>

<ParamField body="city" type="string" required>
  Location (city, commune, or village). Example: `Iași`, `Miroslava`, `București`.
</ParamField>

<ParamField body="street" type="string" required>
  The name of the street, including its type: `Strada Vasile Lupu`, `Bulevardul Lascăr Catargiu`. If the property is on a nameless road, send the local designation used (for example `Drumul Comunal 12`).
</ParamField>

<ParamField body="street_number" type="string">
  The number, as text: `12`, `7A`, `Bl. C3`. Optional, since many rural streets do not have numbering.
</ParamField>

<ParamField body="county" type="string">
  The county: `Iași`, `Cluj`, `București`. Diacritics are optional. Recommended: without county, Housera cannot match the location with the places registry (see below).
</ParamField>

<ParamField body="area" type="string">
  The neighborhood or area: `Copou`, `Tătărași`, `Piața Victoriei`.
</ParamField>

<ParamField body="country" type="string">
  The ISO 3166-1 alpha-2 code of the country, for example `RO`. Lowercase letters are accepted and converted to uppercase.
</ParamField>

<ParamField body="landmark" type="string">
  A nearby landmark, of no more than 120 characters, displayed after the address: `lângă Palas Mall`.
</ParamField>

## The coordinates are the source of truth

The point (`latitude`, `longitude`) is the one that appears on the map and by which the listing is found in search. Send the property point, not the city center:

* if your system has the coordinates from the address geocoding, use them;
* if it doesn't, geocode the full address (street, number, locality, county) before sending;
* check the order: in JSON, `latitude` is the one around 44–48 for Romania, while `longitude` is the one around 20–30.

<Warning>
  A common mistake is reversing latitude with longitude. The result is a listing placed in another corner of the world, which nobody can find in search. The rules only check for valid ranges, not whether the point is in the submitted location.
</Warning>

## Normalization through the places registry

Housera has a registry of localities and neighborhoods. When you send the county, locality, and area, their names are brought to the spelling in the registry:

| You send | It saves |
| - | - |
| `"county": "IASI", "city": "iasi"` | county Iași, city `Iași` |
| `"county": "Iasi", "city": "Iasi", "area": "copou"` | city `Iași`, area `Copou` |

This way, your listings appear correctly in searches by city or neighborhood, however they are written in your system. A name that the registry does not recognize is not rejected: it is kept exactly as you sent it.

You do not need to resolve the location beforehand: send the text you have, and Housera will make the match. For matching, it needs the county, so send it every time.

In response, the location looks like this:

```json theme={null}
"location": {
  "country": "RO",
  "county": "iasi",
  "city": "Iași",
  "area": "Copou",
  "lat": 47.1752,
  "lng": 27.5701,
  "precision": "exact"
}
```

`county` comes as a short identifier, without diacritics (`iasi`, `cluj`, `bucuresti`), and `city` and `area` as names.

## Accuracy

The field `location.precision` can be `exact` or `approximate`. Listings published via API always have the exact location, as you sent it, just like those added from the form.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.