Skip to main content
Groovin needs to know which account is calling. There are two ways, depending on what you use:

​
API keys

An API key is a long secret that starts with gv_live_. It acts as you: anyone who has it can do everything your Groovin account can do, including sending LinkedIn messages.

​
Create a key

  1. Open the Groovin extension, then Settings → MCP and API.
  2. Give the key a name that says what it is for, such as n8n or Experiments.
  3. Click Create key.
  4. Copy the key now: it is shown only once.
Keys do not expire: they work until you revoke them. Create one key per tool, so you can revoke one without touching the others.

​
Use a key

Send it in the Authorization header of every request:

​
Keep it safe

  • Keep it in an environment variable or your tool’s secret manager.
  • Do not paste it into a chat with an AI assistant, or commit it to Git.
  • Do not put it in a web page: anyone can read a page’s code.

​
Revoke a key

In Settings → MCP and API, click Revoke next to the key. It stops working immediately, for any tool using it. If you think a key leaked, do this first.

​
What your account needs

Even with a valid key, a call is refused if your account is not ready:
The Billing admin role is a free seat that manages billing and the team. It cannot use the API or the MCP, and cannot create API keys. To use them, ask an org admin to change your role to Member in Settings → Team.

​
Whose LinkedIn account is used

Your key always acts as you, on your own LinkedIn account. Most routes accept an org_linkedin_account_id, but you can only use your own: a teammate’s account is refused with a 403. You can simply leave it out. There is one exception: Check who is already in your CRM can check against any LinkedIn account of your organization.