/findy/companies

POST /api/findy/companies

Price: 1 credit

Get one company on Findy (findy-code.io): description, address, founding date, representative, website, headcount, mission and vision, products, press releases, engineering team members, tech stack, GitHub repositories and tech blog entries.

How to use it

Find company ids with findy/companies/search; findy/companies/jobs lists the company's open jobs.

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 id or URL (examples: "860", "https://findy-code.io/companies/860"; minLength: 1)

Response

• @type string (default: "FindyCompany")
• id string required
• url string required
• name string nullable
• image string nullable
• description string nullable
• address string nullable
• founded_date integer nullable
• representative string nullable
• website string nullable
• employee_count integer nullable
• corporation_id string nullable
• mission_title string nullable
• mission string nullable
• vision_title string nullable
• vision string nullable
• images array (default: [])
  • @type string (default: "FindyImage")
  • id string nullable
  • url string required
  • filename string nullable
• products array (default: [])
  • @type string (default: "FindyProduct")
  • id string nullable
  • name string required
  • url string nullable
  • description string nullable
  • image string nullable
• press_releases array (default: [])
  • @type string (default: "FindyPressRelease")
  • id string nullable
  • url string nullable
  • published_at integer nullable
• links array (default: [])
  • @type string (default: "FindyLink")
  • name string nullable
  • url string required
• members array (default: [])
  • @type string (default: "FindyMember")
  • id string nullable
  • name string required
  • position string nullable
  • github_account string nullable
  • introduction string nullable
• tech_stack array (default: [])
  • @type string (default: "FindyTechSkill")
  • id string required
  • name string required
  • category string nullable
• github_account string nullable
• github_member_count integer nullable
• github_repositories array (default: [])
  • @type string (default: "FindyRepository")
  • id string nullable
  • name string required
  • url string required
  • description string nullable
  • language string nullable
  • star_count integer nullable
  • fork_count integer nullable
• tech_blog_url string nullable
• tech_blog_entries array (default: [])
  • @type string (default: "FindyBlogEntry")
  • id string nullable
  • url string nullable
  • published_at integer nullable
  • skills array (default: [])
    • @type string (default: "FindyNamed")
    • id string required
    • name string required

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 company under that id 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.