/remoteok/jobs/search

POST /api/remoteok/jobs/search

Price: 10 credits

Search remote jobs on RemoteOK, optionally filtered by one or more tags

How to use it

List remote job postings from RemoteOK, optionally filtered by tags (skills, categories, or job types such as 'python', 'design', 'senior', 'customer support'). Multiple tags are combined with AND — a job must carry every tag. Each result includes the job id, title, company, tags, location, salary range when stated, posting date, and apply link. Pass a returned job id to the 'jobs' endpoint for the full posting with structured salary, employment type, industry, and hiring organization details.

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)
• tags array — Filter jobs by one or more tags (skills, categories, or job types). Multiple tags are combined with AND — a job must match every tag. Omit to get the latest jobs. (default: []; examples: ["python","senior"], ["design"], ["customer support"])

Response

• @type string (default: "RemoteokJobSummary")
• id string required
• alias string nullable
• position string required
• company string nullable
• description string nullable
• tags array (default: [])
• location string nullable
• salary_min integer nullable
• salary_max integer nullable
• image string nullable
• apply_url string nullable
• url string nullable
• created_at string nullable
• epoch integer 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.