GBFS Bike Share & Micromobility Systems Scraper

Extract comprehensive data on 700+ global bike share and micromobility systems from the MobilityData GBFS (General Bikeshare Feed Specification) catalog. This Actor provides the most authoritative, up-to-date list of all GBFS-compliant bike sharing and micromobility systems worldwide, including Citi Bike (US), Velib (France), Bicimad (Spain), Dott, Lime, Lyft Bikes, and hundreds of regional operators.

Key Features

• Complete Global Coverage: All 700+ GBFS-registered systems across 60+ countries
• System Registry Data: Extract system names, locations, URLs, and GBFS specifications
• Live Station Coordinates & Capacities (Optional): Fetch real-time station information including GPS coordinates, station names, docking capacities, and addresses for any system
• Flexible Filtering: Filter by country code (ISO 2-letter), system name (partial match), or fetch all systems
• Scalable Architecture: Batch processing with configurable limits to control compute costs
• Zero Authentication Required: Scrape all public GBFS feeds without API keys or credentials
• Error-Resilient: Gracefully skips systems with temporarily unavailable feeds without aborting the run

Data Extracted

System Records (default mode, includeStations=false)

Field	Type	Description
countryCode	String	ISO 2-letter country code (e.g., "US", "FR", "DE")
systemName	String	Official name of the bike share system
location	String	City or region where the system operates
systemId	String	Unique identifier in the GBFS catalog
systemUrl	String	Official system operator website
autoDiscoveryUrl	String	GBFS auto-discovery manifest URL
supportedVersions	String	GBFS specification versions supported
authenticationType	String	Type of API authentication required (none, key, oauth, etc.)
authenticationInfoUrl	String	URL with authentication documentation
authenticationParameterName	String	Parameter name for API key (if applicable)

Station Records (with includeStations=true)

All system fields above (prefixed system_) plus:

Field	Type	Description
stationId	String	Unique station identifier
stationName	String	Human-readable station name
lat	Number	Latitude coordinate
lon	Number	Longitude coordinate
capacity	Integer	Total docking capacity
address	String	Street address (if available)
region_id	String	Regional zone identifier (if applicable)

Use Cases

• Mobility Data Analysis: Map global bike share penetration, find gaps in coverage
• Integration Testing: Verify your app works with every major bike share API
• Fleet Planning: Analyze system sizes, capacities, and geographic distribution
• Real Estate / Urban Planning: Identify neighborhoods with bike share infrastructure
• Travel Guides: Build directory of bike share options in any city
• Competitive Analysis: Monitor new system launches and operator changes
• Sensor/IoT Data: Import coordinates for map visualization or routing

How to Use This Actor

Basic Usage (All Systems)

Leave all inputs blank to extract all 700+ systems:

1. Click Start with default inputs
2. Wait 30-60 seconds
3. Download results as JSON/CSV from the dataset

Result: ~700 records, one per system, covering all countries.

Filter by Country

To extract only US bike share systems:

1. Set Country Code to US
2. Leave other inputs blank
3. Click Start

Result: ~150 US systems including Citi Bike, Lime, Dott, Lyft Bikes, and regional operators.

Search by System Name

To find systems matching a name pattern:

1. Set System Name Contains to Velo (or Citi, Velib, etc.)
2. Set Country Code (optional) to narrow further, e.g., FR for French Vélo systems
3. Click Start

Result: All systems with "Velo" in the name.

Fetch Live Station Data

To retrieve current station coordinates, names, and capacities for any system:

1. Set Include Live Station Data to ON
2. Set Max Systems to Process to 10 (or higher, up to 1000)
3. Optionally set Country Code or System Name Contains to limit which systems are queried
4. Click Start

Result: One record per station (instead of one per system). For example, Citi Bike has ~3,000 stations, so setting maxSystems=1 and systemNameContains=Citi yields 3,000 records.

Note: Fetching stations increases compute time and costs because we fetch real-time data from each system's API. Budget ~2-5 compute units per system depending on size.

Example Inputs

All Systems, No Stations

{
  "countryCode": "",
  "systemNameContains": "",
  "includeStations": false,
  "maxSystems": 100,
  "maxResults": 5000
}

US Systems with Station Data (First 10 Systems)

{
  "countryCode": "US",
  "systemNameContains": "",
  "includeStations": true,
  "maxSystems": 10,
  "maxResults": 50000
}

European City Bikes (System Name Filter)

{
  "countryCode": "",
  "systemNameContains": "Velo",
  "includeStations": false,
  "maxSystems": 100,
  "maxResults": 5000
}

Output Example

System Record (Default Mode)

{
  "countryCode": "US",
  "systemName": "Citi Bike",
  "location": "New York City, NY",
  "systemId": "citibike-nyc",
  "systemUrl": "https://citibikenyc.com",
  "autoDiscoveryUrl": "https://gbfs.citibikenyc.com/gbfs/gbfs.json",
  "supportedVersions": "2.3, 3.0",
  "authenticationType": "key",
  "authenticationInfoUrl": "https://www.citibikenyc.com/system-data",
  "authenticationParameterName": "key"
}

