PASAR API
Standard GBFS feeds updated every ~10 seconds; only a descriptive Client-Identifier header is required (same platform powers Bergen/Trondheim).
View docs ↗ More Travel & mobility APIs All Norway APIscurl --fail-with-body --location --max-time 30 'https://gbfs.urbansharing.com/oslobysykkel.no/gbfs.json'
I'm building an app using a public Norway API (no private credentials needed). API: Oslo Bysykkel ~ live city-bike availability (GBFS) Provider: Oslo Bysykkel (Urban Sharing) Endpoint: GET https://gbfs.urbansharing.com/oslobysykkel.no/gbfs.json Response format: JSON Source: Oslo Bysykkel (Urban Sharing) (https://oslobysykkel.no/en/open-data/realtime) Source type: Official public feed Endpoint type: Direct public JSON endpoint Integration difficulty: Copy-paste ready Last checked: 2026-07-05 Production caveat: Still handle downtime, changing fields, empty responses, and rate limits before shipping user-facing alerts. Help me fetch and display this data. Follow the documented format and handle errors, empty responses, stale coverage, caching and rate limits.