Feed Setup

The following information will help you get your feeds set up and running correctly.

Feed file hosting

The Waze content acquisition system automatically fetches your feed data periodically. To ensure that Waze retrieves the correct feed file, make it accessible over standard network protocols (HTTP, HTTPS, FTP or SFTP).

  • You can secure your files with a username and password using either BASIC or DIGEST authentication. Windows NT LAN Manager (NTLM) is not currently supported.
  • We transfer the feed files using HTTPS with a SSL certificate to secure the data transfer.
  • You provide the login and password combination through Partner Hub.
  • The content acquisition system fetches data every few minutes. If you have special requirements regarding the feed frequency, please contact the Waze team so that we can adjust our polling periods to reflect your feed update cycle.

XML validation

Waze uses the following XML schema to define the acceptable structure of a Closure and Incidents Feed Specifications (CIFS) feed: https://www.gstatic.com/road-incidents/cifsv2.xsd.

There are a number of tools available on the internet that can help you validate the structure of your XML feeds. These include, but are not limited to:

Critical feed changes

Before making any of the following changes, notify the Waze team by completing this form and editing your request in the Portal to identify the updated feed.

  • Modifying, adding, or removing regions or countries from your feed.
  • Updating the feed URL or any credentials required for accessing the information.
  • Changing the feed structure or tag names.

Feed specifications

A single feed file can provide information on multiple closures and incidents. If you are providing information on multiple events, each closure or incident must be detailed in a separate element and must have a unique Id. These sections should use the local time and date. The CIFS specification details all the tags available to describe your incidents and closures.