Reference · built on requestCommons signalTransit, roads & mobility

Divvy System Data

GBFS 2.3 station status, free-floating bikes and scooters, and monthly trip history for Divvy, the bike share owned by the City of Chicago.

Request accessPricing ↗

About

Divvy is the bike and scooter share system of the City of Chicago, run by Lyft with the Chicago Department of Transportation and the City of Evanston. The City owns the data. The GBFS 2.3 auto-discovery file at gbfs.divvybikes.com/gbfs/2.3/gbfs.json points to gbfs.lyft.com and lists station_status, station_information, free_bike_status, vehicle_types, system_regions, system_alerts, and the pricing, hours, and calendar files. Trip data is released monthly as zip files on divvy-tripdata.s3.amazonaws.com under the Divvy Data License Agreement.

Through Fibric, an operator reads the stations and free vehicles near your properties and proposes what to tell a guest or tenant, or when to add a shuttle run. The record names the station and last_reported.

This is a reference listing. It documents what Fibric would read from Divvy System Data and what it could propose, based on the publisher's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • station_status per station: num_bikes_available, num_ebikes_available, num_docks_available, disabled counts, is_installed, is_renting, is_returning, last_reported, vehicle_types_available
  • free_bike_status: undocked vehicles with bike_id, lat, lon, is_reserved, is_disabled, vehicle_type_id, current_range_meters, and rental_uris
  • vehicle_types: 1 bicycle human, 2 bicycle electric_assist, 3 scooter electric, each with max_range_meters where set
  • station_information: station_id, name, lat, lon, capacity, region_id, and rental_uris
  • system_regions (Evanston) and system_information with system_id lyft_chi, timezone America/Chicago, and a phone number
  • Monthly trip files: trip start and end day and time, start and end station, and rider type (Member, Single Ride, Day Pass)

Proposed actions

Read-only. This feed informs operators; it changes nothing.

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Answer a tenant's bike question

    A resident or guest asks about bikes. The operator reads the nearest station_status rows and free_bike_status vehicles within walking distance and proposes a reply with counts and range.

    With Guest Requests

  • Plan an event exit

    As a game or concert ends, num_docks_available near the venue drops. The operator proposes an extra shuttle run or a message to attendees for your approval.

    With Event Surge

  • Prepare the welcome note

    Before check-in, the operator proposes a line naming the closest Divvy station, its capacity, and whether it is renting and returning.

    With Arrival Prep

  • Rank sites by ride activity

    Monthly trip files count starts and ends by station. The operator proposes a ranking of your Chicago sites with the month named.

    With Site Benchmark

Requirements

  • Polling at or slower than the ttl of 60 seconds each file declares
  • Coordinates or station_id values for the places you watch; free vehicles need a radius, not a station
  • Acceptance of the Divvy Data License Agreement, which Lyft Bikes and Scooters, LLC grants on behalf of the City of Chicago
Authentication
None. GBFS files and the trip archive are public HTTPS resources; no key or account is issued.

Limits

  • Trip files exclude staff service trips and rides under 60 seconds, and are anonymised to station and rider type
  • The archive mixes quarterly zips from earlier years with monthly zips, so a loader must handle both naming patterns
  • The licence bars hosting, streaming, or selling the data as a stand-alone dataset and any attempt to correlate it with customers or Members
  • Bikeshare may modify or discontinue the data at any time without notice, per the licence

Access and pricing

Reference listing. Public feed access is separate from Fibric integration. If you request this feed, your quote covers the build, usage, and support.

Request Divvy System Data ↗

Questions and answers

Does Divvy publish undocked vehicles?
Yes. free_bike_status lists vehicles not docked at a station with bike_id, lat, lon, is_reserved, is_disabled, current_range_meters, and vehicle_type_id. vehicle_types maps id 1 to a human-powered bicycle, 2 to an electric-assist bicycle, and 3 to an electric scooter.
Who owns the data and on what terms?
The City of Chicago owns all right, title, and interest in the Data. Lyft Bikes and Scooters, LLC grants a non-exclusive, royalty-free, perpetual licence to use it for any lawful purpose, with no stand-alone redistribution, no identification of riders, and no implied endorsement.
What does a trip record contain?
Trip start day and time, trip end day and time, start station, end station, and rider type (Member, Single Ride, Day Pass). Staff trips and rides under 60 seconds are removed. Files are released monthly.
Ask about Divvy System Data

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This Commons signal listing is developed, published, and supported by Fibric. It reads public data published by Divvy, City of Chicago data operated by Lyft (gbfs.divvybikes.com, gbfs.lyft.com, divvy-tripdata.s3.amazonaws.com). Upstream agencies and projects are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy