Transport for Grenoble, France API

Free to Use Varies (check documentation)

Overview

The Grenoble Mobilites-M API provides open public transport data for the Grenoble metropolitan area in France, including bus and tram schedules and stop information. No API key is required for basic data access, making it easy to get started. It is a good resource for exploring French regional transit open data.

Beginner Tip

No API key is required — the data is freely accessible. Start by fetching the list of lines or stops to understand the network structure before querying specific timetables.

Available Data

match scores and results
team standings
player statistics
schedule and fixtures
Use case: Integrate grenoble public transport data into web and mobile applications

Example Response

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

Field Reference

id Unique identifier for the transit line or stop
name Human-readable name of the line or stop
mode Transport mode (e.g., TRAMWAY, BUS)
color Hex color code used to display the line on maps
network Code of the operating transport network (e.g., SEM)

Implementation Example

Request
const url = "https://www.mobilites-m.fr/pages/opendata/";
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

Empty response or no data Incorrect network code in the reseaux parameter
Use "SEM" for Grenoble urban tram/bus network or check the API documentation for other valid network codes
CORS blocked in browser Making direct browser requests to the API without a proxy
Route requests through a backend server or use a CORS proxy for development and testing
Unexpected data format Some endpoints return GeoJSON rather than plain JSON
Check the endpoint documentation; geographic endpoints return GeoJSON FeatureCollections, so parse the features array

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 NO
CORS NO
Category Transportation
Difficulty Beginner
Verified: 2026-04-04

Related Tags

Similar APIs

View All →