accessibility.cloud API

accessibility.cloud allows you to request accessibility data via HTTP in JSON format.

accessibility.cloud API

Features

Free access (for non-commercial purposes - if you're an NGO or commercial organization, let's talk!)
Allow your users to find places by location, category, or other metadata
Augment your own data with accessibility information
Requests over HTTP(S)
GeoJSON-compatible output format
Get data about places, elevators, escalators, and facility disruptions

Getting started

Sign up for accessibility.cloud
Create an organization on the web page
Add an app for your organization
- The created app comes with a free API token that allows you to make HTTP requests to our API.
- To start using the API, follow the instructions in your app's settings on the web page.
If you start on the command line, we recommend piping your curl output through jq when testing API requests in the command line. jq can be installed using your favorite package manager (e.g. with apt-get install jq on Debian-based Linux or brew install jq on Macs).

Cached vs. non-cached base URLs

accessibility.cloud's API is available via two base URLs:

Cached: https://accessibility-cloud-v2.freetls.fastly.net – This is the recommended base URL for most use cases. It caches responses up to 5 minutes using a CDN, so data included in the responses can lag behind the database content. Depending on the complexity of your request, a response to a URL not requested before in the last 5 minutes can take up to several seconds. After that, the server should respond to following requests with the same URL within less than 100ms. If you have a use case that needs <100ms for all requests, write us an email so we can figure out a cache warm-up strategy. In case of a backend downtime, the cache can deliver stale data.
Not cached: https://v2.accessibility.cloud - Use this base URL if you need real-time data directly after an import or a data push process, for example for health monitoring, or to request data directly after an edit. Do not use this base URL for end-user-facing web pages or apps except necessary.

Authentication

For every app you create, you get an authentication token. This token allows you to use the JSON API. To authenticate a single request, supply the token as URL query parameter, e.g. appToken=12345.

Your API token allows you to access the following data:

Your organization's profile data
Content of your own organizations' data sources
Content of other organizations' data sources, if the source
- is not in draft mode
- is accessible for your organization (or publicly available)

Features for all endpoints

Retrieving single documents by their `_id`

If you have the _id value of a document, you can retrieve it using a URL like this:

https://accessibility-cloud-v2.freetls.fastly.net/[TYPE]/[ID].json?appToken=[APP_TOKEN]

Replace [TYPE] with the type of the requested resource (e.g. place-infos – see below for allowed types), [ID] with the document's _id, and [APP_TOKEN] with your app token (see above).

Licensing

Responses containing data that is provided under a specific license contain the licenses of all result in the JSON response. Each license has a _id field. Results of the response can refer to their licenses using this id (using a licenseId field).

Pagination

API result sets are paginated. On one page, maximally 1000 results are returned. To get a specific result page, use the skip parameter with the number of results you want to skip, and the limit parameter to set the maximal number of results you want the server to return. Note that currently, each request creates a DB query in the backend.

Filtering returned fields

To get a specific set of returned JSON fields only (e.g. to save bandwidth), you can use the exclude and include GET query parameters. For both parameters, the server accepts a comma-separated list of field paths, e.g. include=properties.name,geometry.

Embedded related resources

Result list returned via the API often contain references to other documents by ID. See the /place-infos endpoint for an example how to embed related documents directly in the result response list.

Sorting

You can sort results by using the sort parameter. For this parameter, the servers accept a field path, e.g. sort=properties.address. Sort order is ascending by default. If you want to sort in descending order, add a descending=1 parameter to your request.

Error handling

The server uses HTTP status codes for a general categorization of the errors you get back. Typical error codes:

404: The server could not find the resource you requested.
401: Your request was not authenticated (e.g. because the token was missing or invalid)
402: You don't have the necessary privileges to access the requested resource
422: Your request did not have the right format, e.g. you supplied invalid parameters
500: The server could not process your request because there was an internal error.

All error responses from the JSON API contain a JSON body with reason and a details fields. For responses with 422 status code, the details field can contain an array with validation errors for each supplied parameter, e.g. like this:

