/cutshort/companies/jobs

POST /api/cutshort/companies/jobs

Price: 10 credits

List the open jobs of a Cutshort company by alias, id or URL: title, description, locations, remote policy, skills, experience and salary range, recruiter and posting date

How to use it

Company aliases come from cutshort/jobs/search and cutshort/companies/search. A returned id works with cutshort/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 — Cutshort company alias, id or company URL (examples: "metadomeai-19-1XL4kYPm", "64784e08d856360027692066", "https://cutshort.io/company/ekloud-inc-67-ISfPFEWf"; minLength: 1)
• count integer required — Max number of results (min: 1)

Response

• @type string (default: "CutshortJob")
• id string required
• short_id string nullable
• url string nullable
• description string nullable
• company object nullable
  • @type string (default: "CutshortJobCompany")
  • id string nullable
  • alias string nullable
  • name string nullable
  • url string nullable
  • image string nullable
  • founded_year integer nullable
  • type string nullable
  • size string nullable
  • stage string nullable
  • followers_count integer nullable
  • is_recruitment_agency boolean nullable
  • description string nullable
  • links array (default: [])
    • @type string (default: "CutshortLink")
    • name string nullable
    • url string nullable
• recruiter object nullable
  • @type string (default: "CutshortPerson")
  • id string nullable
  • name string nullable
  • headline string nullable
  • image string nullable
  • linkedin_url string nullable
• is_hiring_for_client boolean nullable
• client_description string nullable
• locations array (default: [])
• remote_type string nullable
• employment_types array (default: [])
• skills array (default: [])
• category string nullable
• category_tags array (default: [])
• experience_min_years number nullable
• experience_max_years number nullable
• experience_text string nullable
• salary_currency string nullable
• salary_min number nullable
• salary_max number nullable
• salary_text string nullable
• is_salary_hidden boolean nullable
• posted_at integer nullable
• is_active 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 — Cutshort has no company under that alias or 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.