Auckland Transport Pricing: GTFS & AT Park API Costs (2026)

Pricing overview

Auckland Transport (AT) provides access to its public transport data and services through a tiered pricing model, primarily distinguishing between non-commercial and commercial use cases. For developers and organizations building applications that do not generate revenue or are for personal and educational purposes, access to core data feeds is generally provided without charge. This approach supports innovation within the Auckland region's transport ecosystem and encourages the development of tools that benefit the public experience of using Auckland Transport services.

Commercial use, however, operates under a different framework. Organizations intending to monetize their applications or services that integrate Auckland Transport data are required to engage directly with Auckland Transport. This engagement facilitates the negotiation of specific licensing agreements and potential fees, which are tailored to the scope, scale, and nature of the commercial application. The rationale behind this distinction is to manage data distribution responsibly, ensure fair use, and potentially recover costs associated with data provision and infrastructure maintenance, while still fostering a vibrant developer community around public transport information. The official Auckland Transport developer portal serves as the primary resource for detailed information regarding API access and licensing.

The pricing structure is not publicly itemized for commercial usage, indicating a bespoke agreement process. This is common for government entities providing public data where commercial exploitation needs careful consideration regarding resource allocation and public benefit. For instance, similar models exist where public sector data is free for general use but commercially licensed for specific value-added services, as sometimes observed in geospatial data services from providers like Esri ArcGIS developers, which often have various tiers for commercial use.

Plans and tiers

Auckland Transport's API access model is categorized into two primary tiers:

1. Non-Commercial Use: This tier offers free access to essential data feeds and APIs. It is intended for individuals, academic researchers, non-profit organizations, and developers creating applications that are freely available to the public and do not generate direct revenue. This supports community-driven innovation and enhances public access to transport information.
2. Commercial Use: This tier is for businesses, startups, and any entity that plans to monetize an application or service that utilizes Auckland Transport's data. Access under this tier requires a direct agreement with Auckland Transport, where terms, conditions, and any applicable fees are negotiated based on the specific commercial application and its expected data consumption.

The core products available across these tiers include:

• Real-time GTFS (General Transit Feed Specification) feed: Provides up-to-the-minute information on bus, train, and ferry locations, delays, and schedule changes. This is crucial for real-time journey planning applications.
• Scheduled GTFS feed: Contains static schedule data, route information, and stop locations, essential for developing journey planners and transit maps.
• AT Park API: Offers data related to parking availability, locations, and pricing within Auckland Transport's managed parking facilities.

The table below summarizes the general distinctions between these tiers:

To initiate commercial access, developers must contact Auckland Transport through their official channels, typically outlined on the developer support page. This process ensures that commercial use aligns with AT's data governance policies and objectives.

Free tier and limits

Auckland Transport offers a robust free tier designed to support innovation and public access to transport information. This tier specifically grants access to the GTFS feeds (both real-time and scheduled) and the AT Park API for non-commercial purposes. The primary condition for the free tier is that the application or service utilizing the data must not generate direct revenue. This includes applications that are ad-supported, require paid subscriptions, or are part of a broader commercial offering.

While specific hard rate limits (e.g., requests per second, daily data volume) for the free, non-commercial tier are not explicitly published, users are generally expected to adhere to fair usage policies. Excessive or abusive requests that impact the stability or performance of the data services may result in restrictions or suspension of access. Developers are encouraged to implement efficient data caching strategies and only request data as needed to minimize server load. For instance, developers integrating real-time data should follow best practices for API rate limiting and caching to ensure sustainable use of resources.

The free tier is ideal for:

• Independent Developers: Creating personal projects or open-source applications that help commuters.
• Academic Researchers: Analyzing transport patterns, urban planning, or developing new algorithms based on public transport data.
• Non-Profit Organizations: Building tools to assist specific community groups with transport information.
• Educational Institutions: Using real-world data for teaching and student projects.

The primary 'limit' for the free tier is its non-commercial stipulation. Any intent to monetize an application, directly or indirectly, necessitates moving to a commercial agreement. Developers should review the Auckland Transport developer terms of use to ensure compliance with the non-commercial conditions.

Real-world cost examples

Given Auckland Transport's tiered pricing model, real-world costs vary significantly based on the intended use case:

Example 1: Non-Commercial Journey Planner App

