Foorilla AI Jobs Scraper — ML & Data Roles

Start with one input and output

An Apify account is required. Use your Apify API token when calling the API; Console runs do not need that token pasted into the input. No user API-key field is required by this input schema.

Free-tier event rates checked 2026-10-04: actor-start $0.005; result $0.002. Scale and Business plans pay less per result event: $0.075 and $0.05 per 1,000.

Cost: Total = Actor event charges + platform usage if separately billed + any BYO-provider charges. See “Current costs” for your event rates, plan tiers and a calculation. A sample does not promise future billable volume.

Input and output below were read from the same successful run 2IkjOvd6DVxuefqkV (2026-10-03, immutable build cE0nUfrUiBoxiGnYH). This is an observed example, not a guarantee that repeating it returns this row. It used an earlier build; current-build execution has not been proved by this example.

Input JSON

{
  "dedupe": {
    "enabled": false,
    "key": ""
  },
  "maxItems": 3,
  "queries": [],
  "locations": [],
  "locationTypes": [],
  "employmentTypes": [],
  "postedWithin": "any",
  "schemaVersion": "nomad-agent-simple-inventory-search-v2"
}

Matching output excerpt

Long strings and arrays are shortened for display; this is not a complete dataset fixture.

{
  "schemaVersion": "nomad-agent-job-row-v3",
  "source": "foorilla",
  "id": "3844322",
  "url": "https://foorilla.com/hiring/jobs/ai-developer-columbus-ga-united-states-3844322/",
  "title": "AI Developer",
  "company": null,
  "locations": [
    "Columbus, GA, United States"
  ],
  "postedAt": "2026-10-03",
  "deadline": null,
  "description": "Tasks: * Analyze and design technical solutions * Assist junior developers * Build and deploy full stack applications * Conduct unit testing * Design and optimize data structures and queries * Develop and maintain enterprise software * Develop ETL processes and data warehousing strategies * Develop reporting solutions * Integrate AI systems and tools * Maint… [truncated for display]",
  "descriptionHtml": "\n<strong>Tasks:</strong>\n<ul class=\"list-unstyled mb-2\">\n<li>* Analyze and design technical solutions</li><li>* Assist junior developers</li><li>* Build and deploy full stack applications</li><li>* Conduct unit testing</li><li>* Design and optimize data structures and queries</li><li>* Develop and maintain enterprise software</li><li>* Develop ETL processes … [truncated for display]",
  "workType": null,
  "salary": null,
  "employmentTypes": null,
  "hiringContacts": []
}

Recent Foorilla jobs with complete original descriptions. Each row carries the source ID and URL, title, employer, locations, the original description as text and HTML, posting date, deadline, work arrangement, employment type, salary and the hiring contacts the source names, whenever the source publishes them. Unknown optional facts are null; an empty locations array means the source names no physical place, and an empty hiringContacts array means the source names nobody. locations is where the job is, countryCodes lists the countries of those places as ISO 3166-1 two-letter codes (null when no place has a known country), and applicantLocations is where an applicant may live, for example a remote job open only to residents of some countries: it is null when the source states nothing and [] when it states no restriction.

Coverage includes jobs from public Foorilla pages. Every posting is verified before it is served. A posting with a missing, truncated or unverified description is never returned: every row has the full original text.

Input

{"schemaVersion": "nomad-agent-simple-inventory-search-v2", "queries": ["software engineer"], "locations": ["Europe"], "locationTypes": ["remote"], "employmentTypes": [], "postedWithin": "7d", "maxItems": 50, "dedupe": {"enabled": true, "key": ""}}

Every filter is optional, and an empty list means no filter. Filters are applied to all available postings before maxItems is counted.

• queries: a posting matches a query when its title or description contains every word of it, as whole words, ignoring case. A posting matches when any query matches.
• locations: a city, region, country name or two-letter ISO country code. Countries match by name, code and native name (Germany, DE and Deutschland find the same postings), and EU and Europe cover their member countries.
• locationTypes (remote, hybrid, onsite) and employmentTypes (Full-time, Part-time, Contract, Internship): while one is set, a posting whose source does not state that fact is left out.
• postedWithin: a positive duration in hours (h), days (d), weeks (w) or 30-day months (m), up to 36500 days, or any. Postings without a source date use the date they were first seen, which later refreshes never reset.
• maxItems defaults to 50; 0, or anything above 200, means 200.
• dedupe suppresses postings already delivered to the same Apify account for the same search; different filters keep separate histories. Set dedupe.enabled to false to get stateless results, or set dedupe.key to keep separate alert histories.

