POST /api/baitoru/companies/jobs
Price: 1 credit
List an employer's open part-time and casual job postings on baitoru (バイトル): title, store, employment types, location, occupation, pay, hours, interview place, application methods and application barometer; the job number, happy bonus, hiring count, application note and feature tags are not part of the answer
Company ids come from company_id on baitoru/jobs. Pass a returned id to baitoru/jobs for the full posting.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)company string required — baitoru company id or company page URL (examples: "25189", "https://www.baitoru.com/cjlist25189/"; minLength: 1)count integer required — Max number of results (min: 1; max: 2000)@type string (default: "BaitoruCompanyJob")id string requiredurl string requiredtitle string nullablecompany_id string requiredcompany_name string nullablestore_name string nullableemployment_types array (default: [])has_video boolean nullablehappy_bonus string nullablelocation string nullablejob_types string nullablesalary string nullablework_time string nullablefeatures array (default: [])application_level integer nullableapplication_note string nullablehiring_count string nullablejob_number string nullablesalaries array (default: [])@type string (default: "BaitoruSalary")pay_basis string nullablemin_amount integer nullablemax_amount integer nullableimage string nullableinterview_location string nullableis_interview_same_as_work boolean nullablework_place string nullablecan_apply_on_web boolean nullablecan_apply_by_phone boolean nullablephone_number string nullableexpires_at integer nullableis_new boolean nullableis_outsourcing boolean nullableis_baitoru_next boolean nullablecan_bulk_apply boolean nullableis_external_application boolean nullableexternal_application_url string nullablereception_hours string nullablereception_note string nullablesnippet string nullable422 — company is not a baitoru company id or URL 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 baitoru company page 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.