Kadrin Docs Kadrin Batch

Geography

Look up official areas and draw drive-time areas.

Draw drive-time areas (2 credits each)

POST /v1/isochrones

Returns the outline of everywhere you can reach from a point within a set number of minutes by car, on foot or by bike, using travel times without traffic delays. This outline is called an isochrone.

Use this when you need the shape itself, for example to draw it on a map. To get numbers for the area, send it to /enrich instead; you don't need to draw it first. Each area is drawn on the roads in the release you choose, so the same request always gets the same outline. If one area fails, the others still come back; the failed area carries an error and isn't charged.

The roads come from OpenStreetMap. Wherever you show an outline, credit "© OpenStreetMap contributors".

Parameters

NameInTypeWhat it is
Kadrin-Max-Creditsheaderinteger

The most you're willing to spend on this request. If the estimated cost is higher, we stop before running it, charge nothing, and return error 402.

Request body

object as application/json.

FieldTypeWhat it is
isochrones
required
array of any

The drive-time areas to draw, up to 100.

simplifyboolean

Smooth the outline so it's smaller to download. On by default, and the outline /enrich uses for the same area. Off, the outline has about five times as many corner points. Default true.

releasestring

Which data release's roads to use (a frozen snapshot, such as 2026.12). Name one to get the same outline every time; latest uses the newest. Default "latest".

Answers

StatusWhenBody
200The outlines. An area that failed has an error instead of a geometry.object
400Something went wrong. The response explains what happened and what to do next. Failed requests are never charged. (The format is RFC 9457, a standard layout for API errors.)Problem
401Something went wrong. The response explains what happened and what to do next. Failed requests are never charged. (The format is RFC 9457, a standard layout for API errors.)Problem
402Something went wrong. The response explains what happened and what to do next. Failed requests are never charged. (The format is RFC 9457, a standard layout for API errors.)Problem
413Something went wrong. The response explains what happened and what to do next. Failed requests are never charged. (The format is RFC 9457, a standard layout for API errors.)Problem
422Something went wrong. The response explains what happened and what to do next. Failed requests are never charged. (The format is RFC 9457, a standard layout for API errors.)Problem
429Too many requests in a short time. Wait the number of seconds in Retry-After, then try again.Problem
503Something went wrong. The response explains what happened and what to do next. Failed requests are never charged. (The format is RFC 9457, a standard layout for API errors.)Problem

Find official areas by name or location

GET /v1/geographies/lookup

Send a place name (such as 'Cook County, IL' or a ZIP code), or a latitude and longitude, and get back the official areas that match or contain it. Each comes with its GEOID, the ID number the government gives each area, which you can then send to /enrich.

Send either q, or both lat and lon. A name can be followed by a comma and a state, such as 'Boston, MA', and small misspellings are fine. You get up to 10 matches, closest first. Congressional and state legislative districts aren't available yet. Free, up to 600 requests a minute.

Parameters

NameInTypeWhat it is
latquerynumber

Latitude (how far north), such as 42.36 for Boston.

lonquerynumber

Longitude (how far east or west; negative in the US), such as -71.06 for Boston.

qquerystring

A place name, county, city, ZIP code or district.

levelsqueryarray of GeographyLevel

Only return these kinds of area, such as county or tract. Separate several with commas.

Answers

StatusWhenBody
200Matching areas.object
400Something went wrong. The response explains what happened and what to do next. Failed requests are never charged. (The format is RFC 9457, a standard layout for API errors.)Problem
401Something went wrong. The response explains what happened and what to do next. Failed requests are never charged. (The format is RFC 9457, a standard layout for API errors.)Problem
422Something went wrong. The response explains what happened and what to do next. Failed requests are never charged. (The format is RFC 9457, a standard layout for API errors.)Problem
429Too many requests in a short time. Wait the number of seconds in Retry-After, then try again.Problem