Mock sample for your project: AviationData.Systems Airports API V1
Integrate with "AviationData.Systems Airports API V1" from aviationdata.systems in no time with Mockoon's ready to use mock sample
AviationData.Systems Airports API V1
aviationdata.systems
Version: v1
Start working with "AviationData.Systems Airports API V1" right away by using this ready-to-use mock sample. API mocking can greatly speed up your application development by removing all the tedious tasks or issues: API key provisioning, account creation, unplanned downtime, etc.
It also helps reduce your dependency on third-party APIs and improves your integration tests' quality and reliability by accounting for random failures, slow response time, etc.
Description
Other APIs in the same category
airportsapi
airport-web.appspot.com
Get name and website-URL for airports by ICAO code. Covered airports are mostly in Germany.
Vehicle Image
mercedes-benz.com
The vehicle images API offers access to original Mercedes-Benz vehicle images. It provides access to exterior and interior images with parameters e.g. to modify the perspective and to display vehicles at day/nighttime. In addition you can request component images of a vehicle's engine, paint, rim, trim, upholstery and equipments.
Transport for London Unified API
tfl.gov.uk
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
paccurate.io
paccurate.io
Reisezentren-API
deutschebahn.com
This REST-API enables you to query information about travel centers in Germany.
FaSta - Station Facilities Status
deutschebahn.com
A RESTful webservice to retrieve data about the operational state of public elevators and escalators in german railway stations.
LH Partner API
lufthansa.com
Faretrotter Travel API
faretrotter.com
Multimodal travel API to return modes of transportation between cities and points of interest.
PTV Timetable API - Version 3
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.
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.