/wantedly/projects

POST /api/wantedly/projects

Price: 1 credit

Get a Wantedly project (job posting) by its numeric id

How to use it

Get a Wantedly project (job posting / 募集) by numeric id. Returns the full posting — title, description, what/why/how company-story sections with images, location and coordinates, view/support/candidate counts, hiring types, tags, the hiring company profile, the project members (staffings), and supporters.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• project integer required — Numeric Wantedly project id (examples: 2176124; >: 0)

Response

• @type string (default: "WantedlyProject")
• id integer required
• description string nullable
• looking_for string nullable
• published_at string nullable
• location string nullable
• location_suffix string nullable
• latitude number nullable
• longitude number nullable
• page_view integer nullable
• support_count integer nullable
• candidate_count integer nullable
• image string nullable
• what_description string nullable
• what_images array (default: [])
• why_description string nullable
• why_images array (default: [])
• how_description string nullable
• how_images array (default: [])
• company object nullable
  • @type string (default: "WantedlyProjectCompany")
  • id integer required
  • name string required
  • founder string nullable
  • founded_on string nullable
  • payroll_count integer nullable
  • address_prefix string nullable
  • address_suffix string nullable
  • latitude number nullable
  • longitude number nullable
  • web_url string nullable
  • image string nullable
  • industries array (default: [])
  • tags array (default: [])
• staffing_count integer nullable
• staffings array (default: [])
  • @type string (default: "WantedlyStaffing")
  • user_id integer required
  • name string nullable
  • position string nullable
  • description string nullable
  • is_leader boolean (default: false)
  • image string nullable
• supporters array (default: [])
  • @type string (default: "WantedlySupporter")
  • id integer required
  • name string nullable
• category_tags array (default: [])
• hiring_types array (default: [])
• tags array (default: [])
• has_video boolean (default: false)

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 — Project 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.