Google Maps API Analyzer

Analyze your Google Maps API key to see which services are enabled. Check API key permissions, quotas, and service availability for Google Maps, Places, Geocoding, and more.

💡 Pro Tip: Use the toggle to test both Legacy (v3) and Modern (v1) APIs! Each version uses different endpoints and may give different results.

API Key Analysis

API keys should start with "AIza" and be 39 characters long

API Version

Choose between Legacy and Modern APIs

ModernLegacy
How It Works

This tool analyzes your Google Maps API key using improved server-side testing. It makes test requests to various Google Maps services and provides detailed information about their status.

Services Tested:

  • Maps JavaScript API - Core mapping functionality
  • Places API - Place search and details
  • Geocoding API - Address to coordinates conversion
  • Directions API - Route planning and navigation
  • Distance Matrix API - Travel time and distance calculations
  • Static Maps API - Generate static map images
  • Street View Static API - Street view imagery
  • Elevation API - Terrain elevation data
  • Time Zone API - Time zone information
  • Geolocation API - Device location detection
  • Roads API - Road network information

Dual API Version Testing:

• Legacy (v3) APIs: Test older, stable endpoints with simpler parameters

• Modern (v1) APIs: Test newer endpoints with enhanced features and better error handling

• Different Results: Some services may work better with different API versions

• Server-side Security: All testing happens on secure servers

Common Issues & Solutions:

  • REQUEST_DENIED: Service not enabled in Google Cloud Console
  • API Key Issues: Verify billing is enabled and API restrictions are configured
  • Quota Exceeded: Check your API usage limits
  • Version Differences: Try switching between Legacy and Modern APIs for better results
  • FieldMask Errors: Common with Modern v1 APIs - service is likely enabled
  • Invalid Key Format: Ensure key starts with "AIza" and is 39 characters

Important Notes:

  • Your API key is not stored or logged - it's only used for testing
  • Test requests may count against your API quotas
  • Some services may require specific billing setup
  • Results are based on current API key configuration
  • Server-side testing provides more accurate results than client-side validation