Transport for Switzerland API

Beginner's Pick Transportation / No Auth Required Beginner HTTPS
Free to Use
62 C
Measured Score 0 50 100 Speed 3/30 Consistency 20/20 Security 20/20 Browser access 15/15 Transparency 4/15 TESTED 2026-08-10

Overview

Transport for Switzerland (transport.opendata.ch) is a free, community-maintained API for querying Swiss public transport connections, stations, and live departure boards. No authentication is needed — just send a request and get JSON data back. It covers trains, buses, and trams across the entire Swiss transport network.

Beginner Tip

Try the /v1/locations endpoint to search for stations by name and get their IDs, then use those IDs with /v1/stationboard to see live departures. No sign-up or API key required.

Measurement Record

What actually happened when we called this API from our own infrastructure. Every value below was recorded by the request, not copied from the provider's documentation.

Request
GET https://transport.opendata.ch/v1/stationboard?station=Zurich&limit=5
Result
HTTP 200 · application/json · 28,179 bytes
Response time
1018 ms (median of 3) · fastest 1003 ms
Transport
TLSv1.3 · TLS_AES_256_GCM_SHA384 · certificate issued by Let's Encrypt
Browser CORS
Allowed — Access-Control-Allow-Origin: *
Served by
Apache
Recorded
2026-08-10

Fields Returned

Top-level fields present in the response we captured, with the type and value we actually received.

Field Type Value received
station object {5 fields}
stationboard array [1 item]

Captured Response

Captured from a real request to https://transport.opendata.ch/v1/stationboard?station=Zurich&limit=5 on 2026-08-10. Long arrays and nested objects are truncated to keep the shape readable.

JSON Response · Captured
{
  "station": {
    "id": "8503000",
    "name": "Zürich HB",
    "score": null,
    "coordinate": {
      "type": "WGS84",
      "x": 47.377847,
      "y": 8.540502
    },
    "distance": null
  },
  "stationboard": [
    {
      "stop": {
        "…": "(10 more fields)"
      },
      "name": "018583",
      "category": "S",
      "subcategory": null,
      "categoryCode": null,
      "number": "5",
      "operator": "SBB",
      "to": "Rapperswil SG",
      "passList": [
        {
          "…": "(10 more fields)"
        }
      ],
      "capacity1st": null,
      "capacity2nd": null
    }
  ]
}

Field Reference

stationboard List of upcoming departures from the station.

Implementation Example

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

Request
const url = "https://transport.opendata.ch/v1/stationboard?station=Zurich&limit=5";
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.

How This API Fails

We deliberately sent this API a broken request and recorded exactly what came back on 2026-08-10. Knowing the shape of an error before you hit it makes error handling much easier to write.

HTTP 404 Requesting a path that does not exist application/json
{
  "errors": [
    {
      "message": "No route found for \"GET /v1/stationboard/apisscore-nonexistent-path\""
    }
  ]
}

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.

No station found The station name provided does not match any known station in the system.
Use partial names or check spelling — for example, use "Bern" instead of "Berne" or "Bahnhof Bern".
429 Too Many Requests Sending too many requests in a short period.
Add delays between requests and cache results locally, as this is a community-maintained free service.
Connection not found The from/to parameters may have ambiguous station names.
Use station IDs from the /v1/locations endpoint instead of plain text names for more reliable results.

Measured Score Breakdown

Live HTTP request to the API endpoint

Speed 3/30
Consistency 20/20
Security 20/20
Browser access 15/15
Transparency 4/15
Endpoint Response Time 1018ms

Fully tested on Aug 10, 2026

Technical Specifications

Auth No Auth
HTTPS REQUIRED
CORS UNKNOWN
Category Transportation
Difficulty Beginner
Endpoint last called: 2026-08-10

Related Tags

Similar APIs

View All →