Google Maps Getting Started: API Keys & First Request (2026)

Getting started overview

Integrating Google Maps Platform into an application involves several steps to ensure proper authentication, API enablement, and billing setup. The core process includes creating a Google Cloud project, enabling specific Google Maps Platform APIs, and generating an API key for request authentication. This key is used across various Google Maps Platform services, including the Geocoding API, Places API, and Maps JavaScript API. Once set up, developers can make API requests to retrieve geographic data, display maps, or implement location-based functionalities. Google provides client libraries and extensive documentation to assist with integration across multiple programming languages and platforms, such as JavaScript, Python, and Java Google Maps Platform documentation.

A quick reference for the getting started process is outlined below:

Create an account and get keys

Before making any requests to the Google Maps Platform, you need to set up a Google Cloud project and obtain an API key. This key acts as a unique identifier for your project and is essential for authenticating your API calls. Google Maps Platform operates on a pay-as-you-go model, but includes a recurring monthly credit of $200 that covers many common use cases Google Maps Platform pricing details.

1. Create or Select a Google Cloud Project:
   • Navigate to the Google Cloud Console.
   • If you don't have an existing project, click 'Select a project' at the top, then 'New Project'. Give your project a descriptive name.
2. Enable Google Maps Platform APIs:
   • From the Google Cloud Console, use the navigation menu (☰) to go to 'APIs & Services' > 'Library'.
   • Search for the specific APIs you intend to use. For typical web mapping, you'll likely need the 'Maps JavaScript API', 'Geocoding API', and 'Places API'.
   • Click on each API and then click the 'Enable' button.
3. Set Up Billing:
   • Google Maps Platform requires an associated billing account, even if you plan to stay within the free tier. This enables the platform to track usage and apply the monthly credit.
   • Go to 'Billing' in the Google Cloud Console navigation menu.
   • If you don't have a billing account, follow the prompts to create one and link it to your project. You will need to provide payment information.
4. Generate an API Key:
   • In the Google Cloud Console, navigate to 'APIs & Services' > 'Credentials'.
   • Click '+ CREATE CREDENTIALS' and select 'API key'.
   • A new API key will be generated. Copy this key immediately.
   • Restrict Your API Key: This is a critical security step. Click 'RESTRICT KEY' on the newly created key.
   • Under 'Application restrictions', select 'HTTP referrers (web sites)', 'IP addresses (web servers, cron jobs, etc.)', or 'Android apps' / 'iOS apps' depending on your application type. Provide the appropriate referrers (e.g., *.yourdomain.com/*) or IP addresses.
   • Under 'API restrictions', select 'Restrict key' and choose only the Google Maps Platform APIs you've enabled for your project.
   • Click 'Save'.

Your first request

Let's make a simple Geocoding API request to convert an address into geographic coordinates (latitude and longitude). This API is foundational for many location-based services and provides a straightforward way to test your API key and setup Google Maps Geocoding API overview.

For this example, we'll use cURL, a command-line tool for making HTTP requests, which is pre-installed on most Unix-like operating systems and available for Windows. Replace YOUR_API_KEY with the key you generated in the previous step.

Example: Geocoding an Address

curl "https://maps.googleapis.com/maps/api/geocode/json?address=1600+Amphitheatre+Parkway,+Mountain+View,+CA&key=YOUR_API_KEY"

Expected JSON Response (abbreviated):

{
  "results": [
    {
      "address_components": [...],
      "formatted_address": "1600 Amphitheatre Pkwy, Mountain View, CA 94043, USA",
      "geometry": {
        "location": {
          "lat": 37.4224021,
          "lng": -122.0839988
        },
        "location_type": "ROOFTOP",
        "viewport": {
          "northeast": { ... },
          "southwest": { ... }
        }
      },
      "place_id": "ChIJ2e2Eg_W6j4ARhU1w-9mN_9E",
      "types": ["street_address"]
    }
  ],
  "status": "OK"
}

This response indicates that the Geocoding API successfully processed the request, returning the latitude and longitude (lat and lng) for the specified address, along with other detailed address components and a status of OK.

Common next steps

After successfully making your first API call, you can explore a range of Google Maps Platform features to enhance your application. The specific next steps depend on your project's requirements, but common paths include:

• Displaying a Map: Integrate the Maps JavaScript API to embed interactive maps directly into web pages. This involves adding a script tag and a div element to your HTML, then initializing the map with JavaScript.
• Place Search and Autocomplete: Utilize the Places API to enable users to search for specific places (businesses, landmarks, points of interest) or provide autocomplete suggestions as they type. This can significantly improve user experience for address input forms.
• Directions and Routing: Implement the Directions API to calculate routes between two or more locations, considering various modes of transport (driving, walking, bicycling, transit) and providing turn-by-turn instructions.
• Reverse Geocoding: Use the Geocoding API's reverse geocoding functionality to convert geographic coordinates (latitude and longitude) back into human-readable addresses. This is useful for displaying addresses based on user clicks on a map or device location Reverse Geocoding requests.
• Mobile SDKs: For native mobile applications, integrate the Maps SDK for Android or Maps SDK for iOS to deliver rich, interactive map experiences tailored for mobile devices.
• Advanced Features: Explore more advanced capabilities like Distance Matrix API for calculating travel times and distances for multiple origins and destinations, or Street View Static API for embedding panoramic images.

Troubleshooting the first call

Encountering issues during your first API call is common. Here are some frequent problems and their solutions:

• REQUEST_DENIED Status:
  • Cause 1: Missing API Key. Ensure you've included your API key in the URL as &key=YOUR_API_KEY.
  • Cause 2: API Not Enabled. Verify that the specific Google Maps Platform API you are trying to use (e.g., Geocoding API) is enabled for your Google Cloud project in the API Library.
  • Cause 3: Billing Not Enabled. Even with the free tier, a billing account must be linked to your project. Check your Google Cloud Billing settings.
  • Cause 4: Incorrect API Key Restrictions. If you've restricted your API key, ensure the restrictions (HTTP referrers, IP addresses, API restrictions) correctly allow access from where you're making the request and to the specific API. For testing, you can temporarily remove restrictions, but re-apply them for production.
• INVALID_REQUEST Status:
  • Cause: Malformed URL or Parameters. Double-check the API endpoint and parameters. For the Geocoding API, ensure the address parameter is correctly URL-encoded (e.g., spaces replaced with + or %20). Refer to the Geocoding API request documentation for correct syntax.
  • Response: The API documentation often specifies required parameters. For instance, the Geocoding API requires either an address or latlng parameter.
• OVER_QUERY_LIMIT Status:
  • Cause: Exceeded Usage Limits. This typically means you've exceeded the free tier or project-specific query limits. Check your API usage metrics in the Google Cloud Console.
  • Response: If you've exhausted the free credit, ensure your billing account is active and correctly configured for paid usage.
• CORS Issues (for browser-based JavaScript):
  • Cause: API Key restriction mismatch. If you're seeing CORS errors in your browser console when using the Maps JavaScript API, ensure your API key's HTTP referrer restriction includes the domain from which your web page is served. For local development, you might need to add http://localhost:*/*.
  • Response: Consult the MDN Web Docs on CORS for a general understanding of Cross-Origin Resource Sharing.
• No output or blank map:
  • Cause: JavaScript errors or incorrect HTML element. For the Maps JavaScript API, ensure your HTML contains a div element with a specified width and height for the map to render into, and that your JavaScript code correctly initializes the map object. Check your browser's developer console for JavaScript errors.