Mobility v2

Aggregation API for shared mobility services.

GBFS

Currently, we offer data from a number of shared mobility operators in several Norwegian cities.

All of our data is served in version 2.3 and version 3.0 of the General Bikeshare Feed Specification (GBFS) format which is a standardized data feed for shared mobility systems.

List the GBFS endpoint for all operators

All currently implemented operators and their respective gbfs endpoints will be listed under the root endpoint.

HTTP Request for GBFS v3.0

This is the manifest.json endpoint that was introduced in GBFS v3.0. It lists all systems available, in all available versions.

GET https://api.entur.io/mobility/v2/gbfs/v3/manifest.json

Example response

{
    "last_updated": "2024-10-01T10:32:30.786+00:00",
    "ttl": 3600,
    "version": "3.0",
    "data": {
        "datasets": [
            {
                "system_id": "voistavanger",
                "versions": [
                    {
                        "version": "2.3",
                        "url": "https://api.entur.io/mobility/v2/gbfs/v2/voistavanger/gbfs"
                    },
                    {
                        "version": "3.0",
                        "url": "https://api.entur.io/mobility/v2/gbfs/v3/voistavanger/gbfs"
                    }
                ]
            }
        ]
    }
}

HTTP Request for GBFS v2.3

This is a custom endpoint that lists GBFS v2.3 endpoints.

GET https://api.entur.io/mobility/v2/gbfs/v2

Example response

{
    "systems": [
        {
            "id": "oslobysykkel",
            "url": "https://api.entur.io/mobility/v2/gbfs/oslobysykkel/gbfs"
        },
        {
            "id": "boltoslo",
            "url": "https://api.entur.io/mobility/v2/gbfs/boltoslo/gbfs"
        }
    ]
}

GBFS information for an operator (GBFS v3.0)

Get the different GBFS endpoints for a specific operator in GBFS v3.0.

HTTP Request

GET https://api.entur.io/mobility/v2/gbfs/v3/{system}/gbfs

Where {system} is one of the last part of the system id, for instance voistavanger.

Example response

{
    "last_updated": "2023-02-10T09:30:00.000+00:00",
    "ttl": 86400,
    "version": "3.0",
    "data": {
        "feeds": [
            {
                "name": "system_information",
                "url": "https://api.entur.io/mobility/v2/gbfs/v3/voistavanger/system_information"
            },
            {
                "name": "vehicle_types",
                "url": "https://api.entur.io/mobility/v2/gbfs/v3/voistavanger/vehicle_types"
            },
            {
                "name": "gbfs",
                "url": "https://api.entur.io/mobility/v2/gbfs/v3/voistavanger/gbfs"
            },
            {
                "name": "system_alerts",
                "url": "https://api.entur.io/mobility/v2/gbfs/v3/voistavanger/system_alerts"
            },
            {
                "name": "system_pricing_plans",
                "url": "https://api.entur.io/mobility/v2/gbfs/v3/voistavanger/system_pricing_plans"
            },
            {
                "name": "system_regions",
                "url": "https://api.entur.io/mobility/v2/gbfs/v3/voistavanger/system_regions"
            },
            {
                "name": "vehicle_status",
                "url": "https://api.entur.io/mobility/v2/gbfs/v3/voistavanger/vehicle_status"
            },
            {
                "name": "geofencing_zones",
                "url": "https://api.entur.io/mobility/v2/gbfs/v3/voistavanger/geofencing_zones"
            }
        ]
    }
}

GBFS information for an operator (GBFS v2.3)

Get the different GBFS endpoints for a specific operator in GBFS v2.3.

HTTP Request

GET https://api.entur.io/mobility/v2/gbfs/v2/{system}/gbfs

Where {system} is one of the last part of the system id, for instance oslobysykkel.

Example response

{
    "last_updated": 1610375175,
    "ttl": 15,
    "version": "2.3",
    "data": {
        "nb": {
            "feeds": [
                {
                    "name": "system_information",
                    "url": "https://api.entur.io/mobility/v2/gbfs/oslobysykkel/system_information"
                },
                {
                    "name": "station_information",
                    "url": "https://api.entur.io/mobility/v2/gbfs/oslobysykkel/station_information"
                },
                {
                    "name": "station_status",
                    "url": "https://api.entur.io/mobility/v2/gbfs/oslobysykkel/station_status"
                },
                {
                    "name": "system_pricing_plans",
                    "url": "https://api.entur.io/mobility/v2/gbfs/oslobysykkel/system_pricing_plans"
                },
                {
                    "name": "vehicle_types",
                    "url": "https://api.entur.io/mobility/v2/gbfs/oslobysykkel/vehicle_types"
                }
            ]
        }
    }
}

GraphQL

We also offer a client-centric GraphQL API as a way to aggregate data across all providers. It currently offers two entrypoints to finding entities near a location: vehicles and stations.

The GraphQL endpoint's URL is https://api.entur.io/mobility/v2/graphql

An interactive IDE for exploring this API is available at https://api.entur.io/graphql-explorer/mobility

Authentication

This API is open under NLOD licence, however, it is required that all consumers identify themselves by using the header ET-Client-Name. Entur will deploy strict rate-limiting policies on API-consumers who do not identify with a header and reserves the right to block unidentified consumers. The structure of ET-Client-Name should be: "company-application"

Header examples:

• "brakar-journeyplanner"
• "fosen_utvikling-departureboard"
• "nor_way_bussekspress-nwy-app"