/tracxn/companies/search

POST /api/tracxn/companies/search

Price: 10 credits

List the companies of a Tracxn (tracxn.com) explore list — one sector in one geography

How to use it

List the companies Tracxn features for one sector in one geography, addressed by the explore list URL or list id. Each entry carries the company name and profile id to pass to /tracxn/companies, its logo, description, founding year, city and country, current stage, total funding, the latest funding round with its type and date, known investors, the Tracxn score, the rank among its competitors and its rank inside the list. Tracxn publishes only a short curated slice of each list to guests.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• explore string required — Tracxn explore list URL (a sector-in-a-geography startup list under tracxn.com/d/explore), or the list id that follows '__' in that URL (examples: "https://tracxn.com/d/explore/auto-tech-startups-in-india/__hVMq_SvfouSavYtGTT238hkb4bpf6AxJKMZXgXripxA", "hVMq_SvfouSavYtGTT238hkb4bpf6AxJKMZXgXripxA"; pattern: ^[A-Za-z0-9_:/.?=&%+-]{6,400}$)
• count integer required — Max number of results (min: 1)

Response

• @type string (default: "TracxnCompanyCard")
• name string required
• id string nullable
• url string nullable
• image string nullable
• rank integer nullable
• description string nullable
• unicorn_note string nullable
• founded_year integer nullable
• city string nullable
• country object nullable
  • @type string (default: "TracxnEntityRef")
  • name string required
  • id string nullable
  • namespace string nullable
  • url string nullable
• primary_sector string nullable
• highlight string nullable
• time_to_unicorn string nullable
• stage string nullable
• total_funding number nullable
• latest_round object nullable
  • @type string (default: "TracxnLatestRound")
  • round_name string nullable
  • funded_at integer nullable
  • amount number nullable
• investors array (default: [])
  • @type string (default: "TracxnEntityRef")
  • name string required
  • id string nullable
  • namespace string nullable
  • url string nullable
• annual_revenue string nullable
• employee_count integer nullable
• tracxn_score integer nullable
• competitor_rank integer nullable
• competitor_count integer 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 — Explore list not found, or the id belongs to a different entity type. 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.