Realtime APIs
Transport API (GTFS)

GTFS Static API Endpoint


What does GTFS Static do?

The GTFS Static API provides access to standardized public transportation schedules and geographic information, following the General Transit Feed Specification (GTFS). To learn more about GTFS and its specifications, you can visit the GTFS documentation (opens in a new tab) provided by Google.

Important note: We are building iteratively

This is the first time that Malaysia has had an official and freely-usable GTFS API. It is the result of months of hard work and collaboration between the developer team and various public transport operators. It is by no means complete; there are plenty of services that will only be integrated over the coming months and years. However, with several primary services already included, we felt that it was time to push it live - so that the private sector and public transport community could begin building from it, and most crucially, giving us feedback on how to improve it.

If you have any feedback on the GTFS API, please write to us at - we welcome any and all constructive feedback!

Source of GTFS Static Data

The GTFS Static API incorporates data from various transport agencies in Malaysia. Currently, the following agencies contribute their transit data:

Frequency of Data Update

  • GTFS for myBAS Johor Bahru: As required.
  • GTFS for Prasarana: As required.
  • GTFS for KTMB: Daily at 00:01:00.

Request Query & Response Format

The GTFS Static API provides access to public transportation data represented as a GTFS Feed, which consists of a collection of text files packaged in a ZIP file. You can access these data files through the following endpoints:

myBAS Johor Bahru

# ZIP file is returned


# ZIP file is returned


# ZIP file is returned
  • The possible <category> values are rapid-bus-penang, rapid-bus-kuantan, rapid-bus-mrtfeeder, rapid-rail-kl and rapid-bus-kl.
  • Note: A small number of trips (~2%, fully specified in this CSV (opens in a new tab)) for the rapid-bus-kl endpoint have been removed from the stop_times.txt file due to operational issues which affect data accuracy. We are actively working to resolve and restore them to our GTFS feed.

Understanding the data

Upon extracting the ZIP files obtained from the API endpoints, you will find various text files. Here are the essential text files provided by all agencies:

GTFS TypeDescription
agency.txtInformation about transit agencies
stops.txtInformation about transit stops
routes.txtDetails about transit routes
trips.txtSpecific trips with associated route information
stop_times.txtTimetables and stop details for trips
calendar.txtService availability for specific dates

Other optional files, such as frequencies.txt and shapes.txt, are provided if available. For more details, refer to the GTFS Schedule Reference (opens in a new tab).