Job Opportunities API for Make
Search jobs in a Make scenario with the built-in HTTP module and iterate over the results.
- Official
- Open source
- No code
Our Make app (Watch New Jobs, Watch Closed Jobs, Search Jobs, Get a Job, Search and Get Companies, Make an API Call) installs through the invite link while it waits for a listing in Make's directory. The blueprint below uses only Make's built-in HTTP and Iterator modules. Every module run uses Make credits.
Set it up in 4 steps
You need a free API key (no card) — get one here.
Import the blueprint
Create a new scenario, open the ⋯ menu at the bottom of the editor, choose Import Blueprint and pick the downloaded .json file.
Add your key
Open the HTTP module and replace YOUR_API_KEY in the Authorization header. The module is already set to GET with Parse response on:
HTTP → Make a requestURL: https://api.jobopportunitiesapi.org/v1/jobs Method: GET Headers: Authorization = Bearer YOUR_API_KEY Query string: country = DE · q = engineer · remote = remote,hybrid · limit = 20 Parse response: YesCheck the Iterator
The Iterator's Array is {{1.data.data}}: the jobs array inside the parsed response. Each bundle after it is one job, so later modules can map {{2.title}}, {{2.company}}, {{2.apply_url}} and so on.
Optional: add Google Sheets → Add a Row, then schedule
Add Google Sheets → Add a Row after the Iterator, connect your Google account, and map Title, Company, Location, Apply URL and Posted to the Iterator's fields. Run once, then set the scenario schedule to once a day.
Example: for job boards
A regional board on a headless CMS runs the scenario every morning for its country, then sends each bundle to the CMS module with apply_url as the apply link, so new employer-direct roles appear without anyone copying them by hand.
Example: for AI agents
Put an AI module after the Iterator (or an Aggregator first) to classify roles, translate titles or draft a short summary per job before they reach the next tool. For an agent that searches on demand, use the MCP server.
Questions
Straight answers about plans, metering and what to show.
Does the HTTP module work on Make's free plan?
Yes. HTTP and Iterator are built-in Make apps rather than premium connectors; on the free plan, scheduled scenarios run at most every 15 minutes and each module run uses credits.
How do I get the next page?
The response carries next_cursor and has_more. Add a cursor query parameter mapped to next_cursor in a second HTTP module (or a repeater) when you need more than one page. For a daily job, one page is usually enough.
How is usage counted?
Every job row the API returns counts against your plan's monthly record allowance, exactly as a direct API call would. The free key has a small monthly allowance and needs no card, so start with small page sizes and a daily schedule rather than polling every few minutes. Your key's largest page size is in GET /v1/me (limits.max_page_size).
Where do applicants apply?
On the employer's own site. Every job carries apply_url, the employer's application page or applicant-tracking-system link. Job Opportunities API never sits between the candidate and the employer, so always use apply_url as the apply button.
Do I need to show any attribution?
Yes, one line where listings are shown publicly: a visible credit "Data: Job Opportunities API" linking to https://jobopportunitiesapi.org (see /terms — storing, displaying, reselling and redistributing within your key's plan limits are all allowed). In addition, jobs listed through Erioun for Teams carry an attribution field (for example "via Erioun for Teams") and a canonical_url: when attribution is present, show it with the listing and link to canonical_url.
Related integrations
Get a free API key
No card. The same key works for every integration on this site.