/levtech/freelance/projects/search

POST /api/levtech/freelance/projects/search

Price: 5 credits

Search freelance and contract IT projects on Levtech Freelance (freelance.levtech.jp) by keyword, skill, job type, kind of work, industry, project feature, location, remote work, contract type, working days and minimum rate. Each result carries the title, monthly or hourly rate cap, skills, job types, location, remote work, working days and required skills; closed projects are included unless open_only is set.

How to use it

A search returns at most 3,000 projects; set open_only to skip projects no longer taking applications. Skills of different kinds (language, framework, database, OS, cloud) must all match, skills of one kind any of. Pass a result's id to levtech/freelance/projects for the full project.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• count integer required — Max number of projects to return (min: 1; max: 3000)
• keyword string nullable — Search words (examples: "Python", "SRE"; minLength: 1)
• skills array nullable — Skill names (examples: ["Python","React","AWS"]; minItems: 1)
• job_types array nullable — Job types, any of (one of: "it_consultant", "data_scientist", "network_engineer", "infrastructure_engineer", "technical_support", "frontend_engineer", "application_engineer", "server_engineer", "security_engineer", "database_engineer", "test_engineer", "erp_consultant", "embedded_engineer", "mainframe_engineer", "internal_it", "backend_engineer", "project_manager", "project_leader", "pmo")
• works array nullable — Kinds of work, any of (one of: "new_development", "enhancement", "app_development", "tuning", "refactoring", "replacement", "data_mining", "load_balancing", "vendor_management", "api_development", "localization", "internal_systems", "own_product", "server_side", "animation", "graphic_design", "level_design", "data_analysis", "network_monitoring", "game_development", "information_security", "natural_language_processing", "iphone_apps", "android_apps", "system_development", "software_development", "contract_development", "machine_learning", "operations_monitoring", "cms", "ipad", "native_apps", "migration", "groupware", "erp", "scm", "server_setup")
• industries array nullable — Industries, any of (one of: "social_games", "broadcasting_publishing_music", "securities", "telecom", "government", "life_insurance", "healthcare_welfare", "big_data", "ecommerce", "staffing_education", "retail", "console_games", "non_life_insurance", "banking", "credit_cards")
• features array nullable — Project features, any of (one of: "long_term", "new_technology", "new_launch", "little_experience_ok", "startup", "own_service", "casual_dress", "mostly_in_house", "listed_company", "upstream_work", "market_leader", "venture", "lamp", "lapp", "b2c", "b2b", "placed_before", "training", "leadership", "foreign_nationals", "foreign_language", "forties", "thirties", "twenties", "small_team", "high_traffic", "over_1000_employees", "under_100_employees", "gamers_welcome", "urgent", "short_term", "ccnp", "travel_allowance")
• prefectures array nullable — Prefectures, any of (one of: "tokyo", "kanagawa", "chiba", "saitama", "ibaraki", "tochigi", "gunma", "aichi", "osaka", "hyogo", "kyoto", "shiga", "nara", "wakayama", "fukuoka", "nagasaki", "kumamoto", "oita")
• districts array nullable — Cities and districts, any of (one of: "tokyo_23_wards", "tokyo_other", "yokohama", "kanagawa_other", "osaka_city", "osaka_other", "fukuoka_city", "fukuoka_other")
• areas array nullable — Station areas, any of (one of: "roppongi_azabu_akasaka", "shinagawa_mita_hamamatsucho", "shibuya_harajuku_daikanyama", "ebisu_nakameguro_meguro", "ueno_nippori_okachimachi", "shinjuku_yoyogi_okubo", "ikebukuro_takadanobaba_mejiro", "kagurazaka_iidabashi_yotsuya", "koenji_ogikubo_nakano_asagaya", "shimokitazawa_sasazuka_meidaimae", "sangenjaya_setagaya_ikejiri", "ginza_kyobashi_yurakucho", "tokyo_nihonbashi_otemachi", "jimbocho_suidobashi_kudanshita", "akihabara_kanda_ochanomizu", "gotanda_osaki", "shin_osaka_esaka_nishinakajima", "minamimorimachi_obp_kyobashi", "umeda_nakatsu_dojima", "nakanoshima_yodoyabashi_higobashi", "hommachi_yotsubashi_namba", "tennoji_abeno_daikokucho", "nishikujo_bentencho_taisho")
• remote array nullable — Remote work types, any of (one of: "full", "partial")
• online_interview_only boolean — Only projects with online client meetings (default: false)
• contract_types array nullable — Contract types, any of (one of: "subcontract", "temporary_staffing")
• days_per_week array nullable — Working days per week, any of (one of: "5", "4", "3_or_less")
• min_rate string nullable — Minimum monthly rate in JPY, or hourly projects (one of: "300000", "400000", "500000", "600000", "700000", "800000", "900000", "1000000", "1100000", "hourly")
• open_only boolean — Only projects open for applications (default: false)
• sort string — Result order (default: "relevance"; one of: "relevance", "newest", "rate")

Response

• @type string (default: "LevtechProjectCard")
• 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
• skills array (default: [])
  • @type string (default: "LevtechSkill")
  • id string nullable
  • name string required
  • category string nullable
• job_type_names array (default: [])
• positions array (default: [])
• features array (default: [])
  • @type string (default: "LevtechLabel")
  • id string nullable
  • name string required
• station string nullable
• prefecture string nullable
• remote_work string nullable
• remote_type string nullable
• online_interview_ok boolean nullable
• days_per_week string nullable
• required_skills string nullable

Errors

• 422 — An unknown enum value or skill name 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 — The entity was not found, or a precondition failed 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.