Build with Entur

Getting started

Entur's APIs give developers and partners access to Norway's public transport infrastructure — from open journey planning data to commercial ticket sales integrations. Follow the steps below to get set up.

Step 1

What do you want to build with Entur

Depending on your use case, you can use open services, partner services, or combine both.

Open services

Public transport data APIs

Available to everyone. No partnership agreement required.

Journey planner
Mobility (microtransports, bysykkel..)
Real-time vehicle positions
Stops and infrastructure data

Access requirements

Client identification (ET-Client-Name)

Learn more

Partner services

Sales, ticketing & operator APIs

For organisations with a partnership agreement with Entur.

Ticket sales and order management
Timetable and deviations
Seating and inventory
Customers and personalisation

Access requirements

Partnership agreement with Entur
Client identification (ET-Client-Name)
OAuth 2.0 authentication

Learn more

Need to become an Entur partner?

Partner services require a signed agreement with Entur. If your organisation doesn't have one yet, find out how to get started.

How to become an Entur partner →

Step 2

Client identification (ET-Client-Name)

All APIs

Every Entur API — open and partner — requires your application to identify itself using the ET-Client-Name header. This is always the first step, regardless of which service type you are using.

This helps Entur understand how its APIs are used and allows traffic to be managed responsibly. Requests without this header may be rate limited or blocked.

Use a value that uniquely identifies your company and application, in the form <company>-<application> (lowercase, no spaces).

Example

If your company is "Forsen Utvikling" and your app is "Infoplakat", your ET-Client-Name would be forsen_utvikling-infoplakat.

Code
curl --request GET \
  --url "https://api.entur.io/distance/stop-place-distances/NSR:StopPlace:337/NSR:StopPlace:1" \
  --header "ET-Client-Name: forsen_utvikling-infoplakat"

Step 3

Authentication

Partner APIs

If you are only using Open services, skip to step 4.

Partner APIs require OAuth 2.0 Client Credentials authentication in addition to client identification. See the full guide for setup steps, code examples, environments, and troubleshooting.

Authentication guide

Step 4

First API call

Try the Geocoder API, as it is open and does not require authentication. This call looks up a stop place by its national ID and returns its name and coordinates.

Code
curl "https://api.entur.io/geocoder/v1/place?ids=NSR:StopPlace:337&lang=no" \
  -H "ET-Client-Name: my_company-my_app"

Using our docs with AI tools

Every page in the developer portal has a Copy page dropdown in the top right corner. Use it to copy the page as Markdown, open it directly in Claude or ChatGPT, or share the link. Doing so on this page is a good starting point for any LLM.

For programmatic access (e.g. adding to CLAUDE.md or AGENTS.md), we expose:

/llms.txt — the best starting point for any LLM; an index of all doc pages with links to individual Markdown files
/llms-full.txt — all documentation in a single file
Any page as Markdown — append .md to its URL (e.g. /docs/authentication.md)