Mock sample for your project: Vehicle Image API

The Remote Diagnostic Support API will provide the possibility for 3rd party applications (e.g. ADAC, ATU, etc.) to access vehicle diagnostics data remotely on behalf of the Daimler customer. To use the endpoints you need a valid vin/fin (vehicleId).

The Dealer API provides Dealer search functions.

The Car Configurator API offers access to the Mercedes-Benz car configuration functions. It provides required reference data such as the masterdata of all Mercedes-Benz vehicles as well as functions to retrieve initial and changed configurations. In addition to that is is possible to save a newly created configuration so that it can be easily restored or shared with others.

Our unified API brings together data across all modes of transport into a single RESTful API. This API provides access to the most highly requested realtime and status infomation across all the modes of transport, in a single and consistent way. Access to the developer documentation is available at https://api.tfl.gov.uk

The Dealer API provides Dealer search functions.

A RESTful webservice to retrieve data about the operational state of public elevators and escalators in german railway stations.

This REST-API enables you to query for private transport sharing offers provided by companies and cities in Germany, Netherland and Austria.
You can search for informations about the rental stations (points or areas) where you can find the rentals by utilizing the /areas/ ressource.
With the help of the proximity search in the /bookingproposals/ URI you can request the availabilities of the rentalobjects for spontaneous or planed usage in the future.
Feel free to browse through data by setting the parameter 'providernetwork' to the value:
1: Search for car sharing offers provided by the Flinkster platform (http://www.flinkster.de)
2: Finding bike rental offers from Call a Bike (http://www.callabike.de)
You can find more details in the documentation section (Unfortunately only available in german language).
Have lots of fun and we are lucky to take notice of your products or getting your feedback.

The departureboard.io is a high performance API written in Golang. Its goal is to provide to main functions: (1): A JSON API interface to the legacy National Rail SOAP API: Giving developers the ability to pull live information on departures, arrivals, and services from National Rail, without having to use the legacy SOAP API provided by National Rail. Information is still pulled directly from National Rail in the background, providing the same level of real-time data without the additional complexity of having to interact with SOAP. (2): A JSON API interface for additional National Rail information: Giving developers the ability to pull a range of information about the Rail Network, via a JSON API interface. This is not an offering that National Rail currently provide, and is custom developed. Data is sourced from periodically updated XML documents, parsed, and provided for consumption via the departureboard.io API. This API is completely free to use for non-commercial purposes. You can explore the various sections of the documentation using the links below. For more information please see https://api.departureboard.io

Rail line and station information, including locations, fares, times, and parking.

Returns all airports

The PTV Timetable API provides direct access to Public Transport Victoria’s public transport timetable data.
The API returns scheduled timetable, route and stop data for all metropolitan and regional train, tram and bus services in Victoria, including Night Network(Night Train and Night Tram data are included in metropolitan train and tram services data, respectively, whereas Night Bus is a separate route type).
The API also returns real-time data for metropolitan train, tram and bus services (where this data is made available to PTV), as well as disruption information, stop facility information, and access to myki ticket outlet data.
This Swagger is for Version 3 of the PTV Timetable API. By using this documentation you agree to comply with the licence and terms of service.
Train timetable data is updated daily, while the remaining data is updated weekly, taking into account any planned timetable changes (for example, due to holidays or planned disruptions). The PTV timetable API is the same API used by PTV for its apps. To access the most up to date data PTV has (including real-time data) you must use the API dynamically.
You can access the PTV Timetable API through a HTTP or HTTPS interface, as follows:
base URL / version number / API name / query string
The base URL is either:
http://timetableapi.ptv.vic.gov.au
or
https://timetableapi.ptv.vic.gov.au
The Swagger JSON file is available at http://timetableapi.ptv.vic.gov.au/swagger/docs/v3
Frequently asked questions are available on the PTV website at http://ptv.vic.gov.au/apifaq
Links to the following information are also provided on the PTV website at http://ptv.vic.gov.au/ptv-timetable-api/
How to register for an API key and calculate a signature
PTV Timetable API V2 to V3 Migration Guide
Documentation for Version 2 of the PTV Timetable API
PTV Timetable API Data Quality Statement
All information about how to use the API is in this documentation. PTV cannot provide technical support for the API.
Credits: This page has been based on Steve Bennett's http://opentransportdata.org/, used with permission.

An API providing master data for German railway stations by DB Station&Service AG.

Real-time bus prediction methods.

This REST-API enables you to query information about travel centers in Germany.

Real-time rail prediction methods.