Create partner API keys and set up your webhook
Admins create test and live keys, set the live webhook and the events it sends, and check recent deliveries.
Before you start
Everything here is on the Developers tab of the partner console (Partners in the sidebar). Only admins can create keys or change the webhook; others see “Only admins can create keys or change the webhook.”
Your server uses a key to create accounts, open card sessions and report changes. Test keys start with lgp_test_ and see only test companies; live keys start with lgp_live_ and see only live ones.
Create an API key
Under API keys, type a New key name you will recognize, such as
Production server.Next to the name, choose Test or Live.
Select Create key.
New key name (1), Test or Live (2), Create key (3) and Revoke (4). The keys’ first characters are blurred. Screen from October 23, 2026. Under Your new key, select Copy and store the key on your server. Then select I have stored it.
The key is shown only once: “Copy it now and store it on your server. It will not be shown again.” The list then shows its name, a Test tag for test keys, its first characters and when it was last used.
Never put a key in a web page or an app. Anyone with it can act for your platform.
Revoke a key
Select Revoke on the key’s row.
At “Requests with it will fail.”, select Revoke again, or Keep to cancel.
You see “Key revoked. Requests made with it now fail.”, and the key shows Revoked. Requests with it stop working at once.
To replace a key without breaking anything, create the new key, switch your server to it, and only then revoke the old one.
Set up the live webhook
A webhook is an address on your server that LegitGeo calls when something happens to one of your companies, such as a check finishing. The console sets the live webhook. Your server sets the test webhook with a test key, through the API.
Under Live webhook, enter the Endpoint: the full address, starting with
https://.Under Events, untick any events you don’t want. With every box ticked, you get every event.
Select Save webhook.
The endpoint and events (1), Save webhook (2), Send a ping (3) and Recent deliveries (4). A demo partner with a made-up endpoint. Screen from October 23, 2026. The first time you save, copy the Signing secret and store it on your server, then select I have stored it. It is shown only once.
Select Send a ping, above the endpoint, to test it. You see “Ping delivered.”, or “Ping not delivered” with the HTTP status, and LegitGeo retries.
The events are Account ready (the first storefront check finished), Newly named by AI, Dropped by AI, Visibility updated (the weekly AI check finished), Storefront checked, Score dropped (the storefront score fell 5 points or more), Map rank updated, New review, Lead captured, SEO alert and Change measured (a change you reported got its verdict).
For live companies, Newly named by AI, Dropped by AI and Visibility updated start once LegitGeo switches on the weekly AI check for your platform.
Each delivery is signed with the Standard Webhooks scheme, so an official Standard Webhooks library can check it. Answer with a 2xx status within 10 seconds. To replace the secret, select Rotate signing secret, copy the new one and update your server.
Check recent deliveries
Recent deliveries lists the last 15 events sent to your live webhook. Each row shows the event’s name, such as storefront.checked, then Delivered, Failed or Retrying with the number of tries so far, the HTTP status your server answered, and when. Before anything is sent, it says “Nothing sent yet. Events appear here as checks finish.”
The Webhook tile at the top of the console shows Healthy, or how many recent deliveries failed.