Skip to: Navigation | Content | Footer

For developers

The purpose of this section is to provide an overview and explanation for each of the API's in order to assist developers to understand the context of the information fields and effectively configure their own applications.

Auckland Traffic API

Summary of Changes from old to new feeds

  • Camera
    • added thumbUrl that points to the cameras thumbnail path on the ATWS server
    • all URL's (imageUrl, thumbUrl, viewUrl) are now all relative and not absolute
    • added region
    • added group
    • added latLong
    • added direction
    • removed mapX (was used for pixel-based positioning of camera icons on the static map of the old site)
    • removed mapY (was used for pixel-based positioning of camera icons on the static map of the old site)
  • CongestionLocation
    • added startLat
    • added startLon
    • added endLat
    • added endLon
    • removed mapXoffset (was used for pixel-based positioning of camera icons on the static map of the old site)
    • removed mapYoffset (was used for pixel-based positioning of camera icons on the static map of the old site)
  • Sign
    • added latLong
    • removed mapx
    • removed mapy
  • SSDF

New IC2 Feed WSDL URLs

REST

SOAP

Getting Started: What is the Auckland Traffic API?

The Auckland Traffic API lets you access real time data on traffic conditions in Auckland. The API makes available three sets of data:

  1. Traffic Congestion: This is a list of locations on the Auckland Highway Network, with the congestion status of each location. This is the same information which is used to produce the coloured map links on the Auckland Traffic Website.
  2. Signs: This is a list of Variable Message Signs deployed in the Auckland area, and any messages that are currently being displayed on them. This is the same information used to produce the VMS overlay on the Auckland Traffic Website.
  3. Camera List: This service enumerates the cameras made available through the Auckland Traffic Website, providing the camera name, id, online/offline status, and the URLs which can be used to obtain the camera image.

Old REST URLs

Quick Start Guide

These are REST XML services. Access to the REST XML services is restricted requires a username and password to be supplied as custom HTTP headers. You will need to apply for a username and password.

	Host:infoconnect1.highwayinfo.govt.nz
	User-Agent: Custom Application
	Accept-Encoding:gzip,deflate
	username: Your API Username
	password: Your API Password

To preview the services, we would recommend using a tool such as cURL.

	
	curl -k -H "username: Your API Username" -H "password: Your API Password" https://infoconnect1.highwayinfo.govt.nz/ic/jbi/TrafficCameras/REST/FeedService/
	

Alternatively, you can install the Tamper Data plug-in for the Firefox web browser, which will allow you to add the custom HTTP header variables for the username and password to the request, so that you view the XML in your browser.

Usage Policy

There are no specific guidelines on what you can do with the Auckland Traffic API, however, a key concern is that it is kept up to date. One of the key objectives of InfoConnect is to inform road users with useful information. If a partner is displaying out of date, and hence inaccurate information, this would not be acceptable. You should also note the full Terms of Use also apply that you accepted when you registered for InfoConnect.

For access to this API and any additional documentation available, please request access by completing our registration form.