Skip to main content
POST
Find missing LinkedIn URLs
This writes to your real CRM and spends one credit per URL found, out of 500 a month. It can read LinkedIn live through your account. It only fills empty fields and never overwrites a URL.

What this call does

Good to know

  • not_found or ambiguous with an error means the search could not run in full. It does not prove the person is not on LinkedIn.
  • This route can run for more than a minute. A failure shown by your tool does not prove the batch stopped: check your contacts before running it again.
Your AI assistant reaches the same action through the MCP tool find_linkedin_profile_url.

Authorizations

Authorization
string
header
required

Your Groovin API key (gv_live_…), created in the extension under Settings, MCP and API.

Body

application/json
crm_contact_ids
string[]
required

The CRM contacts, up to 25 per call, as text. 5 to 10 is the practical size.

Required array length: 1 - 25 elements

Response

Success.

The result of a batch. The batch can stop early: send what is in not_processed again.

total
integer
required

Contacts asked for, without duplicates.

processed
integer
required

Contacts actually searched.

found
integer
required

URLs found.

failed
integer
required

Searches that failed.

not_processed
string[]
required

Contacts this call did not search. Nothing was spent for them. Send only these again, never the whole list.

not_processed_reason
enum<string> | null
required

Why the batch stopped early. upstream_blocked usually means your CRM must be reconnected.

Available options:
time_budget_exhausted,
credits_exhausted,
upstream_blocked,
null
remaining_credits
integer
required

Your finder credits after this call.

retry_guidance
string | null
required

Plain-text advice when some items failed for a temporary reason, otherwise null. Follow it: it says when to retry, and which items.

results
object[]
required

One item per contact searched.