/remoteok/jobs

POST /api/remoteok/jobs

Price: 5 credits

Get a single RemoteOK job posting by id, slug, or URL

How to use it

Get the full RemoteOK job posting by its id, slug, or URL. Returns the title, company, description, tags, location, apply link, and rich structured details from the posting — salary range with currency and period, employment type, industry, remote/location type, applicant location requirements, work hours, validity date, and the hiring organization with its logo and profile link.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• job string required — Job id, slug, or RemoteOK job URL (examples: "1133392", "remote-template-pizza-pilgrims-1133392", "https://remoteok.com/remote-jobs/remote-template-pizza-pilgrims-1133392"; minLength: 1)

Response

• @type string (default: "RemoteokJob")
• id string required
• alias string nullable
• position string required
• company string nullable
• description string nullable
• tags array (default: [])
• location string nullable
• image string nullable
• apply_url string nullable
• url string nullable
• salary object nullable
  • @type string (default: "RemoteokSalary")
  • currency string nullable
  • min_value number nullable
  • max_value number nullable
  • period string nullable
• employment_type string nullable
• industry string nullable
• job_location_type string nullable
• applicant_location_requirements array (default: [])
• work_hours string nullable
• job_benefits array (default: [])
• is_direct_apply boolean nullable
• valid_through string nullable
• created_at string nullable
• epoch integer nullable
• hiring_organization object nullable
  • @type string (default: "RemoteokOrganization")
  • name string nullable
  • url string nullable
  • image 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 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.