SL Transport API returns HTTP 429 across multiple endpoints
Since 28 September 2026, the SL Transport API has been returning HTTP 429 for multiple endpoints.
Examples:
https://transport.integration.sl.se/v1/sites?expand=true
https://transport.integration.sl.se/v1/sites/9192/departures
Both requests return:
HTTP 429
{"error":"Quota has been exceeded"}
The same result occurs when requesting the URLs directly outside our application, with and without an additional cache-busting query parameter.
The API does not use an API key, so this does not appear to be an application-specific quota.
The separate Journey Planner service at journeyplanner.integration.sl.se continues to respond successfully.
Could you confirm whether a shared quota or gateway limit for transport.integration.sl.se has been exhausted? The status page currently labels the affected component "SL Transport Departures," but the /v1/sites endpoint is affected as well.
Examples:
https://transport.integration.sl.se/v1/sites?expand=true
https://transport.integration.sl.se/v1/sites/9192/departures
Both requests return:
HTTP 429
{"error":"Quota has been exceeded"}
The same result occurs when requesting the URLs directly outside our application, with and without an additional cache-busting query parameter.
The API does not use an API key, so this does not appear to be an application-specific quota.
The separate Journey Planner service at journeyplanner.integration.sl.se continues to respond successfully.
Could you confirm whether a shared quota or gateway limit for transport.integration.sl.se has been exhausted? The status page currently labels the affected component "SL Transport Departures," but the /v1/sites endpoint is affected as well.
Följ inlägget
1
följare
We have investigated this with SL and received confirmation that the issue is caused by a significant increase in incoming traffic. To prevent the underlying servers from becoming overloaded, SL limits traffic in these situations.
This means that some requests may be rejected even if the individual client has not made an unusually large number of requests.
Best regards,
Bert