/townwork/companies/jobs

POST /api/townwork/companies/jobs

Price: 10 credits

List an employer's job postings on townwork (タウンワーク): title, store, pay text and structured pay, access, photo, employment types, new and ended flags and publish date

How to use it

Company ids come from company_id on townwork/jobs. Pass a returned id to townwork/jobs for the full posting.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• company string required — townwork company id or company page URL (examples: "1199776127", "https://townwork.net/company/1199776127/"; minLength: 1)
• count integer required — Max number of results (min: 1; max: 2000)

Response

• @type string (default: "TownworkCompanyJob")
• id string required
• url string required
• company_id string required
• store_name string nullable
• salary string nullable
• base_pay object nullable
  • @type string (default: "TownworkPay")
  • min number nullable
  • max number nullable
  • unit string nullable
  • currency string nullable
  • task_minutes integer nullable
• task_pay object nullable
  • @type string (default: "TownworkPay")
  • min number nullable
  • max number nullable
  • unit string nullable
  • currency string nullable
  • task_minutes integer nullable
• access string nullable
• image string nullable
• employment_types array (default: [])
• is_new boolean nullable
• is_expired boolean nullable
• published_at integer nullable

Errors

• 422 — company is not a townwork 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 townwork 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.

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.