Errors

Quick fixes

Status	What it means	What to do
`400`	Something in your request is wrong	Read `error`, fix the request
`401`	The API key is missing, wrong or revoked	Check the `Authorization` header
`402`	You have no LinkedIn URL credits left	See Credits
`403`	Your account cannot do this	See What your account needs
`404`	It does not exist, LinkedIn is not connected, or the CRM contact has no LinkedIn URL	Check the id. Reconnect LinkedIn in Groovin. Add the URL in your CRM
`405`	You did not use `POST`	Every route uses `POST`, even the ones that read
`409`	Something is already running	Wait for it to finish
`410`	The import’s data was deleted	Start a new import
`422`	The CRM contact’s LinkedIn URL cannot be used	Fix the URL in your CRM
`429`	LinkedIn or your CRM is slowing you down	Stop. Wait at least 5 minutes.
`500`	Something failed on our side	Retry later. If it continues, contact support
`502`	LinkedIn or your CRM could not be reached	Retry later
`504`	No answer in time	On a send, check first. See below

This list can grow: some statuses come straight from LinkedIn. A 401 or 403 can also be LinkedIn’s answer, in which case error mentions LinkedIn.

A send failed

After an error on a send, the message or invitation may already be gone. Never retry automatically.

If linkedin/messages or linkedin/invitations answers a 5xx, a 429, or no answer at all (a network error, or a timeout in your tool):

Wait a few minutes. Groovin’s copy of your inbox can lag behind LinkedIn.
Check. Read the conversation with linkedin/chat-messages. If you sent by profile and have no conversation_id, find it in the conversation list. For an invitation, check the pending invitations.
Only if it is still not there, try again, once.

In a browser, a gateway timeout can show up as a network error rather than a 504. Treat it the same way.

What an error looks like

Every failure answers with an HTTP status and one field:

{ "error": "Too many crm_contact_ids: max 25 per enable request (got 40). Split into smaller batches." }

There are no error codes, and the text can change. In your code, decide what to do from the HTTP status. Show the text to a person, or give it to your AI assistant.

On a 429 or a 5xx, the text ends with advice on what to do next. On a send, that advice is to check before re-sending.

That advice can say “Re-sending is safe” when it is not. On a connections import, a domain lookup or a profile read, follow the page of that route instead.

An HTTP 200 can hold failures

Routes that handle several items answer 200 even when some items failed. Always check each item:

{
  "total": 2,
  "succeeded": 1,
  "failed": 1,
  "results": [
    { "linkedin_profile_id": "ACoAA…", "crm_contact_id": "…", "error": null, "error_status": null },
    { "linkedin_profile_id": "ACoAA…", "crm_contact_id": null, "error": "…", "error_status": 429 }
  ],
  "retry_guidance": "…"
}

Field	How to use it
`error`	What went wrong for this item
`error_status`	`429` or `5xx` means temporary. Anything else needs a fix
`retry_guidance`	When to retry, and which items
`not_processed`	Items the call did not reach. Send only these again

This applies to crm/contacts, crm/contacts/sync-toggle, crm/contacts/find-linkedin-url and crm/companies/find-domains.

When is it safe to retry?

Situation	Retry?
`400`, `401`, `403`, `404`	No. Fix the cause first
`429`	Yes, after at least 5 minutes. If the text mentions a monthly limit, wait for the reset
`5xx` on a read	Yes, after a pause. Live LinkedIn reads spend your allowance again
`5xx` on a batch	Yes, only the failed items
Any failure on a send	Not before checking. See A send failed

Each page says what repeating that call does, and What each call really does lists them all. There are no idempotency keys: Groovin cannot recognize a repeated request on your behalf.

On the MCP

Your AI assistant gets these same messages, but as a tool result rather than an HTTP status. See MCP errors.

Get started

Safety and limits

REST API

MCP

Webhooks

Help

Quick fixes

A send failed

What an error looks like

An HTTP 200 can hold failures

When is it safe to retry?

On the MCP

​Quick fixes

​A send failed

​What an error looks like

​An HTTP 200 can hold failures

​When is it safe to retry?

​On the MCP

Quick fixes

A send failed

What an error looks like

An HTTP 200 can hold failures

When is it safe to retry?

On the MCP