Job-search products
Filter 1099, C2C, and W-2 contract opportunities using structured engagement evidence instead of keyword matching alone.
Build better tech job search with structured opportunity data.
Give your users precise filters for full-time and contract work, pay, location, and remote status. Radar connects duplicate listings, checks availability, and keeps the original source evidence with each record.
Production response excerpt
Real data. Explicit uncertainty.
Verified August 27, 2026 at 19:07 UTC. This is a dated excerpt, not a permanently live example.
Run the live playground →Request
GET /v1/preview/opportunities
?job_family=data
&job_subfamily=data_engineering
&job_class=etl_developer
&level=senior
&liveness_status=live
&limit=5Dated production record
{
"id": "ed30aafb-928f-455b-a5e7-174a87821127",
"title": "Ab Initio Developer",
"employer": "Info Origin Inc.",
"job_family": "data",
"job_subfamily": "data_engineering",
"job_class": "etl_developer",
"level": "senior",
"engagement_models": [],
"commercial_eligibility": "research_required",
"liveness_status": "live",
"last_verified_live_at": "2026-08-27T19:07:00.933559Z",
"sources": [{ "name": "Dice" }],
"evidence": [{
"label": "generic_contract",
"excerpt": "Contract"
}]
}More than a listing feed
Structured context that makes opportunity data usable.
Unknown values remain unknown. Evidence and provenance travel with the normalized record.
01
Canonical opportunities
Stable identities connect repeated and syndicated listings without discarding source evidence.
02
Technology taxonomy
Structured domain, family, class, level, management track, and specialization fields.
03
Contract type
1099, C2C, and W-2 are the three normalized contract types. Freelance and independent work map to 1099.
04
Commercial eligibility
Evidence-backed eligibility states prevent generic contract language from becoming false certainty.
05
Compensation
Normalized rates, units, and currency where the source actually provides them.
06
Geography
Remote status, country, region, city, and location restrictions in queryable fields.
07
Freshness and liveness
Publication precision, observation history, and current actionability are represented separately.
08
Source provenance
Publisher, source records, canonical destinations, and evidence remain inspectable.
09
Application destinations
Listing provenance stays intact while Radar resolves the actual application destination when it can be safely determined.
Use cases
Three ways to build with clean contract data.
Recruiting and staffing tools
Distinguish W-2 contract, independent eligibility, ambiguous contract language, currentness, and application destinations before someone acts.
Job boards, marketplaces, and automated products
Consume normalized opportunity records, stable IDs, liveness, and source provenance without rebuilding the acquisition and normalization layer.
Built with
Apache Airflow
Python
FastAPI
PostgreSQL
Docker
Next.js
Vercel
Cloudflare
GitHub
Stripe
Developer experience
One schema. Structured filters. Stable IDs. Provenance.
REST API · MCP · OpenAPI. Use the same read-only account and API key across both integration paths.
Run a real query
Open the developer explorer, change the filters, and inspect the authenticated response next to generated cURL, JavaScript, and Python.
A few things worth knowing
Frequently asked questions
How Radar API works, where the data comes from, and how to get started.
Have another question? Get in touch →What is the difference between RadarJobs and Radar API?
RadarJobs is the application for finding and tracking technology work, with particularly deep contract-tech filters and evidence. Radar API gives developers structured opportunity records for their own products and workflows through REST and MCP. API access has its own plans and usage limits; RadarJobs access does not include an API plan.
Where does Radar get its job data?
Radar brings together technology opportunities published across job boards and marketplaces, including LinkedIn, Indeed, Dice and Upwork. It organizes them into a consistent format, connects duplicate listings and preserves source attribution and links to the original postings.
How fresh are the listings?
Radar refreshes its inventory and rechecks availability on an ongoing basis. A listing’s published date tells you when it was posted; its last-checked time tells you when Radar last verified availability. Check those timestamps for the specific opportunity you’re viewing, since refresh timing varies by source.
What does Radar add to the original job posting?
Radar structures role, seniority, contract type, pay, location and remote-work information so you can filter consistently across sources. It retains supporting evidence and source links, connects repeated listings and tracks availability. Fields the source does not supply remain clearly identified as unknown.
How are duplicate jobs handled?
Radar connects records it identifies as the same opportunity, preserving their source information instead of presenting each source record as a separate job. Different openings with similar titles can still appear separately.
What if a listing is missing, incorrect or no longer available?
Send us the original posting URL and a short description of what you found. If you have a Radar listing link or opportunity ID, include that too so we can investigate the right record. You can also suggest a source you would like Radar to cover.
Contact Radar support →Which fields can I filter on?
The API supports structured filters for technology roles and seniority, engagement model, remote status, location, pay, source and freshness. Records include stable opportunity IDs, source provenance and availability information. The API reference lists the exact supported fields and values.
Explore the API reference →Can I try the API without purchasing RadarJobs?
Yes. You can inspect the public preview, create a Radar API account and get an API key under the free plan. You do not need a resume, a RadarJobs profile or a RadarJobs purchase. Current allowances and paid options are shown on the API pricing page.
View API plans →How do I retrieve updates without downloading everything again?
Use the API’s changed_since filter for changed opportunities, first_seen_after for newly observed opportunities, and cursor pagination to work through a result set. Stable IDs let you update records in your own system. The documentation explains usage accounting and retry behavior.
Read the integration guides →Can I use Radar data in my own product?
Radar API is designed for integrations such as job-search products and internal tools. Your use is governed by the applicable plan, terms and source requirements. Contact us about bulk redistribution, a custom data feed or licensing requirements so the delivery and permitted use can be agreed for your project.
Review API acceptable use →