Remote4Me Jobs API
Remote jobs. One place. No nonsense.
We built Remote4Me to make finding remote jobs easier. This API lets developers, job communities, and other useful projects access our public job listings in a simple JSON format.
No complicated setup. No paid subscription. No unnecessary hoops to jump through.
Just job data you can work with.
Quick start
Make a GET request to the endpoint below and you'll receive a JSON response containing available job listings.
What can you do with it?
You can use the API to:
- Build job discovery tools and personal job search projects.
- Create useful search interfaces for remote professionals.
- Explore available roles by keyword, country, category, or job type.
- Build integrations that link people back to the original Remote4Me job details.
Available data
The API returns a selection of public job information, including the following fields when available:
| Field | What it means |
|---|---|
title | Job title |
company | Hiring company |
location | Job location |
job_types | Available job-type information |
salary | Salary information, when available |
summary | Short job summary |
description | Public job description |
date_posted | Original posting date |
date_modified | Last modification date |
url | Link to the job details on Remote4Me |
One important thing: the url field points to Remote4Me's job-detail page. It is the link your application should use when sending someone to view a listing.
Search and filters
The API supports these query parameters:
page— choose which page of results to retrieve.per_page— choose how many results to request per page (max 50).
q— search using a keyword.country,category,job_type— filter by specific parameters.
Examples
To retrieve the first page of results with a keyword search:
https://remote4.me/wp-json/remote4me/v1/jobs?q=developerTo request the second page with 10 results per page:
https://remote4.me/wp-json/remote4me/v1/jobs?page=2&per_page=10Understanding the response
A successful response includes pagination and meta information such as:
success— whether the request succeeded.total— total matching jobs.page&per_page— current page number and requested size.total_pages— the number of pages available.jobs— the list of matching job listings.
Your application should check the response and handle empty results, missing optional fields, and request errors gracefully.
A few ground rules
We want the API to stay useful without turning it into a headache for everyone.
- Use the job-detail link: When displaying a listing, link to its
urlfield. This helps people read the full listing and keeps the original page accessible. - Don't mislead job seekers: Don't change details in a way that makes a listing inaccurate. Make it clear when the information came from Remote4Me.
- Keep your data fresh: Job listings expire. Refresh your data regularly and check the original job page before presenting an old listing as active.
- Don't hammer the endpoint: Cache responses where practical, use pagination, and avoid tight loops.
- Respect privacy: Use only the public information provided.
- Don't pretend to be Remote4Me: You can build your own project, but don't imply that Remote4Me officially partners with it unless that is true.
Questions or feedback? 💡
Do I need an API key?
No. The public jobs feed does not require an API key. We prefer keeping basic access straightforward. Please just use reasonable request volumes and cache your results.
Is the API guaranteed to be available forever?
No. We aim to keep the feed useful and reliable, but endpoints, response fields, and availability may change as Remote4Me evolves. Design your integration to handle errors rather than assuming perfect uptime.
Who is this API for?
Developers, independent builders, job communities, and anyone working on a useful way to help people discover remote jobs. Keep it honest, keep it useful, and keep the experience good for job seekers.