André Gernandt • almost 3 years ago
nextbike *** realtime and historical data
We're happy that you want to build something with bike sharing data.
We provide you different APIs with realtime and historical data.
1. Open-Data approach
nextbike provides data in GBFS (General Bikeshare Feed Specification, https://github.com/NABSA/gbfs ). This is a global standard for realtime data.
You can fetch locations of bikes, stations and also a lot of meta data. As a bonus, other companies e.g. e-scooter providers, also implement GBFS. This means once you're consuming this API, you might be able to get data from different micro-mobility service providers very easily.
For nextbike you'll find the entry-point here: https://germany.nextbike.net/maps/gbfs/v1/nextbike_de/gbfs.json
2. nextbike Live API
The nextbike Live API gives you more detailed data than GBFS. You're able to read realtime locations of bikes, stations and all nextbike-related data. The API contains all data from more than 250 cities over Asia, Europe, Norther America and Australia.
See the dropbox link below.
There is also an Open-API specification for this and we can assist you with auto-generating client SDKs ( https://github.com/OpenAPITools/openapi-generator ) to consume this API. Please get in touch!
3. Historical data from Berlin
We brought you some historical data from Berlin where you can do data mining with, run machine learning algorithms on or just use them to get some insights on how bike sharing systems work.
This will be provided in either CSV or JSON format.
Historical data (all rentals with start and end places from Berlin August 2019):
If you need more or other data, please get in touch!
Historical data and live API documentation:
Comments are closed.