The Google Static Maps API may issue an error or warning when something goes wrong.
Invalid requests
In the case of an invalid request, the Google Static Maps API returns
an HTTP 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 | Status code |
|---|---|
The request includes an invalid parameter, or a required parameter is
missing. For example, the size parameter is not within the
expected range of numeric values, or is missing from the request. |
400 BAD REQUEST |
| The API key included in the request is invalid. | 403 FORBIDDEN |
Errors that prevent a map from being displayed
If the request is valid, but another error occurs that prevents the map from
being displayed, the Google Static Maps API returns an error image
instead of the map. An example of such an error condition is when the
application exceeds its
usage limits.
Warnings
For some error conditions, the API returns a map but some information may
be missing from the map. When this happens, the API returns a warning in the
form of an HTTP header named X-Staticmap-API-Warning.
For example, the following URL contains an unexpected value in the
markers parameter:
https://maps.googleapis.com/maps/api/staticmap?center=Williamsburg,Brooklyn,NY&zoom=13&scale=1&size=400x400&markers=sdgaags&key=YOUR_API_KEY
The API returns a map and the following HTTP header:
X-Staticmap-API-Warning:Error geocoding: marker 1
The following table describes the warnings that the API may issue as HTTP headers:
Warnings in X-Staticmap-API-Warning headers
|
|
|---|---|
Error geocoding:
[center, ][marker #number, ][visible #num, ][path #num, ]* |
An error occurred while attempting to geocode the request. There are
many variants of this message, depending on the element where geocoding
failed (center, marker, visible, or path) and the number of elements
that failed. One example of this warning is
X-Staticmap-API-Warning:Error geocoding: marker 1, as
shown in the above example. |
Too many geocoded markers requested (max is 15). Please correct
this or in future some markers may fail to geocode. |
The request specifies more than the allowed maximum number of markers with a human readable address. The maximum is 15. Note that this limit applies only to markers specified as a human-readable address that requires geocoding. It does not apply to markers specified with latitude/longitude coordinates. Note: This limit is currently reported as a warning only, but it's recommended that you reduce the number of geocoded markers in the request, to ensure geocoding is successful for all markers. |
Too many geocoded polyline vertices requested (max is 15). Please
correct this or in future some polylines may fail to geocode. |
The request specifies more than the allowed maximum number of polylines with a human readable address. The maximum is 15. Note that this limit applies only to polylines with vertices specified as human-readable addresses that require geocoding. It does not apply to polylines specified with latitude/longitude coordinates. Note: This limit is currently reported as a warning only, but it's recommended that you reduce the number of geocoded polylines in the request, to ensure geocoding is successful for all polylines. |
You can see the warnings in the Chrome DevTools Console, the Firefox Web Console, or other equivalent tools in your browser.
Need help? Visit our