Getting started

Step 1

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

Step 2

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

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.

Step 4

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/v3/place?ids=NSR:StopPlace:337&lang=no" \
  -H "ET-Client-Name: my_company-my_app"

Using our docs with AI tools

For giving LLMs programmatic access to the documentation (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)

Next steps

Now that you are set up, explore the resources below.