Skip to main content
The Company Profiles API consists of two endpoints: one to check the available profile count for a company, and one to retrieve those profiles via an async callback. This is particularly useful when needing to fetch all employees of a specific company by its exact ID or slug — unlike the Search API which filters by company name (a non-unique string), this endpoint works with the unique LinkedIn company ID or slug from Find Company.

Get Profile Count

Check how many profiles are associated with a company by employment status — no credits consumed. Endpoint: GET https://www.signalhire.com/api/v1/company/getCount
string
required
Secret API key.
string
required
Company ID (numeric) or company slug.
string
required
Employment status filter. Possible values: current, past, both.

Request Example

Response Example (HTTP 200)

integer
Total number of profiles matching the status filter.

Get Profiles

Fetch employee profiles for a company asynchronously via callback. Endpoint: GET https://www.signalhire.com/api/v1/company/getProfiles
string
required
Secret API key.
string
required
Company ID (numeric) or company slug.
string
required
Employment status filter. Possible values: current, past, both.
string
required
URL where results will be POSTed once processing is complete. Same callback format and delivery rules as Person API callbacks.

How It Works

  1. The request returns a searchId immediately with HTTP 200
  2. Profiles are delivered to the callbackUrl in batches of up to 100 profiles per callback
  3. Each profile delivered counts as one view against your daily profile-view quota — the same quota shared with the SignalHire website. The quota varies by plan, up to 2000 profiles/day; if the company has more profiles than your remaining quota, the request is rejected with HTTP 429 — contact support@signalhire.com if a higher limit is needed.
  4. Profiles are returned without contact details (no emails or phone numbers) To subsequently retrieve contact details for specific profiles, pass their uid values to the Person API, which consumes standard credits.

Request Example

Response Example (HTTP 200)

Results are delivered to the callbackUrl as an array of profile objects without contact details.

Response Codes