JOB LISTINGS · SPAIN
InfoJobs Spain Jobs | Salaries & Contracts
Scrape InfoJobs Spain job listings by keyword: title, company, city, salary, contract type, schedule, remote or hybrid arrangement, posting date and link, with optional description excerpts.
About this data
Scrape InfoJobs Spain job listings by keyword: title, company, city, salary, contract type, schedule, remote or hybrid arrangement, posting date and link, with optional description excerpts. Export JSON, CSV or Excel.
From the actor’s Apify Store listing. The per-call endpoint may return a bounded subset; its own description is below.
Buy per call over x402
One endpoint at api.ssh.autos. Each call is one JSON POST, paid in USDC with no account or API key, and answered in the same HTTP response.
POST /v1/es/infojobs/jobs
Records include job IDs, titles, companies, locations, contract types, workday labels, posting dates and source URLs.
Fetch one keyword search page with up to 5 InfoJobs Spain jobs.
Work mode and salary text, numeric bounds, currency and period appear when published.
Calls do not request job details, candidate profiles or company profiles.
Input
Send a JSON body to POST https://api.ssh.autos/v1/es/infojobs/jobs.
| Field | Type | Required | Notes |
|---|---|---|---|
keyword | string | optional | 1–200 characters; default "programador" |
maxItems | integer | optional | 1–5; default 5 |
Returned fields
The answer is JSON: records, a list of up to 5, and summary, the run status and counts. Each record has these 15 fields; a field the source does not publish comes back null.
15 fields per record
| Field | Type | Notes |
|---|---|---|
jobId | string | — |
company | string | — |
location | string | — |
city | string | — |
salaryText | string | Text rendered from disclosed structured salary bounds, currency and period; null when undisclosed. |
salaryMin | number | — |
salaryMax | number | — |
salaryCurrency | string | — |
salaryPeriod | string | — |
contractType | string | — |
workday | string | — |
workMode | string | — |
postedAt | string | — |
url | string | — |
descriptionExcerpt | string | Up to 1200 characters of the search description as published; null when disabled or the listing has no description. |
Example call
npx agentcash@latest fetch https://api.ssh.autos/v1/es/infojobs/jobs -m POST -b '{"keyword": "programador", "maxItems": 5}'The example values come from the API spec or the actor’s own sample input. Running it is a paid call.
What is and isn’t charged
You pay the call price for
- An answer, including a definitive “not found” or an empty result.
- Confirmed no matches returns records: [] (charged: it is an answer).
Free
- Invalid input (422), busy (503), source failure (502), timeout (504) and calls whose client hung up are never charged.
- Invalid input and source failures are not charged.
Prefer a subscription? Run it on Apify
This data source is a public actor on the Apify Store: InfoJobs Spain Jobs Scraper | Salaries & Contracts. Run it with your Apify account and plan for larger, scheduled or exported runs; it may offer more input options than the per-call endpoint.
How x402 payment works
- Your client sends the request. The API answers
402 Payment Requiredwith the price and where to pay. - The client pays from its own wallet: USDC on Base or Solana over x402, or over MPP on Tempo. No account, sign-up or API key.
- The client retries with the payment attached and gets the JSON answer in the same call. You are only charged for answers.
The AgentCash CLI in the example does all three steps for you and pays from your AgentCash wallet. Any x402 or MPP client works the same way.
Machine-readable: openapi.json · llms.txt