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 Waze retrieves the correct feed file:

  • Make it accessible: Use standard network protocols (HTTP, HTTPS, FTP, or SFTP).
  • Secure your data (optional): You can secure your feed with a username and password using BASIC authentication over HTTPS. You provide the login and password combination through Partner Hub.
  • Ensure accessibility: Ensure the hosted file is accessible globally.
    • To avoid disruptions in data fetching, please ensure your firewall does not block access based on country, IP address, or geographic region. These restrictions may prevent us from retrieving your feed data.
    • We use a dynamic system for pulling closure and incident information. This means we don't use static IPs or support pre-authorized URL/domain/wildcard, or DNS entry authorization.

Feed frequency

The content acquisition system fetches data every few minutes. If you have special requirements regarding the feed frequency, add a note indicating this request when submitting the feed, or contact the Waze team so 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.