Ikerbasque Jobs Scraper (No Login) + Full Descriptions

$4/1K jobs | Extract open Ikerbasque research calls (Basque Foundation for Science) with the full original description in text and HTML, plus source links. Typically a handful at a time. No login or API key. Not affiliated with Ikerbasque.

Ikerbasque Research Calls Scraper

Our scraper collects the open research calls and fellowship programmes listed by Ikerbasque, the Basque Foundation for Science. Every row carries the complete original description in text and HTML and a link to the call. Ikerbasque lists only a handful of calls at a time (5 in our test run), so this Actor is a monitor for new calls rather than a bulk exporter. It is ideal for research-career alerts and funding-call tracking.

• Want PhD, postdoc and research jobs from 11 sources, Ikerbasque included, in one run? Use PhD, Postdoc & Research Jobs Scraper (No Login) + 11 Boards.
• Need far more volume across Europe? Our EURAXESS Jobs Scraper — EU Research Positions is a better fit, with many more research postings.
• Looking for postdoc and PhD jobs at universities? Use AcademicPositions Job Scraper.
• Browse all our job-board scrapers: https://apify.com/nomad-agent

Key Benefits

• No login or API key: nothing to set up, and no Ikerbasque account at risk.
• Pricing: $4 per 1,000 jobs, with lower rates on paid plans (Starter $3.7, Scale $3, Business and Enterprise $2 per 1,000), plus $0.02 per run start.
• Full descriptions only: a posting with a missing or truncated description is never returned.
• No repeats across runs: schedule the same search daily and get only postings you have not received yet.

How It Works

1. Provide your search. Every filter is optional:
   • (optional) Search queries (e.g., fellow, climate). A job matches when its title or description contains every word of a query.
   • (optional) Locations. Ikerbasque postings carry no location, so leave this empty.
   • (optional) Posted within (e.g., 24h, 7d, 2w). Default is any.
2. Set how many jobs you want with maxItems.
3. Click Start. The form opens with research and 10 jobs, so a first run returns real rows. In our test run, 4 calls matched and came back in about 16 seconds (with no keyword, all 5 open calls came back).

More settings:

• maxItems - How many jobs one run returns. Default is 50; 0, or anything above 200, means 200.
• dedupe - On by default: jobs already delivered to your Apify account for the same search are skipped. Set dedupe.enabled to false to get everything again, or set dedupe.key to keep separate alert histories.

Run the same search twice and the second run returns only new jobs, possibly none. That is the repeat suppression working; turn dedupe off to see every job again.

Ikerbasque shows only a handful of open calls at a time, so a run returns that handful, however high maxItems is.

Ikerbasque calls carry no location and no closing date in our test run (the fields are empty on all 5 rows), so location filters will find nothing; use keywords instead.

Data You'll Receive

• Call details: title, complete description (text and HTML) and posting date.
• Employer: Ikerbasque Basque Foundation for Science.
• Terms: locations, deadline, work arrangement, employment type and salary were empty or null on all 5 rows in our test run.
• Links and identity: the Ikerbasque call URL, plus a stable id and source for deduplication.

Sample output data

Here is an example job from this Actor (long text shortened for display):

{
  "schemaVersion": "nomad-agent-job-row-v4",
  "source": "ikerbasque",
  "id": "energy-economy-environment-society-modelling-leader-climate-policy",
  "url": "https://www.ikerbasque.net/en/calls/energy-economy-environment-society-modelling-leader-climate-policy",
  "title": "Energy–Economy–Environment–Society modelling leader for climate policy",
  "company": "Ikerbasque Basque Foundation for Science",
  "locations": [],
  "applicantLocations": null,
  "postedAt": "2026-09-28T07:42:27Z",
  "deadline": null,
  "description": "The Basque Centre for Climate Change (BC3) together with the Basque Science Foundation Ikerbasque invites applications for a senior researcher to serve as BC3’s E3S (Energy–Economy–Environment–Society) Modelling Leader. We are seeking an in… [truncated for display]",
  "descriptionHtml": "<p>The Basque Centre for Climate Change (BC3) together with the Basque Science Foundation Ikerbasque invites applications for a senior researcher to serve as BC3’s E3S (Energy–Economy–Environment–Society) Modelling Leader. We are seeking an… [truncated for display]",
  "workType": null,
  "salary": null,
  "employmentTypes": null,
  "hiringContacts": []
}

Ikerbasque Jobs API

Results are stored in a dataset that you can export as CSV, JSON or Excel, or read through the Apify API. Schedule it, or connect it to Make, n8n, Zapier or an MCP client to push new jobs wherever you need them. Each run also writes a RUN-SUMMARY record to its key-value store, with any input field that was mapped or ignored.

Support and Feedback

We improve these scrapers from your feedback. If something breaks or you need a filter:

• Open an issue on the Actor's Issues tab.
• If this Actor saved you time, a short review on the Store helps other people find it.

Run evidence

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: result $0.004; actor-start $0.02.

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 HTbbVE35zl4D2thff (2026-10-03, immutable build x1Ams4nV6SlwEz5SI). This is an observed example, not a guarantee that repeating it returns this row.

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": "ikerbasque",
  "id": "energy-economy-environment-society-modelling-leader-climate-policy",
  "url": "https://www.ikerbasque.net/en/calls/energy-economy-environment-society-modelling-leader-climate-policy",
  "title": "Energy–Economy–Environment–Society modelling leader for climate policy",
  "company": "Ikerbasque Basque Foundation for Science",
  "locations": [],
  "postedAt": "2026-09-28T07:42:27Z",
  "deadline": null,
  "description": "The Basque Centre for Climate Change (BC3) together with the Basque Science Foundation Ikerbasque invites applications for a senior researcher to serve as BC3’s E3S (Energy–Economy–Environment–Society) Modelling Leader. We are seeking an internationally recognised scientist with strong hands-on expertise in modelling and database development, and a demonstra… [truncated for display]",
  "descriptionHtml": "<p>The Basque Centre for Climate Change (BC3) together with the Basque Science Foundation Ikerbasque invites applications for a senior researcher to serve as BC3’s E3S (Energy–Economy–Environment–Society) Modelling Leader. We are seeking an internationally recognised scientist with strong hands-on expertise in modelling and database development, and a demons… [truncated for display]",
  "workType": null,
  "salary": null,
  "employmentTypes": null,
  "hiringContacts": []
}

Recent Ikerbasque research 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; 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 Ikerbasque research 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-v4 format: schemaVersion, source, id, url, title, company, locations, 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. 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: 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 the latest build. Read the dataset together with the run summary: a successful status alone does not show that every source was reached.

Restrictive filters or repeat-delivery suppression can produce zero results.

Product guides and related tools

• Guide and starter input on nomadagent.dev
• Product overview and public links
• Public setup guide
• Job Atlas job-data tools
• Oink personal job alerts
• How to filter remote jobs by real location eligibility

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
Job result (result)	$0.004	$0.0037	$0.003	$0.002	$0.002	$0.002
Actor start (actor-start)	$0.02	$0.02	$0.02	$0.02	$0.02	$0.02

For example, 100 × result, 1 × actor-start totals $0.42 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.

---

Independent tool. We built and run this Actor ourselves. Ikerbasque does not operate, sponsor or endorse it, and its name is used only to say which site the data comes from.