Skip to main content

Dependency on GBFS

The Dott's MaaS API was designed to be interoperable with Dott's GBFS API. The intention was to enable partners on a Level 1 integration (which is usually enabled by GBFS) to be able to transition into a Level 2 integration faster.

Also, this meant that there would be an opportunity to leverage existing functionality in GBFS instead of implementing it in the MaaS API.

Currently, consuming Dott's GBFS API is the only way to get the following information:

  • Geofencing zones
  • Parking spots

Geofencing zones​

This information is crucial to enable consumers to understand Dott's service areas and zones' behavior.

This information is accessible via the geofencing_zones.json endpoint.

Parking spots​

This information is crucial to enable consumers to find parking spots in the regions where they are available.

This information is accessible via a combination of endpoints:

  • station_information.json.
  • station_status.json.

With the information from station_information.json a consumer can get all the parking spots in the form of virtual stations (which are stations with the is_virtual_station property set to true ). This endpoint already contains the coordinates for the parking spots.

The information returned in station_status.json describes the capacity of the parking spots. This information is crucial in regions where the capacity limit is enforced by the municipality.