/linkedin/search/companies

POST /api/linkedin/search/companies

Price: 1 credit

Linkedin Search Companies

How to use it

Search companies by keywords and filters. Returns company profiles with URNs. Results include LinkedIn showcase pages (url contains /showcase/), which are real organizations with their own company URN.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• keywords string — Any keyword for searching in the company page. For exact search put desired keywords into brackets (default: ""; examples: "microsoft")
• location union — Location URN, can be obtained in /linkedin/search/locations, only geo urn type is allowed. Or location name. (default: []; examples: ["geo:103689695"])
  • type string required (one of: "geo")
  • value string required
• industry union — Industry URN or name. Valid top-level industries: Technology, Information and Media; Professional Services; Manufacturing; Hospitals and Health Care; Retail; Government Administration; Holding Companies; Oil, Gas, and Mining; Real Estate and Equipment Rental Services; Transportation, Logistics, Supply Chain and Storage; Utilities; Wholesale. Text auto-resolves to URN. (default: []; examples: ["industry:96"])
  • type string required (one of: "industry")
  • value string required
• employee_count array — Employee count (default: []; one of: "1-10", "11-50", "51-200", "201-500", "501-1000", "1001-5000", "5001-10000", "10001+"; examples: ["1-10\", \"5001-10000\""])
• count integer required — Max result count (max: 900; >: 0)

Response

• @type string (default: "LinkedinSearchCompany")
• urn object required
  • type string required (one of: "fsd_company", "fsd_group", "fsd_profile", "fsd_skill", "activity", "comment", "company", "group", "geo", "pulse", "member", "industry", "ugcPost", "job", "message", "conversation", "media", "share", "linkedInArticle")
  • value string required
• name string required
• url string required
• alias string required
• image string nullable
• industry string nullable
• location string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.