POST /api/daangn/jobs/authors
Price: 1 credit
Get a Daangn (당근) jobs employer by id or profile URL: nickname, manner temperature, registered business name and owner, hire count, review count, response rate and the employer's latest job posts
job_posts holds the employer's 20 latest open and closed posts; pass a post id to daangn/jobs.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)author string required — Daangn jobs employer id or profile URL (examples: "t77jjb996pqr", "https://jobs.daangn.com/authors/t77jjb996pqr"; minLength: 1)@type string (default: "DaangnJobAuthor")id string requiredurl string requirednickname string nullableimage string nullableregion string nullablemanner_temperature number nullableis_official boolean nullableis_identity_verified boolean nullableis_perfect_author boolean nullablecompany_name string nullableowner_name string nullablebusiness_registration_number string nullablebusiness_license_verified_at integer nullablehire_count integer nullablereview_count integer nullableresponse_rate number nullablelast_active_at integer nullablejob_posts array (default: [])@type string (default: "DaangnAuthorJobPost")id string requiredurl string requiredtitle string nullablecompany_name string nullablecompany_logo string nullablebusiness_type string nullableemployment_type string nullableis_closed boolean nullablesalary number nullablesalary_type string nullablesalary_pay_method string nullablework_days array (default: [])work_dates array (default: [])work_start string nullablework_end string nullableis_work_time_negotiable boolean nullableis_work_days_negotiable boolean nullableneighborhood string nullableimages array (default: [])employer_review_count integer nullableis_perfect_author boolean nullablepublished_at integer nullablesalary_text string nullable422 — 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 — Daangn has no jobs employer 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.