Overview

The Velib Metropolis API provides real-time open data for Paris's bike-sharing service, including station locations, bike availability, and dock counts. It follows the GBFS (General Bikeshare Feed Specification) standard, making it easy to integrate if you've worked with other bike-share APIs. No authentication is required, so you can start fetching live station data immediately.

Beginner Tip

Use the GBFS standard endpoint to get station status and information; the feed is updated every 10 seconds so it is great for real-time apps. Explore station_information.json and station_status.json feeds first to understand the data structure.

Available Data

The kind of data this API exposes, based on its documentation. We could not call the endpoint to confirm the exact field names.

Use case: Integrate velib open data api data into web and mobile applications
Velib metropolis, Paris, France data via REST API

Example Response

Illustrative shape only — we were not able to call this endpoint (it requires credentials or exposes no public sample URL), so the fields below show the kind of data this API returns rather than a recorded response.

JSON Response · Illustrative
{
  "route": "Line 1",
  "origin": "Station A",
  "destination": "Station B",
  "departure": "08:30",
  "arrival": "09:15",
  "status": "On Time",
  "delays_min": 0
}

Field Reference

station_id Unique identifier for the bike station
name Human-readable name of the bike station
lat Latitude coordinate of the station
lon Longitude coordinate of the station
capacity Total number of docking points at the station

Implementation Example

Calls a real endpoint of this API. Replace any placeholder credentials with your own key.

Request
const url = "https://velib-metropole-opendata.smoove.pro/opendata/Velib_Metropole/station_information.json";
const response = await fetch(url);
if (!response.ok) throw new Error(`Request failed: ${response.status}`);
const data = await response.json();
console.log(data);

What Can You Build?

Note: These code examples are AI-generated and unverified. Always refer to the official API documentation for accurate usage.

Common Errors & Troubleshooting

Generated guidance based on this API's documentation, not observed by us. Treat it as a starting point and check against the provider's own error reference.

CORS errors in browser Some GBFS endpoints may not allow cross-origin requests from browsers
Fetch the data from your backend server and serve it to your frontend instead
Stale data Caching the GBFS feed responses too aggressively
Respect the ttl field in each feed response and refresh accordingly
Missing station data Requesting a station ID that does not exist or is temporarily offline
Cross-reference station_information.json and handle missing entries gracefully

Metadata Score Breakdown

Estimated from metadata — endpoint not independently tested

This score is estimated from observable metadata — HTTPS support, authentication model, declared CORS, and documentation reachability — because the API requires authentication or exposes no publicly testable endpoint. The five-signal breakdown is only shown for live-tested APIs.

Metadata estimate · endpoint not independently tested

Technical Specifications

Auth No Auth
HTTPS REQUIRED
CORS NO
Category Transportation
Difficulty Beginner
Listing details not endpoint-verified

Similar APIs

View All →