The Google Maps Coordinate API is deprecated. The API will continue to work until January 21, 2016. After that date, the API will no longer be available.


  1. Overview
  2. Get an application client ID
  3. Request an OAuth token
    1. OAuth scope
    2. Client libraries
  4. Send requests to Google Maps Coordinate API


The Google Maps Coordinate API uses OAuth 2.0 for authentication. Please read Using OAuth 2.0 to Access Google APIs for details.

The Google Maps Coordinate API supports the following OAuth 2.0 authorization scenarios:

Get an application client ID

Note that an OAuth 2.0 'application client ID' is not the same as a 'Google Maps API for Work client ID'.

Obtain a client ID, of type 'web application' or 'installed application', by creating a project in the Google APIs Console:

  1. Create a project in the Google APIs Console.
  2. Click API Access in the left-hand navigation panel on the Google APIs Console.
  3. Select your project from the project drop-down at the top left.
  4. Click Create an OAuth 2.0 client id (or Create another client ID).
  5. Select the application type: web application or installed application.
    • A web application requires an HTTP endpoint that will receive the authorization codes resulting from the OAuth 2.0 authorization flow.
    • An installed application does not require such an HTTP endpoint. Instead, the user will be presented with the authorization code that they can copy/paste in your application settings.
  6. Enter your site or hostname, to complete the configuration.
  7. Click Create client ID. Your new client ID will appear on the API Access tab, along with the client secret, the default redirect URI, and other information.
  8. If you want to change the redirect URI and other settings, click Edit settings. The redirect URI is the page that Google will send users to after they have granted your application access.

Request an OAuth token

The next step is for your application to obtain an OAuth access token that grants access to the Coordinate API.

OAuth scope

You may grant one of two levels of access to a user: read-only, or read/write. These are defined using a scope parameter in the authentication request:

  • Grants read and write access to the user.
  • Grants read-only access to the user.

Client libraries

Google supplies OAuth 2.0 client libraries to support API authentication, as described in Using OAuth 2.0 to Access Google APIs. The client libraries take care of communication with the authorization servers, storage of the access and refresh tokens, and negotiation of new tokens. Libraries are available for a number of languages, including Java, PHP, and Python.

You will need the following pieces of information when using a client library:

  • The OAuth scope.
  • Your client ID.
  • Your client secret.
  • The redirect URI.

Send requests to Google Maps Coordinate API

Once you've successfully authenticated, you can start sending requests to the Google Maps Coordinate API.

Requests to the API must be accompanied by an OAuth access token as the value of an Authorization header:

Authorization: Bearer ya29.AHES6ZQY34C3TTHkZr0sm1zntv2exa80xd1yZlvD3qwwe5aqmA2ZJw

Send feedback about...

Google Maps Coordinate API