You can join a group of pioneering companies in the transportation space by becoming a partner and using the Waze Transport SDK. We aim to provide technology and data intelligence to improve your business, while increasing the transparency and efficiency between your drivers and riders.
This section describes the Waze Transport SDK. You must be a partner in order to download the SDK. If you are already a partner, you can continue to the Waze Transport SDK documentation.
It appears that you are not a Waze Transport SDK partner. If you are, please make sure you're logged in with your whitelisted email address to view our documentation guidelines. Log into your whitelisted account when you click Log in or the Account icon in the top right corner of the screen.
If you haven't joined our partnership yet, please fill out an application below:
The Waze Transport SDK links your app to Waze and provides free driving data. With the Waze Transport SDK, you can:
- Get ETA & routing points: Add capabilities like drive and arrival time calculations, based on Waze's real-time traffic and location data
- Access navigation & fastest routes quickly: Drivers seamlessly switch between your app and Waze to find the fastest routes and avoid unforeseen delays
- Gain unique insight: Use the Waze SDK to generate transportation data such as travel times for service deliveries
The SDK is not for partners to build their own navigation app. However, you may use the data provided as part of your app's customer experience and user interface.
The SDK does not support the following:
- Server-side access to Waze data, like traffic reports, speed, etc
- Embedding the Waze map and navigation in your app
- Building a route planning and sharing tool
- Building a fleet management tool
- SLA-based paid service
The Waze Transport SDK is available with the following technical requirements:
|OS Version||Waze Version|
Comparing the Waze Transport SDK and Waze Deep Links
The Waze Transport SDK is intended for transportation apps that are used by high frequency, professional drivers and customers.
If you aren't interested in receiving routing data from Waze and if your drivers don't require a mechanism to switch between Waze and your app frequently, then Waze Deep Links is the more lightweight and suitable solution.
Waze Deep Links lets you open the Waze client application through an external URL, which can be accessed from another mobile app or a mobile web page.
The following table lists the capabilities of the Waze Transport SDK and Waze Deep Links:
|Waze Transport SDK||Waze Deep Links|
|Start a drive from your app|
|Trigger a search in Waze from your app|
|Set the Waze map to a specific location from your app|
|Open Waze from your mobile website|
|Button in Waze which brings users back to your app|
|Data sent to your app from Waze:
(Can be disabled)
Attribution Guidelines and Authorized Modifications
When using the Waze navigation data (e.g., the ETA or route points), you must provide reasonable attribution in your app. The attribution should:
- Be clear, not misleading, and placed close to where the data is used in the user interface
- Say “Powered by Waze” unless explicitly agreed otherwise in writing
- Only be used with Waze data that is used as provided or modified as permitted according to the rules in the section below.
Waze content may only be modified slightly and in a way that may not significantly impact data accuracy, if used on any driver or customer user interface. The following rules apply:
- Route data may not be modified and displayed. A Waze route is exactly the route as provided.
- ETA data may only include an added 1-2 minutes per stop to attribute for real life circumstances such as a driver walking up to the front door or a customer stop grace period of 1-2 minutes before continuing to the next stop.
Generally, we do not permit the use of modified data outside of these rules, specifically on customer user interfaces, unless reviewed on a case by case basis and approved in writing.
Please ensure that brand attribution is visible and readable. Placement of attribution should be within context of usage and close to Waze data associated with it. Size should be no smaller than the following samples.
The following example shows "Powered by Waze" on different background colors. (You can use your app’s color palette.)
The following are examples of problematic attribution:
|The text should be readable.|
|The image colors should be clearly visible.|
Color treatment and considerations
Feel free to use the Waze logo on any colored background or shape you choose. Below are examples of the Waze logo per background type (colored background, white and black).
Use the following transparent logo for color backgrounds only:
Never use the negative of the logo, as the following example shows:
Customer UI example
The following example shows a customer UI example:
Driver UI examples
The following examples show branding in a driver UI:
Headers and banners
You can add your logo to the header below for use when sending emails to drivers and users:
Images for social channels
Combine your brand (logo and/or palette) with the image below to create a shared partnership graphic. You will be supplied with an Adobe Illustrator file that you can easily edit and adjust per social channel.