{
  "error": {
    "reason": "Longitude is required",
    "details": [
      {
        "name": "longitude",
        "type": "required",
        "details": {
          "value": null
        }
      },
      {
        "name": "accuracy",
        "type": "required",
        "details": {
          "value": null
        }
      }
    ]
  }
}

Endpoints

GET /place-infos

Returns place infos (POIs) from arbitrary data sources.

The response is a GeoJSON FeatureCollection.

For requests to this endpoint, the API supports the following parameters:

Include places without known accessibility

By default, the endpoint returns only places that have an accessibility structure set in properties.accessibility.

If you want to include places without set accessibility, add a includePlacesWithoutAccessibility=1 query parameter.

Data source filtering

includeSourceIds: comma-separated list of source ids you want to include, e.g. QGf3sjbSxSpkeNHFm,eWrPejvNrE5AFB7bx
excludeSourceIds: same as includeSourceIds, but excludes specific sources from results. This is helpful if you have your own data source on accessibility.cloud and want to show additional results on a web page without showing your own data source's results twice on the same view.

Location-based search by center/radius

Only use this for queries where a end user explicitly searches places inside the given radius. Please do NOT use this endpoint for data exports. For bigger geographic ranges, split the area into multiple X/Y/Z-tile based queries instead (see below). This ensures that responses can be efficiently cached.

You can request POIs around a specific map location. For this, you have to supply all three of the following parameters:

latitude, longitude: WGS84 geo-coordinates (as floating point strings). When supplied, these coordinates are used as center for a location-based place search.
accuracy: Search radius for location-based place search, in meters (floating point). Maximal allowed value is 10000.

Getting all places inside a X/Y/Z tile

This is the preferred way for fast response times that can be cached by accessibility.cloud's backend. Use this for tiled GeoJSON responses for map libraries like Leaflet.

The backend also allows you to request map tile X/Y position and zoom level (Z). The OpenStreetMaps wiki has an overview about the concept.

Knowing the zoom level you want to request, you can convert your latitude and longitude coordinates to x/y. Note that x/y coordinates refers to the top left corner of the tile, so if you want to use this for a search centered around a point, you have to calculate the position of the top left corner yourself.

x: x coordinate of the map tile you want to request
y: y coordinate of the map tile you want to request
z: zoom level

Filter by metadata

The server has a database for additional metadata-based filter presets that you can use in your queries. If you need a specific query, let the accessibility.cloud team know.

To use a filter, add this parameter:

filter: a String identifying the preset used to filter your data, e.g. at-least-partially-accessible-by-wheelchair.

accessibility.cloud supports the following filter presets:

at-least-partially-accessible-by-wheelchair
fully-accessible-by-wheelchair
not-accessible-by-wheelchair
unknown-wheelchair-accessibility

Filter by category

You can either include or exclude categories by using the following parameters:

includeCategories: comma-separated list of category names to include in the search. All other categories are excluded.
excludeCategories: comma-separated list of category names to exclude in the search. All other categories are included.

Retrieving a PlaceInfo document by its `sourceId` and `originalId`

If you have the originalId and sourceId values of a document, you can retrieve using these parameters:

originalId: the original ID used in the original data source provided externally
sourceId: _id of the data source on accessibility.cloud

Embedding related documents

In the same way, the API allows you to get customized details for results in an embedded related field in the response:

{
  "type": "FeatureCollection",
  "featureCount": 1,
  "related": {
    "licenses": {
      "4HgSTHdeQMA9pvJNM": {             // license of the source below
        "_id": "4HgSTHdeQMA9pvJNM",
        "name": "Public Domain",
        ...
      }
    },
    "sources": {
      "eWrPejvNrE5AFB7bx": {
        "name": "Another data source",
        "licenseId": "4HgSTHdeQMA9pvJNM", // reference to the license above
        ...
      }
    }
  },
  "features": [
    {
      "type": "Feature",
      "geometry": { ... },
      "properties": {
        "sourceId": "eWrPejvNrE5AFB7bx", // reference to the source above
        ...
      }
    }
  ]
}

For example, the response will include a data source document after adding the includeRelated=source parameter.

