CleanJobData
All feed pages

City feed

Paris job listings API

La French Tech in one stable API. Paris jobs from Greenhouse, Lever, Ashby, and Workable — international startups, scale-ups, and tech companies operating out of France.

The Problem

Parisian tech roles are often buried in French-language job boards that are difficult for international products to parse and normalize.

Our Solution

We normalize Paris job data into a consistent schema, making it easy to build international or expat-focused products for the French market without custom language handling.

What you're getting

Source
Direct postings from ATS and employers career sites.
Companies
This batch includes roles from Spgi, Regeneron, voize, voize GmbH, and OpenAI, and more.
Volume
Preview shows 10 roles (limit 10, with more pages available). Authenticate and paginate to explore the full Paris index.
Filters
Filter by country, state, city, title, remote setting, experience level, and salary. Full filter reference in the Jobs API docs.

At a glance

  • Strong representation of Paris's startup and scale-up scene — companies building in fintech, SaaS, and deep tech.
  • Normalized French location data covering Paris arrondissements and surrounding tech hubs like Saclay.
  • Consistent schema for French job boards and global products adding a France tab.

When you are ready for every filter, validation rule, and response field, use the Jobs API reference.

Global Platform Scale

1,078,026

Total Jobs Indexed

+1,016

Added Past 24h

+525,356

Added Past 30 Days

20,093

Employers

Example request

Same query as the playground, as cURL. Use your real key on the server only.

Jobs API referenceFull playground
curl -X GET "https://api.cleanjobdata.com/jobs?state_id=4816" \
  -H "Authorization: Bearer YOUR_API_KEY"

How to integrate

1. Get an API key

Sign up for CleanJobData, open the dashboard, and create or copy your API key. Send it as Authorization: Bearer <token> on every request (server-side only in production—never expose keys in mobile apps or public repos).

2. Query Paris listings

Start from state_id 4816 (Paris), then add city_id, title, or remote filters as needed.

Use a modest limit while prototyping, default to sort_by=published for recency, then follow pagination.next_page for large imports. Back off with exponential retry if you hit rate limits.

3. Shape data for your product

Choose which fields you render in job cards versus what you index for search. On list endpoints, trim payloads with fields, include_fields, or exclude_fields, and only request description when you truly need full text on list views.

FAQ

Can I use this in production for a paid job board?
Yes—that is the intended use case. Pick a plan that matches your query volume, keep keys on your server, cache responses where it makes sense, and follow the pagination contract for large imports. Contact support if you need higher limits or contract terms.
How do I narrow results beyond Paris?
Add state_id, city_id, or location, combine with a keyword in title, or filter remote-only roles. Each option is spelled out in the Jobs API reference (/docs/api/jobs) with validation rules you can copy into code.
What rate limits or quotas should I expect?
Limits depend on the plan you choose. Higher tiers support more queries per second so job boards with heavy traffic or large sync jobs stay smooth. Paginate with the API's cursors and retry politely if you occasionally receive a 429 response.
How is this different from scraping job boards myself?
We normalize employers, locations, salary text, and remote flags into one schema, refresh listings continuously, and expose stable HTTP filters. You spend time on product and UX instead of repairing scrapers every time a site changes markup.
How fresh is the job data?
We refresh listings continuously from our sources, so you are not stuck with a stale export. Use sort_by=published when you want the newest posts first, and run incremental syncs on a schedule that matches how often your job board should update.
Do you return full job descriptions on list endpoints?
Descriptions are available but not included in lightweight list responses by default. Request them explicitly when building detail views so list pages and mobile clients stay fast and cheap to render.