Skip to main content
REST failures use an HTTP status and a JSON error object, for example:
People-search errors include people_search_timeout, people_search_incomplete and people_search_unavailable. Job-search errors include jobs_search_timeout, jobs_search_incomplete and jobs_search_unavailable. They contain no partial results, deduct no credits and must not be interpreted as an empty successful search. The hosted MCP tools preserve these codes. Search latency remains variable; a narrower query is guidance, not a guarantee of success. jobs_credit_plan_required means job search needs an active credit allowance. tech_credit_plan_required means a website technology lookup needs an active credit allowance. Technology failures include tech_stack_timeout, tech_stack_unavailable, tech_sites_timeout, tech_sites_unavailable, tech_catalog_timeout and tech_catalog_unavailable. They deduct no credits and are not an empty successful page. missing_reference means a company profile has no LinkedIn organization ID to associate with postings.

Safe retries

Use a small, bounded number of retries with increasing delays for temporary failures. For lookups, keep the same idempotency key and unchanged request input. A transport timeout is not evidence that no credit was deducted. Do not keep retrying invalid input or an unavailable allowance. Company lookup accepts exactly one returned company_id or bare website domain. Person lookup accepts exactly one returned person_id or public HTTPS LinkedIn /in/ URL without query parameters or a fragment. People search needs query or company; optional country codes use two uppercase letters.

MCP failures

Tools can return an MCP error result with a structured error in the text content. Inspect the error code instead of treating the message as profile data. account_not_ready means you need to sign in to the dashboard first. A disconnected or expired authorization cannot be used for data requests.

Get help

Use Support in the dashboard. Include the endpoint or tool name, approximate time, request ID if available, and redacted error code. Never include API keys, tokens or person payloads. Replies currently appear in the dashboard; email notifications link back to the reply. Credit errors include credit_budget_exceeded (maximum above your cap, no data lookup), credits_unavailable (maximum cannot be reserved), request_in_progress (retry the same key), identity_mismatch (review canonical references), and saved_result_deleted (410; a new key may incur a new charge). Unused reservations are released; a timeout alone does not prove no committed charge.