If given, the includeRelated parameter has to be a comma-separated list of relation names. Allowed relation names for places are:

source
source.organization
source.license
sourceImport
source.language
equipmentInfos
equipmentInfos.disruptions
disruptions

Example request

curl -v 'https://accessibility-cloud-v2.freetls.fastly.net/place-infos.json?appToken=YOUR_APP_TOKEN_HERE&latitude=48.2435&longitude=16.3974&accuracy=1000&includeSourceIds=QGf3sjbSxSpkeNHFm&includeRelated=source' | jq .

Example response

{
  "type": "FeatureCollection",
  "featureCount": 3,
  "related": {
    "licenses": {
      "ksZeCT5iukcsigZhQ": {
        "_id": "ksZeCT5iukcsigZhQ",
        "name": "Accessibility License",
        "plainTextSummary": "A summary…",
        "consideredAs": "restricted",
        "organizationId": "JvmSCpsocEvDcgfkb"
      },
      "sources": {
        "QGf3sjbSxSpkeNHFm": {
          "name": "",
          "licenseId": "ksZeCT5iukcsigZhQ"
        }
      }
    }
  },
  "features": [
    {
      "type": "Feature",
      "geometry": {
        "type": "Point",
        "coordinates": [
          16.39748637322089,
          48.24350856260559
        ]
      },
      "properties": {
        "originalId": "WCANLAGEOGD.325800",
        "category": "toilets",
        "name": "Öffentliche Toilette",
        "address": "Damm autom. selbstr. Familienbadestrand, Bezirk 22, Vienna, Austria",
        "accessibility": {
          "accessibleWith": {
            "wheelchair": true
          }
        },
        "sourceId": "QGf3sjbSxSpkeNHFm",
        "sourceImportId": "yEQBjistheHWLfvG3",
        "_id": "g6DyPyuGPbR2bRHML",
        "distance": 0
      }
    },
    {
      "type": "Feature",
      "geometry": {
        "type": "Point",
        "coordinates": [
          16.391322824757268,
          48.244053162833104
        ]
      },
      "properties": {
        "originalId": "WCANLAGEOGD.325799",
        "category": "toilets",
        "name": "Öffentliche Toilette",
        "address": "Donauinsel autom. selbstr. Beachvolleyballpl., Bezirk 21, Vienna, Austria",
        "accessibility": {
          "accessibleWith": {
            "wheelchair": true
          }
        },
        "sourceId": "QGf3sjbSxSpkeNHFm",
        "sourceImportId": "yEQBjistheHWLfvG3",
        "_id": "nho3WmyqaW52nc6Cs",
        "distance": 460.0797197954276
      }
    },
    {
      "type": "Feature",
      "geometry": {
        "type": "Point",
        "coordinates": [
          16.40251909699923,
          48.23904145814893
        ]
      },
      "properties": {
        "originalId": "WCANLAGEOGD.325782",
        "category": "toilets",
        "name": "Öffentliche Toilette",
        "address": "Donauinsel Anlage NEU 10, Bezirk 21, Vienna, Austria",
        "accessibility": {
          "accessibleWith": {
            "wheelchair": false
          }
        },
        "sourceId": "QGf3sjbSxSpkeNHFm",
        "sourceImportId": "yEQBjistheHWLfvG3",
        "_id": "bJY23bukFmpayGSvA",
        "distance": 620.5354929354854
      }
    }
  ]
}

GET /apps

TODO

GET /categories

Returns all categories known to accessibility.cloud, together with their translated names in the given locale.

Example request

curl 'https://accessibility-cloud-v2.freetls.fastly.net/categories.json?appToken=YOUR_APP_TOKEN_HERE&locale=en' | jq

Example response

{
  "count": 172,
  "totalCount": 172,
  "related": {},
  "results": [
    {
      "_id": "car_sharing",
      "icon": "car_sharing",
      "parentIds": [
        "transport"
      ],
      "translations": {
        "_id": {
          "de": "Carsharing",
          "en": "Car sharing"
        }
      },
      "synonyms": [
        "amenity=car_sharing"
      ]
    },
    ...
  ]
}

