Reference · built on requestCommons signalTransit, roads & mobility

Citi Bike System Data

GBFS 2.3 station status and information for Citi Bike in New York City, Jersey City, and Hoboken, plus monthly trip history files.

Request accessPricing ↗

About

Citi Bike is the bike share system for New York City and the New Jersey side of the Hudson, operated by Lyft. It publishes a GBFS 2.3 feed whose auto-discovery file lists system_information, station_information, station_status, free_bike_status, vehicle_types, system_regions, system_alerts, system_pricing_plans, system_hours, system_calendar, and gbfs_versions in English, French, and Spanish. Trip histories are published monthly as compressed CSV files, with separate JC files for Jersey City.

Through Fibric, an operator watches the stations around your hotel, office, or venue and proposes guest guidance or a shuttle change when docks or bikes run out. Each proposal records the station and its last_reported time.

This is a reference listing. It documents what Fibric would read from Citi Bike 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: num_bikes_available, num_ebikes_available, num_docks_available, disabled counts, is_installed, is_renting, is_returning, last_reported, and vehicle_types_available
  • station_information: station_id, name, short_name, lat, lon, capacity, region_id, rental_uris, and is_charging
  • vehicle_types: id 1 bicycle with human propulsion and id 2 bicycle with electric_assist and max_range_meters
  • system_regions: NYC District, JC District, Hoboken District, Bronx, and operator-side regions
  • system_alerts, and system_information with system_id lyft_nyc, operator Lyft, timezone America/New_York, start_date 2013-05-01
  • Monthly trip files: Ride ID, Rideable type, Started at, Ended at, start and end station name, ID, latitude and longitude, Member or casual ride

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

  • Tell a guest where the bikes are

    When a guest asks for a bike, the operator reads the nearest stations' num_bikes_available and num_ebikes_available and proposes a reply with the station names and counts, stamped with last_reported.

    With Guest Requests

  • Add bike access to the arrival note

    The evening before arrival, the operator proposes a line for the welcome note: the closest station, its capacity, and whether it is renting.

    With Arrival Prep

  • Watch docks empty during an event

    Around a venue, falling num_docks_available across stations signals a crowd on its way out. The operator proposes a staffing or shuttle change for your approval.

    With Event Surge

  • Rank sites by ride volume

    Monthly trip files give starts and ends by station. The operator proposes a ranking of your sites by nearby ride volume, with the month named.

    With Site Benchmark

Requirements

  • A poller that honours ttl, which is 60 seconds on every Citi Bike feed
  • The station_id values, or a lat/lon radius, for the places you care about
  • Acceptance of the NYCBS Data Use Policy, including no stand-alone redistribution of the data
Authentication
None. The GBFS files and the trip archive on s3.amazonaws.com/tripdata are public HTTPS resources with no key.

Limits

  • Trip histories are monthly and filtered: staff trips, test-station trips, and rides under 60 seconds are removed
  • free_bike_status can return no vehicles; station_status counts are where the fleet shows up
  • Stations that are not installed still appear in station_status with zero counts, so filter on is_installed and is_renting
  • The Data Use Policy forbids hosting or selling the data as a stand-alone dataset and any attempt to correlate it with customer identities

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 Citi Bike System Data ↗

Questions and answers

Which GBFS version and files does Citi Bike publish?
Version 2.3. The auto-discovery file at gbfs.citibikenyc.com/gbfs/2.3/gbfs.json points to gbfs.lyft.com and lists system_information, station_information, station_status, free_bike_status, system_hours, system_calendar, system_regions, system_pricing_plans, system_alerts, gbfs_versions, and vehicle_types in en, fr, and es.
How often can I poll?
Each file carries ttl 60, the number of seconds before the data will be updated again, and last_updated, the publisher's view of the system at that moment. Poll no faster than the ttl.
What do the trip history files contain?
Ride ID, Rideable type, Started at, Ended at, start and end station name and ID, start and end latitude and longitude, and Member or casual ride. Older files used Trip Duration, Bike ID, User Type, Gender, and Year of Birth. Months over one million trips are split into several CSVs in one archive.
Ask about Citi Bike 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 Citi Bike, operated by Lyft (gbfs.citibikenyc.com, gbfs.lyft.com, s3.amazonaws.com/tripdata). 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