Lazee Jobs API

A scheduled sync runs every 2 days (about every 48 hours). It fetches every tracked board in full and brings the dataset in line with what the boards list at that moment:

• New postings are added with first_seen_at set to the sync time.
• Postings whose title, location, pay or URL changed are rewritten and get a new synced_at.
• Postings the board no longer lists are deleted. They return 404 from then on.
• Unchanged postings are left alone, so synced_at tells you when a job last actually changed.

Every request carries an API key in a request header. Keys are issued by the marketplace when you subscribe, and the exact header name follows the marketplace's convention. The examples on this page use X-API-Key as a stand-in; swap it for the header shown on your subscription page.

GET https://<announced-at-launch>/v1/jobs?role=frontend
X-API-Key: YOUR_API_KEY
Accept: application/json

Keys are for server-side use. Do not ship one inside a browser or mobile app; proxy the call through your own backend instead.

Base URL: https://<announced-at-launch>/v1 (placeholder until launch). All endpoints are GET and return application/json.

{
  "data": {
    "total_jobs": 1284,
    "companies": 87,
    "platforms": 10,
    "last_synced_at": "2026-10-22T02:00:00.000Z",
    "refresh_interval_hours": 48
  }
}

Every parameter is optional and they combine with AND. A parameter that accepts several values matches any of them (OR within the parameter). Unknown parameters are ignored; known parameters with a bad value return 400.

Response: an array under data plus a meta object.

{
  "data": [ /* job objects, see "The job object" */ ],
  "meta": {
    "page": 1,
    "limit": 25,
    "total": 1284,
    "total_pages": 52,
    "last_synced_at": "2026-10-22T02:00:00.000Z"
  }
}

The same object appears in list results and from the single-job endpoint (wrapped in data). Field names are snake_case; timestamps are ISO 8601 in UTC.

{
  "id": "cmh3k9x2a0001qzk8f1g7h4jd",
  "platform": "GREENHOUSE",
  "company": "Stripe",
  "title": "Backend Engineer, Payments",
  "location": "San Francisco, CA / Remote (US)",
  "workplace": "remote",
  "department": "Engineering",
  "employment_type": "Full-time",
  "compensation": "$180,000 – $250,000",
  "url": "https://boards.greenhouse.io/stripe/jobs/1234567",
  "posted_at": "2026-10-21T09:15:00.000Z",
  "first_seen_at": "2026-10-22T02:00:00.000Z",
  "synced_at": "2026-10-22T02:00:00.000Z",
  "role": "backend",
  "level": "mid",
  "regions": ["us"]
}

These are the keys the filters accept today, generated from the same taxonomy the job board uses. Fetch /filters at runtime rather than hard-coding them; new keys may be added, existing ones are not renamed within /v1.

{
  "data": {
    "role":      [{ "key": "backend", "label": "Backend" }, ...],
    "level":     [{ "key": "senior", "label": "Senior" }, ...],
    "region":    [{ "key": "india", "label": "India" }, ...],
    "workplace": [{ "key": "remote", "label": "Remote" }, ...],
    "platform":  [{ "key": "GREENHOUSE", "label": "Greenhouse" }, ...],
    "company":   ["Airbnb", "Anthropic", "Stripe", ...]
  }
}

Results are paged with page and limit. The default page size is 25 and the maximum is 100. meta.total is the number of jobs matching your filters and meta.total_pages is the last page you can request; asking for a page past it returns an empty data array, not an error.

Ordering is by posted_at then id, so paging through a result set between two syncs is stable. A sync in the middle of a long crawl can shift rows; compare meta.last_synced_at across pages and restart if it changed.

Errors use standard HTTP status codes and a JSON body with a machine-readable code and a human message. Validation errors also name the offending param.

HTTP/1.1 400 Bad Request
Content-Type: application/json

{
  "error": {
    "code": "invalid_parameter",
    "message": "level must be one of: intern, entry, mid, senior, staff, manager",
    "param": "level"
  }
}

Plans, quotas and prices are set on the marketplace and published at launch. Expect a free tier sized for prototyping and paid tiers by monthly request volume. Rate limits are enforced per key; a 429 carries a Retry-After header.

Because the data only changes every 2 days, most integrations need far fewer requests than they first assume. One full pull per sync, filtered to what you need, is usually enough.

Senior backend or full-stack roles, remote, in India:

curl "https://<announced-at-launch>/v1/jobs?role=backend,fullstack&level=senior&region=india&workplace=remote&limit=10" \
  -H "X-API-Key: YOUR_API_KEY"

Engineering roles mentioning “payments”, posted this month, with a listed pay range:

const params = new URLSearchParams({
  q: "payments",
  role: "engineering",
  has_compensation: "true",
  posted_after: "2026-10-01",
  limit: "50",
});

const res = await fetch(`https://<announced-at-launch>/v1/jobs?${params}`, {
  headers: { "X-API-Key": process.env.LAZEE_JOBS_API_KEY },
});
if (!res.ok) throw new Error(`Jobs API ${res.status}`);

const { data: jobs, meta } = await res.json();
console.log(`${meta.total} jobs, refreshed ${meta.last_synced_at}`);
for (const job of jobs) console.log(job.company, "—", job.title, job.url);

Entry-level and intern roles in the US on Ashby or Lever:

import os, requests

resp = requests.get(
    "https://<announced-at-launch>/v1/jobs",
    params={"platform": "ASHBY,LEVER", "level": "entry,intern", "region": "us", "page": 1},
    headers={"X-API-Key": os.environ["LAZEE_JOBS_API_KEY"]},
    timeout=15,
)
resp.raise_for_status()
body = resp.json()

for job in body["data"]:
    print(job["company"], "-", job["title"], job["url"])
print("page", body["meta"]["page"], "of", body["meta"]["total_pages"])