/jobtalk/reviews

POST /api/jobtalk/reviews

Price: 1 credit

Get one employee review from Jobtalk (転職会議) with its full text, rating, category and reviewer profile, plus the same reviewer's answers in the other categories

How to use it

Review ids and URLs come from jobtalk/companies/reviews and jobtalk/companies/interviews.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• review string required — Jobtalk review URL or review id (examples: "https://jobtalk.jp/companies/2513/answers/9070254", "9070254"; minLength: 1)
• company string nullable — Jobtalk company id or company URL the review belongs to; required with a bare review id (examples: "2513"; minLength: 1)

Response

• @type string (default: "JobtalkReview")
• id string required
• url string required
• company_id string required
• member_id string nullable
• category string nullable
• category_name string nullable
• rating number nullable
• text string nullable
• posted_at integer nullable
• reviewer_id string nullable
• reviewer_gender string nullable
• reviewer_age integer nullable
• reviewer_job_type string nullable
• reviewer_position string nullable
• reviewer_employment_type string nullable
• reviewer_relationship string nullable
• reviewer_relationship_name string nullable
• reviewer_annual_salary number nullable
• experienced_at integer nullable
• interview object nullable
  • @type string (default: "JobtalkInterview")
  • recruitment_type string nullable
  • interviewed_at integer nullable
  • stage string nullable
  • result string nullable
  • method string nullable
  • declined_reasons array (default: [])
• president_name string nullable
• company_response string nullable
• company_response_at integer nullable
• inspection_reason string nullable
• other_reviews array (default: [])

Errors

• 422 — review is not a Jobtalk review URL or id, or a bare id came 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 review under that id for that company 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.