Skip to main content
The REST API lets your scripts and automation tools do what your AI assistant does through the MCP.

​
The basics

A complete call looks like this:
When you have nothing to set, send {}.

​
Before you press Send

There is no test mode. The Try it button on each page calls the real API with your key.
Each page starts with what the call really does:
  • Blue (Info): safe to try.
  • Yellow (Warning): changes nothing, but uses a limited LinkedIn action, or cannot be undone.
  • Red (Danger): changes something real, on LinkedIn or in your CRM.
Your requests go straight from your browser to Groovin. Use a separate key for your experiments, and revoke it afterwards. Code examples show values such as REPLACE_WITH_CONVERSATION_ID: replace each of them before running the code.

​
All the routes

See What each call really does for the full list, with the effect of each one.

​
Calling a route by its name

Each route also has a name, which is the name of its MCP tool. You can call any route through a single address, which is handy when your tool already knows the MCP names:
action is the tool name, and params holds the same fields as the route. It does exactly the same thing as the route, with the same effects.

​
Calling from a web page

The API accepts calls from a browser. Do not put your API key in a public page, though: anyone can read it there. Call the API from a server or an automation tool.