PriceDNA API
Property analysis, geocoding and rent, as JSON, from your own code.
Personalized real estate intelligence, as an API.
System status
Each has its own reference. One key works for all three.
Property report, as JSON: the price your goal can support, and every section behind it.
POST /v1/property
Addresses to points and points to the nearest address, with the census tract and flood risk when you ask.
POST /v1/geocode
POST /v1/reverse
Typical rent and its range by bedroom count, with yearly growth, for any US place.
POST /v1/rent
Higher volume, custom data, or a custom integration. Tell us what we can help with.
Every account can make keys, on every plan.
Create a free account, then make a key in the API console.
Send your key in the X-PriceDNA-API-Key header on every request.
X-PriceDNA-API-Key
X-PriceDNA-API-Key: $PRICEDNA_KEY Content-Type: application/json
Keep your key server-side only. Requests and responses are JSON.
Every plan includes all three APIs. Paid plans include more.
The Geocoding and Rent APIs take up to 100 rows per request. See paid plans.
All three APIs, in one OpenAPI 3.1 file.
Download the OpenAPI spec
Errors usually arrive as problem details (RFC 9457), sent as application/problem+json.
application/problem+json
validation-error
errors
invalid-request
Idempotency-Key
unauthorized
no-new-properties-left
new_properties_left
new_properties_per_cycle
resets_at
forbidden
not-found
request-in-progress
Retry-After
idempotency-key-reused
rate-limited
no-points-left-today
points_left
points_needed
no-rent-checks-left
rent_checks_left
service-unavailable
server-error
HTTP/1.1 400 Bad Request Content-Type: application/problem+json { "type": "https://www.pricedna.co/api#error-validation-error", "title": "Your request has invalid fields", "status": 400, "detail": "Your request has invalid fields", "errors": [ { "field": "number_of_units", "detail": "Must be between 1 and 500." } ] }