POST /api/findy/jobs
Price: 5 credits
Get one job on Findy (findy-code.io): the full posting with description, rewarding points, ideal candidate, development environment, required and preferred skills, salary range with base pay and examples, bonus, working hours, location, holidays, benefits, hiring process, job roles, skills and features, and the hiring company with its AI usage and published articles.
Find jobs with findy/jobs/search or findy/companies/jobs; pass a result's url, or its id with company.id. findy/companies has the full company profile.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)job string required — Job id or URL (examples: "https://findy-code.io/companies/860/jobs/ojzZi_KaNOqIM", "ojzZi_KaNOqIM"; minLength: 1)company string nullable — Company id of the job, needed with a bare job id (examples: "860")@type string (default: "FindyJob")salary_min number nullablesalary_max number nullablesalary_currency string nullableid string requirednumeric_id integer nullableurl string requiredis_public boolean nullabledescription string nullablerewarding string nullableideal_candidate string nullabledevelopment_environment string nullablerequired_skills string nullablepreferred_skills string nullableemployment_type string nullablesalary_text string nullablebase_salary_min number nullablebase_salary_max number nullablebase_salary_period string nullablesalary_examples string nullablesalary_notes string nullablebonus string nullabletrial_period string nullablework_hours string nullablebreak_time string nullableovertime string nullablelocation string nullableholidays string nullableinsurance string nullablebenefits string nullableother_benefits string nullablecareer_programs string nullablehealth string nullablesmoking_policy string nullablehiring_process string nullableother_notes string nullableslide_deck_url string nullablejob_roles array (default: [])@type string (default: "FindyJobRole-Output")id string requiredname string requiredcategory_id string nullableis_management boolean nullableskills array (default: [])@type string (default: "FindyNamed")id string requiredname string requiredfeatures array (default: [])@type string (default: "FindyNamed")id string requiredname string requiredpersonality_tags array (default: [])@type string (default: "FindyNamed")id string requiredname string requiredcreated_at integer nullablepublished_at integer nullableupdated_at integer nullableimage string nullablecompany object required@type string (default: "FindyJobCompany")id string requiredurl string requiredname string nullableimage string nullableteam_plus_award string nullableaddress string nullablewebsite string nullablecorporation_id string nullableimages array (default: [])@type string (default: "FindyImage")id string nullableurl string requiredfilename string nullableai_usage object nullable@type string (default: "FindyAiUsage")is_using_ai boolean nullablecomment string nullableusage_types array (default: [])tools array (default: [])@type string (default: "FindyAiTool")id string requiredname string requiredupdated_at integer nullableinterviews array (default: [])@type string (default: "FindyArticle")id string nullableurl string nullabledescription string nullableimage string nullablepublished_at integer nullablefeature_articles array (default: [])@type string (default: "FindyArticle")id string nullableurl string nullabledescription string nullableimage string nullablepublished_at integer nullabletools_articles array (default: [])@type string (default: "FindyArticle")id string nullableurl string nullabledescription string nullableimage string nullablepublished_at integer nullable422 — A bare job id without company 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 job under that company and job 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.