Waze
Waze is a Google-owned, community-driven navigation and real-time traffic application. Its developer surface is not a self-service JSON REST API but a set of public URL-invocation and embed contracts plus partner-gated data and SDK programs. Waze Deep Links open the Waze app from a URL to locate an address, drop a pin, or start turn-by-turn navigation; the Waze iFrame embeds the interactive Live Map in any web page; Waze for Cities Data Feeds let agencies exchange road-closure, incident, and working-vehicle data (CIFS, WZDx, DATEX II, ESRI) and receive a partner-specific JSON alerts feed; the Waze Transport SDK gives transportation apps ETA/routing and trip-data collection; and the Waze Audio Kit surfaces audio content in-drive. Developer documentation is hosted on Google for Developers at developers.google.com/waze and partner programs are provisioned through the Waze Partner Hub.
Waze publishes 4 APIs on the APIs.io network. Tagged areas include Company, Mobility, Navigation, Maps, and Traffic.
Waze’s developer surface includes documentation, getting-started guide, support, engineering blog, authentication, and 13 more developer resources.
Kin Score
APIs 4
Individual APIs this provider publishes, each with its own machine-readable definition.
Waze Deep Links
URL-invocation API to open the Waze app from an external link to locate an address, drop a pin, or start navigation. Query params include ll (lat,lon), q (search), navigate, z (...
Waze iFrame (Live Map)
Embeddable client-side component that renders the interactive Waze Live Map inside a web page via an
Waze for Cities Data Feeds
Partner data-exchange for road closures, incidents, and working vehicles using CIFS (preferred), WZDx, DATEX II, or ESRI formats; Waze returns a partner-specific JSON alerts fee...
Waze Transport SDK
Partner-gated SDK for transportation apps to add ETA and routing points and trip-data collection using Waze real-time traffic and location data.
Security Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Get Started 2
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Access & Security 5
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API