Need Updated Guidance on Google Business Profile API, OAuth Verification, Quotas, and Multi-Location SaaS Integration

Google Cloud Integration Services
1

Hello everyone,

I have been researching Google Business Profile APIs, OAuth verification requirements, quotas, and related documentation.

However, Google products, APIs, permissions, and onboarding requirements can change over time, and I would like to confirm the current recommended approach using the most up-to-date information available.

Our planned workflow is:

  • A business owner connects one or more Google accounts via OAuth.

  • Different Google accounts may have access to different Business Profile locations.

  • The platform retrieves all locations the user is authorized to manage.

  • Locations from multiple connected Google accounts are aggregated into a single dashboard.

  • The user can manage all authorized locations from one place.

Example:

  • Google Account A manages Locations 1–10.

  • Google Account B manages Locations 11–20.

  • The user connects both accounts.

  • The platform retrieves and displays all locations in a unified interface.

I would appreciate guidance on the following questions:

  1. Is this workflow compliant with current Google Business Profile API policies?

  2. Is it acceptable to aggregate locations from multiple authorized Google accounts into a single dashboard?

  3. Which API(s) should currently be used to retrieve all locations a user is authorized to manage?

  4. What is the recommended onboarding process from development to production, including:

    • Google Cloud Project setup

    • OAuth Consent Screen configuration

    • OAuth Verification

    • Production approval requirements

    • Quota allocation and quota increase requests

  5. Are there any special requirements or best practices for SaaS platforms managing multiple client accounts and locations?

  6. Is creation and management of Google Business Profile Posts (Local Posts) currently supported through any public API, partner program, or approved alternative solution?

  7. Are there any current limitations, policies, or requirements developers should be aware of before implementing this type of integration?

Any updated documentation, recommendations, or official guidance would be greatly appreciated.

Thank you for your time and assistance.