Localith API

API Access helps your team generate and manage the key used by the Localith google business profile api tool workflows and integrations.

Overview

Use this page when you need to create an API key for Localith, connect an integration such as n8n, or understand how API credentials fit into your wider Google Business Profile operations.

This guide focuses on account-level API access and key handling. It does not try to document every possible endpoint or integration pattern. For implementation ideas, pair this page with n8n Instructions.

Before you start

Before you create or regenerate an API key, make sure:

• you have access to the Localith account that owns the connected profiles
• you are allowed to manage API credentials for that workspace
• you know which integration or workflow will use the key
• you have a secure place to store the key once it is generated

If your team uses automations, also decide whether the key should be reused across workflows or reserved for a specific integration.

Open the API key

Your API key is accessible from the Account submenu in the bottom of the Localith sidebar.

1. Click the Account menu at the bottom of the sidebar.
2. Select API key from the submenu.
3. A popup appears with your current API key and a link to the API documentation.

Copy or regenerate your API key

Use this flow when you need credentials for a new integration or workflow.

1. Open Account > API key in Localith.
2. Copy the existing key, or regenerate it if you need a new one.
3. Paste the key into your target integration, such as n8n or an internal tool.
4. Save the integration credentials and test access with a simple read-only request first.

If you use the Localith n8n community node, follow the next setup step in n8n Instructions.

How API Access fits into the workflow

The API key is the account credential layer behind Localith integrations. In practice, that means it is used to:

• authenticate automation workflows
• connect Localith to tools like n8n
• allow controlled access to reviews, listings, and metrics data
• support update workflows where the integration writes changes back into Localith-managed operations

Current confirmed examples include review, listing, and metrics workflows described in the n8n setup guide.

Security and operational guidance

• Treat the API key like a sensitive credential.
• Test new workflows with read-only or limited-scope actions before you automate write operations.
• If a key is exposed or shared incorrectly, regenerate it and update the affected integrations.
• Keep internal ownership clear so your team knows who is responsible for integration credentials.

Limits or edge cases

• Current source coverage confirms the API Access screen and key-management workflow, but does not yet provide a full endpoint-by-endpoint developer reference.
• Integrations may still need their own validation, approvals, or branching logic outside Localith.
• API usage should follow your account permissions and any applicable rate-limit behavior.

Common questions