Skip to content
RealtyDataAPI
All endpoints

Autocomplete Cities, ZIP Codes, Neighborhoods, Counties & Street Addresses

GET/v1/locations/autocomplete2 Credits / Call($0.08–$0.20 / 1K calls)· Updated 2026-11-15

Direct Answer · PropTech Engineering Summary

GET /v1/locations/autocomplete resolves partial user keystrokes (?query=78701, ?query=Austin, ?query=Beverly Hills) into structured geographic boundaries with area_type (postal_code, city, neighborhood, county, address), canonical id tokens (city:tx_austin, postal_code:78701), state codes, and centroid lat/lng in ~30ms warm / <500ms live for 2 Credits per call.

Honest Trade-Offs & Scope Boundaries

  • →Designed to power typeahead search boxes and normalize ambiguous user prompts before dispatching /v1/properties/search or /v1/redfin/search.
  • →Zero credits charged if a nonsensical query string returns 0 boundary suggestions.

Resolve user search input (78701, Austin, Beverly Hills) into structured real estate boundaries with canonical id (postal_code:78701 or city:tx_austin), coordinates, and area type. Cost: 2 Credits per call.

Parameters

  • querystringrequired

    Partial or complete ZIP code, city, neighborhood, school district, or address.

    Example: Austin

  • limitinteger (1 to 20)

    Maximum location suggestions to return (1-20, default 10).

Example Request (cURL / Python / JavaScript)

curl "https://api.realtydataapi.com/v1/locations/autocomplete?query=Austin" \
  -H "x-api-key: rl_live_your_api_key"

Live Response Preview

{
  "code": 0,
  "provider": "https://realtydataapi.com",
  "status": "ok",
  "data": {
    "query": "Austin",
    "count": 2,
    "suggestions": [
      {
        "id": "city:tx_austin",
        "area_type": "city",
        "label": "Austin, TX",
        "city": "Austin",
        "state_code": "TX",
        "country": "USA",
        "latitude": 30.2672,
        "longitude": -97.7431
      },
      {
        "id": "postal_code:78701",
        "area_type": "postal_code",
        "label": "78701, Austin, TX",
        "city": "Austin",
        "state_code": "TX",
        "postal_code": "78701",
        "country": "USA",
        "latitude": 30.2711,
        "longitude": -97.7437
      }
    ]
  },
  "meta": {
    "request_id": "req_rl_auto_aus",
    "endpoint": "/v1/locations/autocomplete",
    "credits_charged": 2,
    "cached": true,
    "took_ms": 19
  }
}

Response Fields

Structured location suggestions with canonical search IDs.

FieldTypeSample / Notes
codeintegerExample: 0
providerstringExample: https://realtydataapi.com
statusstringExample: ok
dataobject
querystringExample: Austin
countintegerExample: 5
suggestionsarray of object
idstringExample: city:tx_austin
area_typestringExample: city
labelstringExample: Austin, TX
citystringExample: Austin
state_codestringExample: TX
postal_codestringExample: 78701
latitudenumberExample: 30.2672
longitudenumberExample: -97.7431
metaResponseMeta
request_idstringExample: req_rl_78701_9a2f
endpointstringExample: /v1/properties/search
credits_chargedintegerExample: 40
cachedbooleanExample: true
took_msintegerExample: 28

Status Codes

200
Structured location suggestions with canonical search IDs.