If you're not familiar with EveryBlock, read our about page and FAQ. The main take away is that EveryBlock gathers, organizes and publishes content at the level of neighborhood and city block. Given a location, we can tell you what's been happening there recently.

EveryBlock serves 10 metros: Boston, Chicago, Denver, Fresno, Hialeah, Houston, Medford, Nashville, Philadelphia and Seattle. It's technically not the entire metro area -- just the city proper -- but we call these metros for future-compatibility.

EveryBlock offers distinct pages for neighborhoods, ZIP codes and, in some cases, city-specific entities such as wards, school districts, police districts, etc. These are known as location types. A specific item in a location type is called a location. For example, Albany Park is a location of the neighborhood type.

The GIS Boundary Data provides you with access to all the location boundaries, across all of the current EveryBlock metros. This includes:

  • Location type - for example neighborhood, zip code, etc.
  • Location name - as it is displayed in EveryBlock. For locations like neighborhoods, where there is no single definition, names can vary from the way they are named in other sources
  • Boundaries - an array of geographic coordinates (latitude/longitude points) that form a polygon that represent the geography of the location. These are as they are displayed in EveryBlock. In general EveryBlock obtains geographic information from official sources such as GIS departments from city, state and federal agencies. In some cases, for practical reasons, the boundaries are simplified (some points are removed). For ZIP codes we use ZCTA's from TIGER.
  • Centroid - for some applications it is useful to provide a coordinate that can represent the center of a location. Given that locations have irregular shapes we calculate the centroid for each location.

This is a simple REST-style Web API. Make GET requests via HTTP, and we'll return a document with the content you requested. The document format can specified in the request. The supported formats are JSON, JSONP, and XML. If no format is specified, endpoints default to JSON.

Format types can be specified via an Accept header or extension within the URL.

        Headers:
            JSON: Accept: application/json
            JSONP: Accept: application/javascript
            XML: Accept: application/xml

        Extensions:
            JSON: .json
            JSONP: .jsonp
            XML: .xml
    

An example using extensions: https://api.everyblock.com/content/.json

All endpoints are hosted on https://api.everyblock.com and require authentication. Authentication is handled with an API token in the HTTP request headers. Get an API token here.

Here is an example:

      GET /content/ HTTP/1.1
      Host: api.everyblock.com
      Authorization: Token 90fe24d329973b71272faf3f5d17a8602bff996b
    

Here is an example using the token URL parameter:

        https://api.everyblock.com/content/chicago/?token=90fe24d329973b71272faf3f5d17a8602bff996b
    

Returns Boundary Data Geometries in GeoJSON format for various Location Types, along with key properties such as Location Name, Centroids, etc..

/gis/[metro]/[location type]/

Eg.

/gis/philly/zipcodes/

or

/gis/houston/neighborhoods/

URL Parameters:

  • metro -- A metro's short_name. This can be found via the Content Endpoint
  • location type -- Available location types vary with metro but common types are: zipcodes, neighborhoods and wards.