/levtech/freelance/projects

POST /api/levtech/freelance/projects

Price: 1 credit

Get one freelance or contract IT project on Levtech Freelance (freelance.levtech.jp): work content, required and preferred skills, monthly or hourly rate cap, settlement hours and payment terms, start date, interview count, working days, location, remote work, skills, job types, industries, features, and similar projects. Closed projects are returned with is_closed true.

How to use it

Find project ids with levtech/freelance/projects/search.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• project string required — Project id or URL (examples: "638033", "https://freelance.levtech.jp/project/detail/638033/"; minLength: 1)

Response

• @type string (default: "LevtechProject")
• pay_type string nullable
• pay_max number nullable
• pay_period string nullable
• pay_currency string nullable
• id string required
• url string required
• is_closed boolean nullable
• is_new boolean nullable
• contract_type string nullable
• published_at integer nullable
• start_date integer nullable
• work_content string nullable
• required_skills string nullable
• preferred_skills string nullable
• coordinator_comment string nullable
• settlement_hours_min integer nullable
• settlement_hours_max integer nullable
• settlement_terms string nullable
• payment_terms string nullable
• interview_count integer nullable
• min_days_per_week integer nullable
• openings integer nullable
• station string nullable
• prefecture string nullable
• ward string nullable
• remote_work string nullable
• remote_type string nullable
• online_interview_ok boolean nullable
• side_job_ok boolean nullable
• skills array (default: [])
  • @type string (default: "LevtechSkill")
  • id string nullable
  • name string required
  • category string nullable
• job_types array (default: [])
  • @type string (default: "LevtechLabel")
  • id string nullable
  • name string required
• positions array (default: [])
  • @type string (default: "LevtechLabel")
  • id string nullable
  • name string required
• industries array (default: [])
  • @type string (default: "LevtechLabel")
  • id string nullable
  • name string required
• works array (default: [])
• domains array (default: [])
• features array (default: [])
  • @type string (default: "LevtechLabel")
  • id string nullable
  • name string required
• similar_projects array (default: [])
  • @type string (default: "LevtechRelatedProject")
  • pay_type string nullable
  • pay_max number nullable
  • pay_period string nullable
  • pay_currency string nullable
  • id string required
  • url string required
  • is_new boolean nullable
  • contract_type string nullable
  • skills array (default: [])
  • station string nullable
  • prefecture string nullable
  • remote_work string nullable
  • features array (default: [])
    • @type string (default: "LevtechLabel")
    • id string nullable
    • name string required
• remote_projects array (default: [])
  • @type string (default: "LevtechRelatedProject")
  • pay_type string nullable
  • pay_max number nullable
  • pay_period string nullable
  • pay_currency string nullable
  • id string required
  • url string required
  • is_new boolean nullable
  • contract_type string nullable
  • skills array (default: [])
  • station string nullable
  • prefecture string nullable
  • remote_work string nullable
  • features array (default: [])
    • @type string (default: "LevtechLabel")
    • id string nullable
    • name string required
• replacement_projects array (default: [])
  • @type string (default: "LevtechLabel")
  • id string nullable
  • name 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 — No project 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.