This page describes the error messages that can be returned by the Maps Embed API. When an error occurs, the Maps Embed API presents error message text in place of the map. Certain error conditions may also occur, which result in the display of a darkened watermarked map.
In the case of an invalid request, the Maps Embed API returns
4xx status code and a message describing the
problem. Below are examples of such error conditions. Note: This is not
a complete list of the possible errors. Please check the actual error code
and message returned by the API for details of specific problems.
|Example of error condition
|The request includes an invalid parameter, or a required parameter is
missing. For example, the
zoom parameter is not within the
expected range of numeric values, or a required parameter is missing from
400 BAD REQUEST
|The API key included in the request is invalid.
API key and QPS errors
API key and QPS errors are treated as invalid requests. Possible causes include the following:
- Missing or invalid API key. To resolve this error, ensure that your request includes a valid API key. Get an API key.
- Maps Embed API is not enabled for your project. Learn about enabling and disabling APIs.
- API key has a restriction violation. Read more about API key best practices.
Billing and HTTP referer errors
A darkened map, or "negative" Street View image, watermarked with ￼"for development purposes only" is returned when any of the following is true:
- Billing has not been enabled on your account. Enable billing.
- The provided billing method is invalid (for example an expired credit card). To resolve this, visit the Google Cloud Console, and ensure that you have provided a valid method of payment.
- A self-imposed daily limit has been exceeded. Learn how to view or change daily billable limits.
- The request is missing an HTTP referer, and you are using a referer-restricted API key. Learn more about adding referers.
Checking errors in your browser
For Billing and HTTP referer errors, the Maps Embed API writes
error messages to
window.console. For invalid requests (including
API key and QPS errors), only the HTTP
4xx status code is reported
in the console. This section explains how you can check the console output in
Google Chrome. If you are using any other browsers, please check the developer
documentation for your browser. For your reference, this is a list of tools to
check console output in some other browsers.
- Console for Internet Explorer.
- Web Console for Firefox.
- Remote debugging for Android.
- Web Inspector for iOS.
- To open the Developer Tools, select the menu icon > More Tools > Developer Tools.