Output

One flat row per posting in the nomad-agent-job-row-v5 format: schemaVersion, source, id, url, title, company, locations, countryCodes, applicantLocations, postedAt, deadline, description, descriptionHtml, workType, salary, employmentTypes, hiringContacts. employmentTypes lists the types the source states (Full-time, Part-time, Contract, Internship) or is null. countryCodes lists the countries of the job's places as ISO 3166-1 alpha-2 codes (for example DE, FR), in the same order as locations, each once. A code comes from the source if it states one, otherwise from the place label. It's null when no place has a known country (a remote job with no country, or an unidentifiable place) and never an empty list. A place without a known country adds nothing, so the list can name fewer countries than there are places. A posting stored on a single-country board with no place at all carries that board's country, so locations can be [] while countryCodes names one. The locations filter matches countries against these codes as well as names and text. applicantLocations lists the regions where the source says an applicant may live (for example United States for a remote job open to US residents), null when it states nothing and [] when it states no restriction. Each hiring contact has a name, and a title and url or null. Newest postings come first. A run summary, including any input field that was mapped or ignored, is written to the RUN-SUMMARY record of the run's key-value store.

Changes

• October 2026: countryCodes added (row v5). Rows are now nomad-agent-job-row-v5: one new field, countryCodes, lists the ISO 3166-1 alpha-2 country codes of the job's places, in the order of locations, each once (null when no place has a known country, never an empty list). A code is the country the source states, or if it doesn't state one, the country read from the place label. A place whose country can't be determined adds nothing. locations and applicantLocations are unchanged. Input, other fields, and pricing are unchanged. Integrations validating against the v4 schema must allow the new field and the new schemaVersion.
• October 2026: applicantLocations added (row v4). Rows are now nomad-agent-job-row-v4: one new field, applicantLocations, lists where an applicant may live as the source states it (null when the source states nothing, [] when it states no restriction). locations is unchanged and still the physical place only; for a remote job open to some regions it is often [] while applicantLocations lists the regions. Input, other fields and pricing are unchanged. Integrations that validate rows against the v3 schema must allow the new field and the new schemaVersion.
• October 2026: recordType removed. nomad-agent-job-row-v3 rows no longer include the recordType field, because every dataset row is a posting. Read schemaVersion instead. The RUN-SUMMARY record is unchanged and keeps its own recordType.
• September 2026: search filters and richer rows. The input (nomad-agent-simple-inventory-search-v2) adds queries, locations, locationTypes and employmentTypes. Rows are now nomad-agent-job-row-v3 and add employmentTypes and hiringContacts. Integrations that still send keyword or location keep working: those values become queries and locations, remote: true becomes locationTypes: ["remote"], and other old fields are ignored with a note in RUN-SUMMARY instead of failing the run. Pricing is unchanged.
• Earlier: this Actor moved to verified available postings in the shared simple job format, and every row includes the complete description.

Fast setup and source code

Public repository · Agent setup skill.

Use the Actor’s current input form for filters, or start with its documented API example. Select latest for foorilla-ai-jobs-scraper and record the immutable build ID and number returned by your run. Inspect the dataset and any run summary the Actor documents together; a successful status alone does not establish complete source coverage.

Restrictive filters or repeat-delivery suppression can produce zero results. Diagnostics and demo records are not source records. Optional AI or translation stays explicit where supported.

Product guides and related tools

• Product overview and public links
• Public setup guide
• Job Atlas job-data tools
• Oink personal job alerts
• Applied to 200 jobs with no response? What to do instead

Current costs

Current Actor event rates, checked 2026-10-16. USD; use the Pricing tab for your plan and later changes.

Event	Free	Bronze	Silver	Gold	Platinum	Diamond
Actor start (actor-start)	$0.00005	$0.00005	$0.00005	$0.00005	$0.00005	$0.00005
Foorilla job result (result)	$0.0001	$0.0001	$0.000075	$0.00005	$0.00005	$0.00005

For example, 1 × actor-start, 100 × result totals $0.205 in Actor event charges on Free. This is an arithmetic example, before any waiver; actual charged events depend on the run and selected options. It is not a promise of output or a charge for simply setting an item cap.

Your total is the charged Actor events, plus platform usage only if this Actor’s Pricing tab bills it separately, plus any external provider you use with your own key. Do not add platform usage twice when it is included. Apify credits and plan discounts affect your invoice. Set a run cost limit in Console before starting.