/tracxn/companies/funding

POST /api/tracxn/companies/funding

Price: 10 credits

Get the full Tracxn (tracxn.com) funding history and investor list of a company

How to use it

Get the complete funding history of a Tracxn company: every disclosed round with date, amount, round name, post-money valuation, revenue multiple, lead investors and other investors, plus the institutional investor roster with each investor's location, first investment date and the round they entered in, and the split between institutional and angel investors.

Call these first: /tracxn/companies

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• company string required — Company profile URL on tracxn.com, or the profile id that follows '__' in that URL (examples: "https://tracxn.com/d/companies/bigbasket/__lgBEzK2HajAJWbmAO0CnrQYnIPr1qailEUYRD4zGXVU", "lgBEzK2HajAJWbmAO0CnrQYnIPr1qailEUYRD4zGXVU"; pattern: ^[A-Za-z0-9_:/.?=&%+-]{6,400}$)

Response

• @type string (default: "TracxnCompanyFunding")
• id string required
• alias string nullable
• url string required
• name string required
• investor_count integer nullable
• institutional_investor_count integer nullable
• angel_investor_count integer nullable
• funding_rounds array (default: [])
  • @type string (default: "TracxnFundingRound")
  • funded_at integer nullable
  • amount number nullable
  • round_name string nullable
  • post_money_valuation number nullable
  • revenue_multiple string nullable
  • lead_investors array (default: [])
    • @type string (default: "TracxnEntityRef")
    • name string required
    • id string nullable
    • namespace string nullable
    • url string nullable
  • other_investors array (default: [])
    • @type string (default: "TracxnEntityRef")
    • name string required
    • id string nullable
    • namespace string nullable
    • url string nullable
• investors array (default: [])
  • @type string (default: "TracxnCompanyInvestor")
  • name string required
  • id string nullable
  • namespace string nullable
  • url string nullable
  • location string nullable
  • first_investment_at integer nullable
  • first_investment_round string nullable
• faqs array (default: [])
  • @type string (default: "TracxnFaq")
  • question string required
  • answer 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 — Company not found, or the id belongs to a different entity type (investor, person, sector). 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.