/jobtalk/companies/salaries

POST /api/jobtalk/companies/salaries

Price: 5 credits

Get individual salary reports for a Japanese company on Jobtalk (転職会議), newest first: annual salary in yen, the year it applies to, and the employee's age, gender, job type, position and employment type

How to use it

Company-wide salary averages, salary by age and by occupation are on jobtalk/companies. Find the company id with jobtalk/companies/search.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• company string required — Jobtalk company id or company URL (examples: "2513", "https://jobtalk.jp/companies/2513"; minLength: 1)
• employment_types array nullable — Employment type of the reporting employee (one of: "fullTime", "contract", "temporary", "partTime", "nonFullTime", "outsourcing", "intern", "other"; examples: ["fullTime"])
• gender string nullable — Gender of the reporting employee (one of: "male", "female")
• job_types array nullable — Job type of the reporting employee, as it appears in job_type (examples: ["法人営業"])
• count integer required — Max number of results (min: 1; max: 10000)

Response

• @type string (default: "JobtalkSalaryReport")
• id string required
• url string required
• company_id string required
• member_id string nullable
• annual_salary number nullable
• rating number nullable
• posted_at integer nullable
• salary_year_at integer nullable
• age integer nullable
• gender string nullable
• job_type string nullable
• position string nullable
• employment_type string nullable
• relationship string nullable
• relationship_name string nullable

Errors

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