# Lusha setup for PopMCP

One Lusha API key, copied from API & connectors in your Lusha dashboard and pasted into PopMCP's API key field. Your Lusha email is optional and only used for tables.

- Auth: API credentials
- Setup time: 1 min
- API base URL: https://api.lusha.com
- Credentials screen: https://dashboard.lusha.com/api/manage-api-keys
- Provider docs: https://docs.lusha.com/v2/authentication

## Before you begin

- A Lusha account on any plan, including Free, which has a key of its own and a smaller rate limit
- API access still on for you. An admin or manager can turn it off under Account Settings, Permissions
- Credits on the account, because searches and reveals spend them

## Get your credentials

### 1. Sign in to Lusha

Sign in at dashboard.lusha.com with your own account. A key acts as the person who owns it, so use the login you want your AI to work as.

Screen: https://dashboard.lusha.com

### 2. Copy your API key

Open API & connectors in the left sidebar and click Copy API key at the top right. Every user has a key already, so there is nothing to create.

Screen: https://dashboard.lusha.com/api/manage-api-keys

### 3. Paste the key into PopMCP

In PopMCP, open the Lusha connector and paste the value into API key. To use Lusha tables without being asked for your email, open More options and fill in Your Lusha email. Click Connect.

## Fields PopMCP asks for

- API key (apiKey) [required]: In Lusha, open API & connectors, then click Copy API key.
- Your Lusha email (ownerEmail): The email you sign in to Lusha with. Lusha asks for it when your AI works with tables.

## Verify

PopMCP marks the Lusha connector Connected, shows your plan and how many credits you have left. Checking the balance is free. Try asking your AI how many Lusha credits are left.

## Troubleshooting

### Lusha did not accept this API key

Cause: The key was not copied whole, or it was regenerated after you copied it. A malformed key is answered with 400 Invalid API key format.

Fix: Click Copy API key again in API & connectors and paste it without extra text.

### Lusha knows this key but will not let it in

Cause: The account is inactive, or an admin or manager turned off your API access, which suspends your key.

Fix: Ask an admin to turn your access back on under Account Settings, Permissions. The same key starts working again.

### Lusha allows this check 5 times a minute

Cause: The usage call PopMCP connects with is limited to 5 calls a minute.

Fix: Wait a minute and click Connect again.

### 402 on a search or a reveal

Cause: The account is out of credits, or the key or user has reached a monthly credit limit.

Fix: Check the balance in Lusha, then add credits or ask an admin to raise the limit.

### 429 Too Many Requests

Cause: Your plan's rate limit was reached. Free and Starter allow 40 requests a minute and 100 a day.

Fix: Wait and try again. If the daily limit is used up, it resets the next day, or a higher plan raises it.

### 403 on recommendations only

Cause: The connected key is account-wide. Lusha gives recommendations only to a key owned by a team member.

Fix: Reconnect with a key you generated for yourself.

### A table tool asks for ownerEmail

Cause: Lusha requires the email of a user on the account on every table call, and none was given at connect.

Fix: Reconnect and fill in Your Lusha email under More options, or tell your AI which email to use.

### Website visitors answers 400

Cause: One of the domains is not set up for tracking in Lusha, which fails the whole request, or the date range is longer than 3 months.

Fix: Set the domain up for tracking in the Lusha dashboard and keep the range to 3 months or less.

---

Source: https://www.docs.popmcp.com/docs/integrations/lusha/