/wttj/companies/search

POST /api/wttj/companies/search

Price: 10 credits

Search Welcome to the Jungle companies by name or keyword, optionally filtered by sector, office country or a geo radius. Each result includes the company name, summary, logo and cover, sectors, tech stack, employee count, open-job count, labels, offices with coordinates and the public profile URL.

How to use it

Search Welcome to the Jungle companies. Pass query and count; optionally filter by sector, country_code or a latitude/longitude/radius geo search. Each item has name, summary, image, sectors, tools, employee_count, job_count, offices and url.

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 or tech-stack query (default: ""; examples: "fintech")
• count integer required — Max number of companies to return (min: 1)
• language string — Result localization language (default: "en"; one of: "cs", "en", "es", "fr", "sk")
• sector string nullable — Parent industry/sector filter (one of: "Tech", "Banking / Insurance / Finance", "Consulting / Audit", "Health / Social / Environment", "Advertising / Marketing / Agency", "Culture / Media / Entertainment", "Education / Training / Recruitment", "Industry", "Distribution", "Food and Beverage", "Fashion / Luxury / Beauty / Lifestyle", "Real Estate", "Mobility / Transport", "Corporate Services", "Hotel / Tourism / Leisure", "Engineering", "Nonprofit / Association", "Architecture", "Legal / Law", "Public Administration")
• country_code string nullable — Office country ISO alpha-2 code filter, e.g. FR (examples: "FR")
• latitude number nullable — Latitude for geo radius search (min: -90; max: 90)
• longitude number nullable — Longitude for geo radius search (min: -180; max: 180)
• radius integer nullable — Geo search radius in meters (min: 1)

Response

• @type string (default: "WttjCompanySearchHit")
• name string nullable
• alias string nullable
• reference string nullable
• summary string nullable
• image string nullable
• cover string nullable
• sectors array (default: [])
  • @type string (default: "WttjSectorEntity")
  • name string nullable
  • reference string nullable
  • parent_name string nullable
  • parent_reference string nullable
• tools array (default: [])
• employee_count integer nullable
• size string nullable
• job_count integer nullable
• labels array (default: [])
• offices array (default: [])
  • @type string (default: "WttjOffice")
  • address string nullable
  • city string nullable
  • state string nullable
  • district string nullable
  • zip_code string nullable
  • country string nullable
  • country_code string nullable
  • latitude number nullable
  • longitude number nullable
  • is_headquarter boolean nullable
• url 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 — No matching companies 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.