Places SDK and the
Places library of the
Maps JavaScript API, if
specifically enabled for Google Maps APIs for Work support.

Geolocation API
, if specifically enabled for Google Maps APIs for Work support.

Google Maps Mobile SDK for Work (
Maps SDK for Android and iOS),
if specifically enabled for Google Maps APIs for Work support.

The following APIs are not covered by Google Maps APIs for Work.
Applications that use these APIs must do so in compliance with the
published Terms of Service for these APIs, and are not covered by the
Google Maps APIs for Work SLA, or eligible for technical support at this
time:

A single load of the Maps JavaScript API into a page. The
Maps JavaScript API is reloaded every time a page that
uses the API is reloaded. User interactions with the map (eg. panning, zooming,
changing map types) do not generate more page views. Note however that a page view
is generated if the API is loaded into the page even if the API is not
then used to display a map. We therefore recommend against including the
<script> tag that loads the API in page templates, and
recommend
loading the API asynchronously on pages where maps are only displayed in response to
optional user activity.

Note that Google Maps Platform Standard and Premium Plan
applications are limited by map loads,
which are slightly different from page views. Please refer to the
Google Maps Platform FAQ for more
information.

The Google Maps Mobile SDK for Work uses map loads to track usage.
Please refer to the Google Maps Mobile SDK
usage limits
for more information.

Requests that constitute page views (as defined
above) are applied against the total number of page views
purchased with your Google Maps APIs for Work license. When this limit is reached,
you will need to renew your license promptly.

What are the usage limits for the Google Maps Mobile SDK for Work?

Each map load is applied against the total number of map loads
purchased with your Google Maps Mobile SDK for Work license. When this
limit is reached, you will need to renew your license promptly. Refer to
the
Google Maps Mobile SDK usage limits for more information.

What are the usage limits for Geocoding requests made from the Maps JavaScript API?

Google Maps APIs for Work customers are provided with the following
usage limits for Geocoding requests made from the Maps JavaScript API:

Service

API being used

Limits

Geocoding

Maps JavaScript API

Geocoding has a daily allocation and rate limit which is applied per
user session, regardless of how many users share a given IP
address.

This service should not be used for batch geocoding operations; you
should use the
Geocoding API for such operations.

What are the usage limits for the Google Maps
image APIs?

Google Maps APIs for Work customers are provided with the following
usage limits for the Google Maps image APIs:

Service

Limits

Maps Static API

Requests are applied against the total number of page views
purchased with the Google Maps APIs for Work license.

The maximum image size is 2048 by 2048 pixels. This is calculated as
size times scale, as explained below.

Street View API

Requests are applied against the total number of page views
purchased with the Google Maps APIs for Work license.

The maximum image size is 2048 by 2048 pixels.

Maps Static API images can be requested up to 2048x2048 pixels. Because the
scale value in a static map request affects the number of
pixels returned, the maximum size value is different for
each scale level:

Scale

Max Size

Returns

1

2048x2048

2048x2048

2

1024x1024

2048x2048

4

512x512

2048x2048

The Street View API does not support the scale
parameter.

Using the Google Maps Platform

What keys or credentials should I use for different Google Maps Platform products?

Each time you use the Google Maps Platform you must include credentials to validate
your request. The type of credentials required varies depending upon the APIs
being used with your Google Maps APIs for Work licence. For most APIs, you will use
your client ID. In some cases, you will need an API key.

Client ID: A client ID is given to
you when you sign up as a Google Maps APIs for Work customer.

Example of loading an API with a client ID:
&client=gme-companyname

Digital Signature: Typically, a
digital signature is used by Google Maps APIs for Work customers when
authenticating with a client ID. The digital signature is generated using
a cryptographic key provided to you by Google.

API Key: An API key is a unique identifier that you
generate using the
Google Cloud Platform Console. API keys are generally used with the standard APIs.
Google Maps APIs for Work customers typically use a client ID, though a few
APIs require an API key instead of the client ID. For APIs that require an
API key, you can choose to use an API key without applying restrictions (called a
“generic API key”) or a key with restrictions applied for greater security
(recommended). APIs in any platform may use a generic API key.

If you choose to add a restriction (for example, IP address) to the API key, once
restricted, a key will only work on platforms that support that type of restriction.
Four types of API key restrictions are available:

Note: When generating a key on the Google Cloud Platform Console,
Google Maps APIs for Work users must make sure to select the project that
was created for them upon signup. This project will include the word
Business or Work in the name.

Example of loading an API with a key:
&key=AIzaSyBjsINSH5x39Ks6c0_CoS1yr1Mb3cB3cVo

The table below indicates which credential should be used with each Google Maps Platform
product. (As mentioned above, the types of API key restrictions are: server, browser, Android,
and iOS.)

How do I access the Google Maps Platform using a Google Maps APIs for Work client ID,
from a page that's loaded over HTTPS (SSL)?

To access the Google Maps Platform from a page that's loaded over HTTPS, you must first
authorize the HTTPS URLs on which you wish to use the API.

How do I load the Maps JavaScript API over HTTPS (SSL) when using the
Common Loader base_domain parameter?

It is not possible to load the Maps JavaScript API over SSL using the
common loader with the base_domain parameter set.

The base_domain parameter does not affect your application's
performance — API requests are always handled by the optimal Maps
server for a particular user's location regardless of the domain from which
the API is loaded.

KML

How do I render KML files that are hosted on intranet
sites on a map?

The KmlLayer class that generates KML overlays in the
Maps JavaScript API uses a Google hosted service to retrieve
and parse KML files for rendering. Consequently it is not possible to display
KML files that are not hosted at a URL that is available publicly accessible,
or that require authentication to access.

If you need to develop applications that use KML files hosted on intranet
sites we recommend that you render the KML on the client side by using
third-party JavaScript libraries. As the KML file is analyzed by the
browser, performance may be lower than by using the
KmlLayer class.

URL Signing

Can I sign URLs using JavaScript?

We strongly recommend against signing URLs using JavaScript as this would
expose your cryptographic key to end users. Therefore signatures should
only be generated by server side components.

An HTTP 403 response indicates a permission issue, likely because the
signature could not be verified for this request. This could be because:

A signature has been specified but is incorrect for this request.

The request specifies a Google Maps APIs for Work client ID but
does not specify a signature, and the web service being called requires that all
requests made using a client id include a valid signature.

A signature has been specified but the associated Google Maps APIs for Work
client ID has not been specified.

Styling

Why aren't businesses showing up on my map?

When loading a map using the Maps JavaScript API and
including a client parameter, business listings on the map are turned off
by default. To turn them back on, you'll need to include some
styling code with your
map: