/behance/jobs

POST /api/behance/jobs

Price: 1 credit

Get Behance full-time/contract job details by id or URL

How to use it

Get a Behance full-time or contract job posting by its numeric id or URL. Returns title, full description, company, job type, remote status, locations, salary range, categories, creative fields, and posting/expiry dates. Freelance briefs are not available.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• job string required — Behance full-time/contract job numeric id or job URL (examples: "357693", "https://www.behance.net/joblist/fulltime/357717/3D-Modeling-Artist"; minLength: 1)

Response

• @type string (default: "BehanceJob")
• id integer required
• job_title string nullable
• description string nullable
• job_type string nullable
• company_type string nullable
• remote_status string nullable
• company_name string nullable
• company_url string nullable
• company_image string nullable
• location string nullable
• locations array (default: [])
  • @type string (default: "BehanceJobLocation")
  • name string nullable
  • country string nullable
  • state string nullable
  • city string nullable
• categories array (default: [])
• creative_fields array (default: [])
• salary_min number nullable
• salary_max number nullable
• salary_currency string nullable
• salary_timeframe string nullable
• posted_at integer nullable
• expires_at integer nullable
• applicant_count integer nullable
• application_url string nullable
• url 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 — Job not found (or it is a freelance brief). Verify the numeric job id or URL. 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.