POST /api/green_japan/jobs
Price: 10 credits
Get one job on Green (green-japan.com): the full posting with overview, duties, requirements, hiring background and process, openings, employment type, salary range and details, locations, address, working hours, holidays, benefits, skills, features and job types, the hiring company's profile and its listed jobs. Closed postings are returned with status closed.
Find job ids with green_japan/jobs/search or green_japan/companies/jobs; green_japan/jobs/similar lists related jobs.
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: "324628", "https://www.green-japan.com/company/10550/job/324628")@type string (default: "GreenJapanJob")salary_min number nullablesalary_max number nullablesalary_currency string nullableid string requiredurl string requiredname string nullablestatus string nullableoverview string nullabletext string nullablehiring_background string nullablerequirements string nullablecareer_gains string nullablehiring_process string nullableopenings string nullabledepartment string nullableemployment_type string nullablesalary_details string nullablelocations array (default: [])location_ids array (default: [])address string nullableaccess string nullablework_start_time string nullablework_end_time string nullableholidays string nullablebenefits string nullableskills array (default: [])skill_ids array (default: [])features array (default: [])feature_ids array (default: [])job_types array (default: [])@type string (default: "GreenJapanJobType")id string requiredname string requiredcategory_id string nullablecategory_name string nullablesections array (default: [])@type string (default: "GreenJapanJobSection")id string nullabletext string requiredimages array (default: [])business object nullable@type string (default: "GreenJapanBusiness")name string nullabledescription string nullableimage string nullableupdated_at integer nullablerenewed_at integer nullablewelcome_comment object nullable@type string (default: "GreenJapanWelcomeComment")author_name string nullabletext string requiredimage string nullablecompany object nullable@type string (default: "GreenJapanCompanyProfile")id string requiredurl string requiredname string nullabledescription string nullablehighlights array (default: [])address string nullablepresident_name string nullablefounded_date integer nullableemployee_count integer nullableaverage_age number nullablecapital string nullablerevenues array (default: [])@type string (default: "GreenJapanRevenue")year integer requiredmonth integer nullableamount number nullableamount_text string requiredstock_market string nullablestock_market_id string nullableshareholders string nullablemain_customers string nullableindustries array (default: [])@type string (default: "GreenJapanIndustryRef")id string requiredname string requiredcategory_id string nullablecategory_name string nullablefeatures array (default: [])feature_ids array (default: [])premium_interviews array (default: [])@type string (default: "GreenJapanPremiumInterview")id string requireddirectory_name string nullableimage string nullablecover string nullableimages array (default: [])company_jobs array (default: [])@type string (default: "GreenJapanCompanyJob")salary_min number nullablesalary_max number nullablesalary_currency string nullableid string requiredurl string requiredcompany_id string requiredname string nullablelocations array (default: [])job_types array (default: [])@type string (default: "GreenJapanJobType")id string requiredname string requiredcategory_id string nullablecategory_name string nullableimage string nullableis_remote boolean nullableis_inexperienced_welcome boolean nullable422 — 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 job 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.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.