Choose the source that fits the question
Both Actors return remote-job rows, but their source fields and coverage differ. Start with one source instead of merging results immediately. That makes it easier to understand missing fields, duplicates, and attribution requirements.
| Actor | Useful when | Filters |
|---|---|---|
| Jobicy Remote Jobs Scraper | You need role, geography, or industry filtering. | search, geo, industry |
| Remotive Remote Jobs Scraper | You need keyword search or a known Remotive category. | search, category |
Run a small keyword search
- Open either Actor and select Try for free or the Input tab.
- Keep the maximum at 20 while learning the dataset.
- Use the starter input below.
- Select Start, wait for a successful run, and open the Dataset tab.
Jobicy input
{
"search": "python",
"geo": "",
"industry": "",
"maxResults": 20
}Remotive input
{
"search": "python",
"category": "",
"maxResults": 20
}For a ready-made run, open the public Remotive Python remote-jobs example and adjust the inputs.
Verify the output before using it
Inspect at least five rows. Confirm that the title and company are present, the job is still public, the source URL opens, and the application URL points to the expected destination. Salary and expiry fields are useful when disclosed, but they will not exist on every posting.
| Field | What to check |
|---|---|
jobId | Use the source identifier for deduplication between scheduled runs. |
title, company | Confirm the role and employer match the linked source record. |
location, workplaceType | Remote does not always mean worldwide. Preserve candidate-location restrictions. |
publishedAt, expiresAt | Treat missing expiry as unknown, not as an indefinitely open role. |
applyUrl | Keep the direct source link so a person can verify the vacancy. |
Export once, then schedule carefully
Use the Dataset export menu for CSV, Excel, or JSON. For a recurring alert, save the input as a Task and attach an Apify schedule or webhook. Deduplicate on the source and jobId before sending notifications.
Respect the upstream feeds. Jobicy asks public API users not to request its feed more than once per hour. Remotive recommends no more than four public API requests per day and requires attribution. A daily run is a sensible starting cadence for either source.
Understand cost before scaling
Each Actor charges $3 per 1,000 returned job rows. A 20-row learning run therefore has a result charge of $0.06, plus any Apify platform usage associated with the run. Empty searches, failed requests, diagnostics, and duplicate rows are not sold as job results.
Common questions
Why did my search return fewer than 20 jobs?
The public feed may contain fewer current matches. Broaden the keyword, remove a geography or category filter, and run again.
Can I combine Jobicy and Remotive?
Yes. Keep a source field, deduplicate using source plus job ID, and verify application URLs before publishing or alerting.
Can I automate job applications?
No. These Actors provide public research data. Keep a person in the application process and avoid spam, bulk applications, or discriminatory filtering.
When should I use LinkedIn jobs instead?
Use LinkedIn search when you need its employer and location coverage. Use these public-API Actors when low-cost remote-job feeds and simple recurring updates are the priority.
Need broader employer career pages?
Use the Jobs and ATS directory to compare LinkedIn, Greenhouse, Lever, Workday, and other public career-site tools.
Browse Jobs & ATS tools