RP Promap Help Series

Google API Setup & Integration Testing

Overview

This guide walks you through setting up your Google Maps API for ProMap and using our new Integration Testing Tool to verify everything is configured correctly.

👉 Full setup guide: https://help.roseperl.com/en/articles/11594871-creating-a-google-api

🚀 New: Integration Testing Tool

Inside ProMap → Settings, you can now run a full diagnostic check of your Google API configuration.

What the Test Checks

The tool verifies the following services:

Billing
Geocoding API
Maps JavaScript API
Places API
Distance Matrix API
Geolocation API
Places API (New)

It uses your API key to confirm each service is:

Enabled
Properly configured
Returning valid responses

✅ Successful Configuration Example

When everything is configured correctly, you will see:

“Google Maps integration is fully configured. All required services are enabled and working correctly.”

Each service will show:

Status: Passed
Description confirming functionality (e.g., map rendering, address conversion)

⚠️ If a Test Fails

If any service fails, you will see a message like:

“Google Maps integration is not fully configured. Your API key is valid, but some required services are not enabled.”

Example Failure

Places API – Failed
Required for address autocomplete and search functionality.

👉 Enable API: https://console.cloud.google.com/marketplace/product/google/places-backend.googleapis.com

🛠 How to Fix Failed Tests

Click the Enable API link shown next to the failed service
Sign in to your Google Cloud account
Enable the missing API
Ensure billing is active on your project
Return to ProMap and click Run Test again

Repeat until all checks show Passed.

💡 Important Notes

Billing Requirement

Even if APIs are enabled, Google requires billing to be active for most services.

Multiple Places APIs

You may need BOTH:

Places API
Places API (New)

These are separate services and must both be enabled.

API Key Permissions

Ensure your API key:

Has access to all required services
Is not overly restricted (or restrictions match your domain/setup)

🤖 Automated Setup Option

Need help setting up your Google API?

👉 Use our automated setup tool: Rose Perl Dashboard

This tool helps you:

Generate a Google API key
Enable required services automatically
Configure billing correctly

🔍 Running the Test

Go to ProMap → Settings
Enter your Google API Key
Click Run Test

The system will:

Run a check for Billing, Geocoding, Maps JavaScript, Places, Distance Matrix, Geolocation, and Places API (New) using the API key in this form.

📸 Reference Example

Below is a real example of the Integration Testing Tool inside ProMap:

Example with Errors:

🔍 What to Look For (Annotated Guide)

1. Green Success Banner
Confirms your Google Maps integration is fully configured.

2. Run Test Button
Use this anytime after making changes to revalidate your setup.

3. Integration Check Results Panel
Displays each API/service status individually.

4. Status Indicators

✅ Passed = Working correctly
⚠️ Failed = Requires action

5. Service-Level Feedback
Each item explains exactly what is working or what needs fixing (e.g., "Map rendering is working correctly" or "API not enabled").

6. Action Links (on failure)
If a service fails, a direct Enable API link will appear—click it to fix the issue in Google Cloud.

🚨 Common Errors & Resolutions

Based on our latest guidance: 👉 https://help.roseperl.com/en/articles/12062691-google-api-errors-common-errors-and-resolutions

1. API Not Enabled

Error: Service shows Failed (e.g., Places API not enabled)

Fix:

Click the provided Enable API link in the test results
Enable the API in Google Cloud Console
Re-run the test

2. Billing Not Enabled

Error: Billing check fails or APIs return errors despite being enabled

Fix:

Go to Google Cloud → Billing
Attach a valid billing account to your project
Re-run the test

3. API Key Restrictions

Error: Requests fail even though APIs are enabled

Fix:

Check API key restrictions
Ensure:
- Correct referrer (your domain) is added
- Required APIs are allowed under API restrictions
For testing, you may temporarily remove restrictions