GET /disruptions

Returns disruption infos from arbitrary data sources. The response is a GeoJSON FeatureCollection.

For requests to this endpoint, the API supports the following parameters:

Data source filtering

includeSourceIds: comma-separated list of source ids you want to include, e.g. QGf3sjbSxSpkeNHFm,eWrPejvNrE5AFB7bx
excludeSourceIds: same as includeSourceIds, but excludes specific sources from results. This is helpful if you have your own data source on accessibility.cloud and want to show additional results on a web page without showing your own data source's results twice on the same view.

Location-based search

You can request POIs around a specific map location. For this, you have to supply all three of the following parameters:

latitude, longitude: WGS84 geo-coordinates (as floating point strings). When supplied, these coordinates are used as center for a location-based place search.
accuracy: Search radius for location-based place search, in meters (floating point). Maximal allowed value is 10000.

Embedding related documents

You can embed related documents like in the place-infos, equipment-infos and disruptions endpoints.

If given, the includeRelated parameter has to be a comma-separated list of relation names. Allowed relation names for places are:

source
source.organization
source.license
sourceImport
source.language
placeInfo
equipmentInfos

Example request

curl -v 'https://accessibility-cloud-v2.freetls.fastly.net/disruptions.json?appToken=YOUR TOKEN HERE&includeRelated=equipmentInfo&limit=1' |

Example response

{
  "type": "FeatureCollection",
  "featureCount": 1,
  "totalFeatureCount": 159,
  "related": {
    "equipmentInfos": {
      "KNzmFCkq9Fod9jAKF": {
        "type": "Feature",
        "geometry": {
          "type": "Point",
          "coordinates": [
            13.3869289,
            52.52093915
          ]
        },
        "properties": {
          "category": "escalator",
          "originalId": "10095415",
          "originalPlaceInfoId": "527",
          "isWorking": false,
          "sourceId": "nwccXsd9WMekvFs3r",
          "sourceImportId": "ZNCp79ofnzXDCTPQi",
          "placeInfoId": "vrQ3hnmdZnaMvmp3m",
          "_id": "KNzmFCkq9Fod9jAKF"
        }
      }
    },
    "licenses": {
      "ns5HmC6xFrakRdoJ5": {
        "_id": "ns5HmC6xFrakRdoJ5",
        "name": "CC-BY 4.0 International",
        "shortName": "CC-BY 4.0 Int.",
        "websiteURL": "https://creativecommons.org/licenses/by/4.0/",
        "fullTextURL": "https://creativecommons.org/licenses/by/4.0/legalcode",
        "consideredAs": "CCBY",
        "organizationId": "6ZhFGZ97omm6uKyfn"
      }
    }
  },
  "features": [
    {
      "type": "Feature",
      "geometry": {
        "type": "Point",
        "coordinates": [
          13.386934058,
          52.520336851
        ]
      },
      "properties": {
        "originalId": "30400715",
        "originalEquipmentInfoId": "10095415",
        "originalPlaceInfoId": "527",
        "category": "escalator",
        "lastUpdate": {
          "$date": 1510119891000
        },
        "sourceId": "9JcQxdE2PAFxLTEJc",
        "sourceImportId": "wyvKYaPYNR54AwtQ6",
        "placeInfoId": "vrQ3hnmdZnaMvmp3m",
        "equipmentInfoId": "KNzmFCkq9Fod9jAKF",
        "_id": "SdGFAf7ZgmSz2YERS"
      }
    }
  ]
}

GET /equipment-infos

Returns equipment / facility infos from arbitrary data sources, for example elevators and escalators.

The response is a GeoJSON FeatureCollection.

For requests to this endpoint, the API supports the following parameters:

Data source filtering

includeSourceIds: comma-separated list of source ids you want to include, e.g. QGf3sjbSxSpkeNHFm,eWrPejvNrE5AFB7bx
excludeSourceIds: same as includeSourceIds, but excludes specific sources from results. This is helpful if you have your own data source on accessibility.cloud and want to show additional results on a web page without showing your own data source's results twice on the same view.

