/saramin/interviews/search

POST /api/saramin/interviews/search

Price: 10 credits

Search Saramin interview reviews by company and filters

How to use it

Search Saramin interview reviews (면접후기) shared by candidates — optionally filter by company name, candidate experience level (new grad or experienced), and job category, and order by newest or by interview date. Each result carries the company, the role and interview period, the candidate experience level, the outcome (pass or fail), the overall impression and perceived difficulty, the interview types and panel composition, the interview process narrative, the list of questions asked, and any extra tips, plus the date the review was posted.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• keyword string nullable — Company name to search interview reviews for (examples: "삼성전자"; minLength: 1)
• count integer required — Max number of interview reviews to return (min: 1)
• career string nullable — Filter by candidate experience level (one of: "newcomer", "experienced")
• job_category string nullable — Filter by job category (one of: "planning_strategy", "marketing", "accounting_finance", "hr", "general_admin", "it_development", "design", "sales_trade", "customer_service", "purchasing_logistics", "product_planning", "transport_delivery", "service", "production", "construction", "medical", "research_rnd", "education", "media_culture_sports", "finance_insurance", "public_welfare")
• sort string — Result ordering (default: "newest"; one of: "newest", "interview_date")

Response

• @type string (default: "SaraminInterview")
• id string required
• company string required
• position string nullable
• period string nullable
• career_level string nullable
• result string nullable
• is_passed boolean nullable
• overall_rating string nullable
• difficulty string nullable
• interview_types array (default: [])
• personnel string nullable
• text string nullable
• questions array (default: [])
• tips string nullable
• created_at string 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 — 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.