Station Record (With Stations Enabled)

{
  "system_countryCode": "US",
  "system_systemName": "Citi Bike",
  "system_location": "New York City, NY",
  "system_systemId": "citibike-nyc",
  "system_systemUrl": "https://citibikenyc.com",
  "system_autoDiscoveryUrl": "https://gbfs.citibikenyc.com/gbfs/gbfs.json",
  "system_supportedVersions": "2.3, 3.0",
  "system_authenticationType": "key",
  "system_authenticationInfoUrl": "https://www.citibikenyc.com/system-data",
  "system_authenticationParameterName": "key",
  "stationId": "72.0",
  "stationName": "W 52 St & 11 Ave",
  "lat": 40.76727216,
  "lon": -73.99392888,
  "capacity": 55,
  "address": "West 52nd Street & 11th Avenue",
  "region_id": ""
}

Pricing

This Actor uses a pay-per-result model:

• System Records (~700 systems): ~$0.001 per system = ~$0.70 total
• Station Records (with live fetching): ~$0.001 per station + ~$0.01 compute per system
  • Example: 10 systems with ~30,000 total stations = ~$30 (30,000 × $0.001) + ~$0.10 compute

Recommendation: Start with includeStations=false to get the registry for ~$0.70, then decide if you need live station data.

Input Parameters

Parameter	Type	Default	Description
countryCode	String	""	ISO 2-letter country code. Leave blank for all countries.
systemNameContains	String	""	Case-insensitive substring match on system name. Leave blank for all systems.
includeStations	Boolean	false	Fetch live station_information.json for each system.
maxSystems	Integer	100	Maximum systems to process when includeStations=true. Ignored when false. Range: 1–1000.
maxResults	Integer	5000	Hard cap on total output records (systems or stations). Range: 1–50,000.

Supported Countries

The Actor works with systems in all countries, including:

North America: US, Canada, Mexico
Europe: UK, France, Germany, Spain, Italy, Netherlands, Belgium, Poland, Sweden, Norway, Denmark, and 20+ others
Asia: Japan, South Korea, Taiwan, Singapore, India, Thailand
South America: Brazil, Chile, Colombia, Argentina
Oceania: Australia, New Zealand

See the full list in the GBFS registry: https://github.com/MobilityData/gbfs

Frequently Asked Questions

Q: Why am I getting fewer results than expected?

A: Check your filters:

• If countryCode is set, only systems in that country are returned
• If systemNameContains is set, only matching systems are returned
• If maxResults is set to a low number, some records may be excluded

Q: Can I get real-time bike/dock availability?

A: This Actor returns system registry and static station metadata (names, coordinates, capacity). For real-time availability (number of bikes/docks at each station RIGHT NOW), you would fetch the station_status.json feed from each system separately. Some systems provide this via their public API; others require authentication.

Q: Why do some systems fail to fetch station data?

A: Station feeds may be temporarily unavailable (network issues, API rate limiting) or the system may not provide station_information.json. The Actor logs these silently and continues with other systems. Check the run log for details.

Q: Can I export the results to CSV?

A: Yes! Click Dataset → Download → choose CSV format.

Q: How often is the GBFS registry updated?

A: The MobilityData catalog is updated continuously as new systems launch or shut down. Re-run this Actor weekly to stay current.

Q: Can I integrate this with Google Maps or my app?

A: Yes. Export the dataset as JSON, then import station coordinates into your map library (Leaflet, Google Maps API, Mapbox, etc.).

Q: Is there any rate limiting when fetching stations?

A: The Actor limits concurrent fetches to 10 systems at a time to avoid overwhelming operators' APIs. Most feeds return data within 1-2 seconds.

Q: What if a system uses non-standard GBFS versions?

A: The supportedVersions field tells you which GBFS spec versions each system implements. All systems listed use GBFS 2.0 or later, which is standardized and widely compatible.

Legal & Disclaimer

• This Actor scrapes publicly available, non-personal data from the MobilityData GBFS registry and open APIs
• The MobilityData GBFS registry is published under the Creative Commons Attribution 4.0 International License
• Individual system data is governed by each operator's terms of service (most allow research/educational use)
• Do not: Use station data for real-time commercial services without contacting system operators for proper data licensing agreements
• Do: Respect robots.txt and rate limits on individual systems
• For production integrations, contact each system operator directly for official API access and commercial licensing

Support

Questions or issues? Open an issue on the Actor's support page or contact the maintainer. For GBFS spec questions, see the official documentation: https://github.com/MobilityData/gbfs

Related Actors

• Trip Scraper - Extract historical trip data from public GBFS archives
• Station Status Monitor - Track real-time bike/dock counts at specific stations
• City Bike Comparison Tool - Compare pricing and availability across multiple systems

---

Last Updated: May 2026
Data Source: MobilityData GBFS Registry (https://github.com/MobilityData/gbfs)
Maintained By: seatsignal