Location-based search

You can request POIs around a specific map location. For this, you have to supply all three of the following parameters:

latitude, longitude: WGS84 geo-coordinates (as floating point strings). When supplied, these coordinates are used as center for a location-based place search.
accuracy: Search radius for location-based place search, in meters (floating point). Maximal allowed value is 10000.

Embedding related documents

You can embed related documents like in the place-infos endpoint.

For example, the response will include associated place infos and disruptions after adding the includeRelated=placeInfo,disruptions parameter.

If given, the includeRelated parameter has to be a comma-separated list of relation names. Allowed relation names for places are:

source
source.organization
source.license
sourceImport
source.language
placeInfo
disruptions

Example request

curl -v 'https://accessibility-cloud-v2.freetls.fastly.net/equipment-infos.json?appToken=YOUR_TOKEN_HERE&includeRelated=disruptions&limit=1' | jq .

Example response

{
  "type": "FeatureCollection",
  "featureCount": 1,
  "totalFeatureCount": 3010,
  "related": {
    "disruptions": {},
    "licenses": {
      "ns5HmC6xFrakRdoJ5": {
        "_id": "ns5HmC6xFrakRdoJ5",
        "name": "CC-BY 4.0 International",
        "shortName": "CC-BY 4.0 Int.",
        "websiteURL": "https://creativecommons.org/licenses/by/4.0/",
        "fullTextURL": "https://creativecommons.org/licenses/by/4.0/legalcode",
        "consideredAs": "CCBY",
        "organizationId": "6ZhFGZ97omm6uKyfn"
      }
    }
  },
  "features": [
    {
      "type": "Feature",
      "geometry": {
        "type": "Point",
        "coordinates": [
          12.07710864,
          50.8825014
        ]
      },
      "properties": {
        "category": "elevator",
        "originalId": "10378163",
        "originalPlaceInfoId": "2073",
        "isWorking": true,
        "sourceId": "nwccXsd9WMekvFs3r",
        "sourceImportId": "ZNCp79ofnzXDCTPQi",
        "placeInfoId": "4mMrcqMMxkDxCQdJn",
        "_id": "dXNpJfzyaTGMQ2NtF"
      }
    }
  ]
}

GET /global-stats

This API endpoint returns the time series that accessibility.cloud calculates every time it finishes an import.

Series filtering

name: name of the statistic series you want to get. The following series are available:
- Meteor.users
- PlaceInfos
- Sources
- Organizations
- PlaceInfos.withoutDrafts
- EquipmentInfos.withoutDrafts
- EquipmentInfos.withoutDrafts.onlyEscalators
- EquipmentInfos.withoutDrafts.onlyBrokenEscalators
- EquipmentInfos.withoutDrafts.onlyElevators
- EquipmentInfos.withoutDrafts.onlyBrokenElevators
- Disruptions.withoutDrafts
- Disruptions.withoutDrafts.onlyEscalators
- Disruptions.withoutDrafts.onlyElevators
- Sources.withoutDrafts

Example request

This requests only one value with the latest known number of elevators that are out-of-service. Note that you need to specify that the backend should sort the returned data.

curl 'https://accessibility-cloud-v2.freetls.fastly.net/global-stats.json?name=EquipmentInfos.withoutDrafts.onlyBrokenElevators.count&appToken=YOUR_TOKEN_HERE&sort=date&descending=1&limit=1' | jq

Example response

{
  "count": 1,
  "totalCount": 7,
  "related": {},
  "results": [
    {
      "_id": "EawJ6KEdXDDmG8Fkj",
      "name": "EquipmentInfos.withoutDrafts.onlyBrokenElevators.count",
      "date": {
        "$date": 1512478862900
      },
      "value": 99
    }
  ]
}

GET /languages

TODO

GET /licenses

TODO

GET /organizations

TODO

GET /source-imports

TODO

GET /sources

TODO

GET /captcha

While not really part of the json apis, the captcha api returns a visual captcha that requires solving before the /image-upload API can be used.

Example request

curl 'https://accessibility-cloud-v2.freetls.fastly.net/captcha?appToken=YOUR_TOKEN_HERE'

