/jobkorea/companies

POST /api/jobkorea/companies

Price: 10 credits

Get one JobKorea (jobkorea.co.kr) company by id or URL: name, industry, company type, headcount, founding date, capital, revenue, CEO, entry salary, main business, homepage, address, affiliates, business segments, yearly revenue and income, the full financial statement table by year, industry revenue ranking, benefits by category, yearly headcount, hiring counts and company history

How to use it

Pass an id from jobkorea/companies/search or a job's company id. Money values are in KRW; ratio rows of financial_statements are percent.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• company string required — JobKorea company id or URL (examples: "1696583", "https://www.jobkorea.co.kr/company/1696583"; minLength: 1)

Response

• @type string (default: "JobkoreaCompany")
• id string required
• url string required
• name string nullable
• summary array (default: [])
• industry string nullable
• company_type string nullable
• employee_count integer nullable
• employee_count_date integer nullable
• founded_date integer nullable
• capital number nullable
• revenue number nullable
• revenue_date integer nullable
• ceo string nullable
• entry_salary number nullable
• main_business string nullable
• social_insurance array (default: [])
• homepage string nullable
• address string nullable
• affiliates array (default: [])
• business_segments array (default: [])
  • @type string (default: "JobkoreaBusinessSegment")
  • share number nullable
  • description string required
• financials array (default: [])
  • @type string (default: "JobkoreaFinancialYear")
  • year integer required
  • revenue number nullable
  • operating_income number nullable
  • net_income number nullable
• financial_statements array (default: [])
  • @type string (default: "JobkoreaStatementRow")
  • account string required
  • unit string required
  • values array (default: [])
    • @type string (default: "JobkoreaStatementValue")
    • date integer required
    • value number required
• industry_ranking object nullable
  • @type string (default: "JobkoreaIndustryRanking")
  • rank integer nullable
  • based_on string nullable
  • year integer nullable
  • companies array (default: [])
    • @type string (default: "JobkoreaRankedCompany")
    • rank integer required
    • id string nullable
    • name string nullable
    • is_current boolean (default: false)
• benefits array (default: [])
  • @type string (default: "JobkoreaBenefitGroup")
  • category string required
  • names array (default: [])
• headcount_history array (default: [])
  • @type string (default: "JobkoreaHeadcountYear")
  • year integer required
  • employee_count integer required
• hiring_counts array (default: [])
  • @type string (default: "JobkoreaHiringCount")
  • career_type string required
  • count integer required
• history array (default: [])
  • @type string (default: "JobkoreaHistoryEvent")
  • year integer required
  • month integer nullable
  • text string required

Errors

• 422 — 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 — JobKorea has no 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.