/findy/jobs/search

POST /api/findy/jobs/search

Price: 10 credits

Search software engineering jobs on Findy (findy-code.io), the Japanese job board for engineers, by keyword, job role, skill, company industry, work region, job feature, minimum salary, new jobs, slide decks or Team+ Award companies. Each result carries the title, description, salary range, job roles, skills, features and the hiring company.

How to use it

A search returns at most 3,000 jobs, so narrow by role, skill or region for more. Pass a result's url, or its id with company.id, to findy/jobs for the full posting.

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 jobs to return (min: 1; max: 3000)
• keyword string nullable — Search words (examples: "Rails", "機械学習"; minLength: 1)
• job_roles array nullable — Job roles, any of (one of: "frontend_engineer", "backend_engineer", "full_stack_engineer", "forward_deployed_engineer", "customer_reliability_engineer", "devops_engineer", "site_reliability_engineer", "infrastructure_engineer", "security_engineer", "network_engineer", "database_engineer", "data_engineer", "machine_learning_engineer", "data_scientist", "data_analyst", "ai_llm_engineer", "ios_engineer", "android_engineer", "qa_engineer", "software_engineer_in_test", "ux_engineer", "game_engineer", "embedded_engineer", "it_consultant", "system_engineer", "internal_it", "technical_support_engineer", "pre_sales", "other_engineer", "project_manager", "product_manager", "scrum_master", "vp_of_engineering", "cto_or_advisor", "engineering_manager", "tech_lead", "ai_llm_project_manager", "other_management")
• skills array nullable — Skill names, any of (examples: ["Go","TypeScript"]; minItems: 1)
• industries array nullable — Company industries, any of (one of: "communication", "media", "games", "advertising_marketing", "cloud_saas", "ai", "telecom", "broadcasting", "publishing", "electronics_iot", "automotive", "electronic_components", "oil_chemicals", "heavy_industry", "utilities", "transportation", "railways", "food_beverage", "consumer_goods", "apparel", "retail", "restaurants", "travel_hotels", "education", "recruitment", "banking_securities", "credit_payments_leasing", "insurance", "accounting", "investment", "real_estate", "construction", "pharmaceuticals", "healthcare", "hospitals", "elderly_care", "consulting", "it_services", "trading", "government", "agriculture_forestry_fisheries", "other")
• areas array nullable — Work regions, any of (one of: "hokkaido_tohoku", "kanto", "hokuriku_koshinetsu", "tokai", "kansai", "chugoku_shikoku", "kyushu_okinawa", "overseas")
• features array nullable — Job features, any of (one of: "partly_remote", "fully_remote", "agile", "scrum", "own_product", "english", "meet_cto_ceo", "no_experience_ok", "side_job_ok", "contract_ok", "b2c", "b2b", "any_language", "sier_ses_welcome", "join_as_side_job")
• salary_min integer nullable — Minimum upper bound of the annual salary range in JPY (examples: 8000000; min: 1)
• new_only boolean — Only jobs marked new (default: false)
• with_slides boolean — Only jobs with a company introduction slide deck (default: false)
• team_plus_award_only boolean — Only jobs at Findy Team+ Award companies (default: false)
• sort string — Result order (default: "popularity"; one of: "popularity", "newest")

Response

• @type string (default: "FindyJobCard")
• salary_min number nullable
• salary_max number nullable
• salary_currency string nullable
• id string required
• numeric_id integer nullable
• url string required
• description string nullable
• work_hours string nullable
• job_roles array (default: [])
  • @type string (default: "FindyJobRole-Output")
  • id string required
  • name string required
  • category_id string nullable
  • is_management boolean nullable
• skills array (default: [])
  • @type string (default: "FindyNamed")
  • id string required
  • name string required
• features array (default: [])
  • @type string (default: "FindyNamed")
  • id string required
  • name string required
• personality_tags array (default: [])
  • @type string (default: "FindyNamed")
  • id string required
  • name string required
• created_at integer nullable
• published_at integer nullable
• company object required
  • @type string (default: "FindyCompanyRef")
  • id string required
  • url string required
  • name string nullable
  • image string nullable
  • team_plus_award 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.