Example response

<svg xmlns="http://www.w3.org/2000/svg" width="150" height="50">
  <path d="M15 33 C92 32,72 32,143 7" stroke="#708cdf" fill="none"/>
  …omitted…
</svg>

GET /images

This API endpoint returns the images assigned to an object id. Only images that passed moderation are returned.

For requests to this endpoint, the API supports the following parameters:

Context

This query parameter is required.

context: name of the object the images are attached to. Can be one of:
- place

Object ID

This query parameter is required.

objectId: the ID of the object the images are attached to.

Example request

curl 'https://accessibility-cloud-v2.freetls.fastly.net/images?context=place&objectId=5b1667525536dc06e63effdb&appToken=YOUR_TOKEN_HERE&locale=en' -H 'Accept: application/json' | jq

Example response

{
  "totalCount": 1,
  "images": [
    {
      "_id": "FbDShZ8uEjrmYrfNb",
      "url": "https://accessibility-cloud-uploads.eu-central-1.amazonaws.com/place/5b1667525536dc06e63effdb/eHbzCTlqWa1T2hplB56lyGn9OBpTv2jM3_L0EDB9uzt.png",
      "date": "2018-06-12T13:36:08.326Z",
      "mimeType": "image/png"
    }
  ]
}

POST /image-upload

This API endpoint allows uploading images to assign them to a place-id.

Several steps have been taken to prevent abuse:

These images need to pass moderation before they are returned.
A captcha is required
Frequent requests are throttled

For requests to this endpoint, the API supports the following parameters:

Place ID

This query parameter is required.

placeId: the ID of the object the images are attached to.

Captcha

This query parameter is required.

captcha: the solution to a captcha requested with the same IP and api token from /captcha

Potential Errors:

Error: Captcha not solved/found {"error":{"reason":"No captcha found."}}
- Solution: Request another captcha using the /captcha endpoint
Error: Mime type not supported {"error":{"reason":"The given mime type image/xxx is not supported by this endpoint."}}
- Solution: Pass a valid Content-Type: header with one of image/png, image/jpeg, image/tiff, image/tif or image/gif
Error: File type not recognized {"error":{"reason":"Unsupported file-type detected (unknown)."}}
- Solution: Upload a valid image, ensure that the data is not corrupted.
Error: Too many requests {"error":{"reason":"Too many requests"}}
- Solution: Throttle the upload frequency, the maximum number of requests are 3 every 5 seconds.

Example request

curl -X POST 'https://accessibility.cloud/image-upload?placeId=5b1667525536dc06e63effdb&captcha=hLb70W&appToken=YOUR_TOKEN_HERE' -H 'Accept: application/json' -H "Content-Type: image/png" -T example.png

Example response

{"error":null,"success":true}

Files

json-api.md

Latest commit

History

json-api.md

File metadata and controls

accessibility.cloud API

Features

Getting started

Cached vs. non-cached base URLs

Authentication

Features for all endpoints

Retrieving single documents by their _id

Licensing

Pagination

Filtering returned fields

Embedded related resources

Sorting

Error handling

Endpoints

GET /place-infos

Include places without known accessibility

Data source filtering

Location-based search by center/radius

Getting all places inside a X/Y/Z tile

Filter by metadata

Filter by category

Retrieving a PlaceInfo document by its sourceId and originalId

Embedding related documents

Example request

Example response

GET /apps

GET /categories

Example request

Example response

GET /disruptions

Data source filtering

Location-based search

Embedding related documents

Example request

Example response

GET /equipment-infos

Data source filtering

Location-based search

Embedding related documents

Example request

Example response

GET /global-stats

Series filtering

Example request

Example response

GET /languages

GET /licenses

GET /organizations

GET /source-imports

GET /sources

GET /captcha

Example request

Example response

GET /images

Context

Object ID

Example request

Example response

POST /image-upload

Place ID

Captcha

Potential Errors:

Example request

Example response

Retrieving single documents by their `_id`

Retrieving a PlaceInfo document by its `sourceId` and `originalId`