• Scenario: An independent developer creates a free mobile application that helps Auckland commuters plan journeys using real-time bus and train data from the GTFS feeds. The app includes features like real-time vehicle tracking, estimated arrival times, and interactive route maps. The app is open-source and does not display ads or charge users.
• API Usage: Frequent requests to the real-time GTFS feed and occasional requests to the scheduled GTFS feed for route information.
• Cost: NZD 0.00 per month. As this application is purely non-commercial and benefits the public without generating revenue, it falls squarely within the free tier. The developer only incurs costs for their own development tools, hosting, and backend infrastructure.

Example 2: University Research Project

• Scenario: A university research team is studying the impact of public transport delays on urban mobility patterns in Auckland using historical and real-time GTFS data. Their analysis tools are custom-built and run on institutional servers. The research is published in academic journals and is not commercialized.
• API Usage: High volume of requests for historical GTFS data (if available or collected over time) and sustained access to real-time GTFS for data collection periods.
• Cost: NZD 0.00 per month. Similar to the journey planner, academic research falls under the non-commercial free tier, provided the research outcomes are not directly commercialized. The university would bear costs for their computing infrastructure and personnel.

Example 3: Commercial Logistics Platform

• Scenario: A logistics company develops a platform that integrates Auckland Transport's real-time GTFS data and AT Park API to optimize delivery routes and manage parking for its fleet of delivery vehicles. The platform is a core part of its commercial offering, enabling more efficient and profitable operations.
• API Usage: Consistent, high-volume requests to both real-time GTFS and AT Park API across a large fleet of vehicles.
• Cost: Negotiated with Auckland Transport. This scenario clearly falls under commercial use. The company would need to contact Auckland Transport directly to establish a commercial agreement. The cost would likely be a recurring fee (e.g., monthly or annually) based on factors such as the number of vehicles, frequency of API calls, data volume consumed, and the specific terms agreed upon. This could range from hundreds to thousands of NZD per month, depending on scale and negotiation.

Example 4: Real Estate App with Parking Information

• Scenario: A real estate application provides property listings in Auckland and integrates AT Park API data to show nearby parking availability and costs for each property. The app generates revenue through property listing fees and premium features.
• API Usage: Moderate to high volume of requests to the AT Park API, potentially tied to user searches and property views.
• Cost: Negotiated with Auckland Transport. Since the app is commercial and uses AT Park data to enhance its revenue-generating services, a commercial agreement is required. The cost would be determined through direct negotiation, likely considering the number of API calls, user base, and the value derived from the integration.

How the pricing compares

Comparing Auckland Transport's pricing with other public transport data providers or general API platforms reveals a common pattern for publicly funded data. Many government or municipal entities providing public transport data, especially GTFS feeds, often offer free access for non-commercial use to foster innovation and public benefit. This aligns with a global trend of open data initiatives.

• Open Data Initiatives: Many cities worldwide, such as those covered by Google's GTFS documentation, make their GTFS feeds publicly available at no cost for non-commercial purposes. Auckland Transport follows this model, which is beneficial for developers and researchers.
• Commercial Licensing: Where commercial use is concerned, direct negotiation for pricing is a frequent approach among public transport authorities. This contrasts with commercial API providers (e.g., mapping APIs like Google Maps Platform or payment gateways like Stripe) that typically publish transparent, usage-based pricing tiers (e.g., per request, per transaction) with clear volume discounts. For example, Google Maps Platform offers a pay-as-you-go model with specific pricing for different API calls, which is different from Auckland Transport's direct negotiation for commercial use.
• General API Platforms: Platforms like Twilio or AWS provide extensive documentation on their pricing structures, often including free tiers with specific limits, and then graduated pricing based on usage metrics like messages sent, compute time, or data storage. Auckland Transport's model is less about granular, per-call pricing and more about broad licensing agreements for commercial entities.

Auckland Transport's approach prioritizes facilitating public access and innovation through its free non-commercial tier, while retaining control and ensuring appropriate use for commercial applications through direct negotiation. This allows for flexibility in commercial agreements, potentially tailoring terms to very specific business models, which might be an advantage for some enterprises compared to rigid, published pricing tiers. However, it also means less immediate transparency on commercial costs without direct engagement.

Developers seeking predictable costs for high-volume commercial applications might find the lack of published commercial pricing a point of consideration, but the free non-commercial access is a strong incentive for initial development and testing.