What you can ask for
Scores near a place
GET /v1/scores: the open fields around a postcode, a town or village, an address with a postcode, or a point. Nearest first, with nearby housing applications.One field
GET /v1/fields/{field_id}: one field by the field_id the scores give, with the housing applications within 1 km.Your usage
GET /v1/usage: your calls this month against your quota.The basics
- Base URL:
https://api.checkthatfield.com/v1 - Format: JSON in every answer, errors included.
- Versioning: the version is in the path. Everything here is
/v1. - Keys: every call needs a secret key. See Authentication.
- OpenAPI: the machine-readable description is at
https://api.checkthatfield.com/v1/openapi.json.
What the answers include
Each field comes with:- its score, from 0 to 100
- its band: Low (0–19), Moderate (20–44), High (45–69) or Very High (70–100)
- two horizons: the likelihood of housing within about 5 and about 15 years
- the top reasons behind the score, at most three, in words. Each says whether it raises or lowers the score and how much (
strong,moderate,slight, orcap). There are no numbers.
The API gives what the free report gives. The sources, the records behind each reason and the full reasoning stay in the deep report on checkthatfield.com. Each field’s
report_url links to it on our map."status": "pending" and is queued for scoring. See Pending scores.
Your first request
A response, trimmed
[longitude, latitude]. Distances are in metres: from the postcode or point, or from the edge of the built-up area when you ask about a town or village.
Next
Authentication
Get a key and send it.
Quotas and limits
What counts, and how fast you can call.
Errors
Every error code and what to do.
Attribution
What you must show beside the data.