Discovery endpoints for landing page, conformance, and API metadata.
Get API landing page
Gives a (technical & human readable) output describing how this API must be used. If the parameter f=html is supplied, a human readable page must be responded.
query Parameters
fThe optional f parameter indicates the output format that the server shall provide as part of the response document. The default format is JSON.
Headers
Accept-Languageshort string, display names (length 0-75)
ET-Client-NameEntur Client Header.
It is required that all consumers identify themselves by using this header.
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> for companies, and <personal name>-<application> for individuals.
X-Correlation-IdCorrelation id
Get API landing page › Responses
The reponse containing a landing page
Get OpenAPI specification document
Returns this OpenAPI document in JSON or YAML format.
query Parameters
fOutput format for the OpenAPI document.
Headers
ET-Client-NameEntur Client Header.
It is required that all consumers identify themselves by using this header.
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> for companies, and <personal name>-<application> for individuals.
X-Correlation-IdCorrelation id
Get OpenAPI specification document › Responses
General Success response.
List available processes
The list of processes contains a summary of each process the OGC API - Processes offers, including the link to a more detailed description of the process.
For more information, see Section 7.9.
Headers
Accept-Languageshort string, display names (length 0-75)
ET-Client-NameEntur Client Header.
It is required that all consumers identify themselves by using this header.
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> for companies, and <personal name>-<application> for individuals.
X-Correlation-IdCorrelation id
List available processes › Responses
Information about the available processes
List available collections
returns a collection of available collection (like offers, packages, legs, support-requests and payments)
Headers
ET-Client-NameEntur Client Header.
It is required that all consumers identify themselves by using this header.
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> for companies, and <personal name>-<application> for individuals.
X-Correlation-IdCorrelation id
List available collections › Responses
A list of available collections
timeStampnumberMatchednumberReturnedGet API conformance declaration
A list of all conformance classes specified in a standard that the server conforms to.
query Parameters
fThe optional f parameter indicates the output format that the server shall provide as part of the response document. The default format is JSON.
Headers
Accept-Languageshort string, display names (length 0-75)
ET-Client-NameEntur Client Header.
It is required that all consumers identify themselves by using this header.
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> for companies, and <personal name>-<application> for individuals.
X-Correlation-IdCorrelation id
Get API conformance declaration › Responses
The URIs of all conformance classes supported by the server.
To support "generic" clients that want to access multiple OGC API Features implementations - and not "just" a specific API / server, the server declares the conformance classes it implements and conforms to.
Get process description
The process description contains information about inputs and outputs and a link to the execution-endpoint for the process. The Core does not mandate the use of a specific process description to specify the interface of a process. That said, the Core requirements class makes the following recommendation: Implementations SHOULD consider supporting the OGC process description. For more information, see Section 7.10.
path Parameters
processIDHeaders
Accept-Languageshort string, display names (length 0-75)
ET-Client-NameEntur Client Header.
It is required that all consumers identify themselves by using this header.
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> for companies, and <personal name>-<application> for individuals.
X-Correlation-IdCorrelation id
Get process description › Responses
A process description.
Get collection metadata
a (machine or human) readable description of this collection
path Parameters
collectionIdlocal identifier of a collection
Headers
Accept-Languageshort string, display names (length 0-75)
ET-Client-NameEntur Client Header.
It is required that all consumers identify themselves by using this header.
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> for companies, and <personal name>-<application> for individuals.
X-Correlation-IdCorrelation id
Get collection metadata › Responses
description of data delivered by this collection