/inhersight/companies/search

POST /api/inhersight/companies/search

Price: 1 credit

Search or browse InHerSight (inhersight.com) employer profiles by keyword, industry and size

How to use it

Find InHerSight (inhersight.com) employers. Provide a company name keyword to search by name, or omit the keyword and browse the directory filtered by industry and size with a chosen ordering. Returns companies with alias, name, InHerSight composite score, industry, headquarters and rating/review counts. Use the returned alias or id to fetch the full profile via /inhersight/companies.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• query string — Company name keyword. When set, browse filters are ignored. (default: ""; examples: "google")
• industry string nullable — Filter companies by industry (one of: "agriculture", "art", "consumer_goods", "construction", "corporate", "education", "finance", "government", "health", "legal", "manufacturing", "media", "organization", "recreation", "service", "technology", "transportation")
• size string nullable — Filter companies by size (small/medium/large) (one of: "small", "medium", "large")
• order_by string — Result ordering for browse mode (default: "recommended"; one of: "recommended", "top_rated")
• count integer required — Max number of results to return (min: 1)

Response

• @type string (default: "InhersightSearchCompany")
• id integer required
• alias string required
• name string required
• url string required
• image string nullable
• composite_score number nullable
• industry string nullable
• industry_group string nullable
• headquarters string nullable
• employee_range string nullable
• size string nullable
• review_count integer nullable
• rating_count integer nullable
• job_count integer nullable
• is_top_company boolean 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.