/rikunabi/companies

POST /api/rikunabi/companies

Price: 5 credits

Get Rikunabi NEXT company details by id

How to use it

Get a Rikunabi NEXT (リクナビNEXT) employer profile by its company id. Returns the company name, CEO, address, phone, business details, and website, an AI company research brief (markdown summary with cited sources), the total number of open positions, and the list of the company's currently posted jobs (each with job key, title, location, salary, employment types, and preference tags).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• company string required — Rikunabi NEXT company id, or a company URL containing it (examples: "332919455", "https://next.rikunabi.com/company/332919455/"; minLength: 1)

Response

• @type string (default: "RikunabiCompany")
• id string required
• url string required
• name string required
• ceo_name string nullable
• address string nullable
• phone string nullable
• business_details string nullable
• web_url string nullable
• job_count integer nullable
• company_research object nullable
  • @type string (default: "RikunabiCompanyResearch")
  • summary string nullable
  • citations array (default: [])
    • @type string (default: "RikunabiResearchCitation")
    • id string nullable
    • url string nullable
    • favicon_url string nullable
  • updated_at string nullable
• jobs array (default: [])
  • @type string (default: "RikunabiJobCard")
  • id string required
  • url string required
  • title_pr string nullable
  • company_name string nullable
  • company_id string nullable
  • location string nullable
  • lat number nullable
  • lon number nullable
  • employment_types array (default: [])
  • salary_text string nullable
  • salary object nullable
    • @type string (default: "RikunabiCardSalary")
    • min integer nullable
    • max integer nullable
    • currency string nullable
    • unit string nullable
  • qualification string nullable
  • preference_tags array (default: [])
  • image string nullable
  • is_new_arrival boolean nullable
  • published_at integer nullable

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 — Company not found 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.