API reference

Every request is authenticated with your API key in the X-API-Key header. Keys are issued from your dashboard; keep them server-side and never ship them in client code.

curl https://api.joblistingsapi.com/v1/jobs \
  -H "X-API-Key: jla_live_your_key_here"

Set JLA_API_KEY in your environment, then fetch your first ten jobs. Each snippet runs as written.

curl https://api.joblistingsapi.com/v1/jobs?limit=10 \
  -H "X-API-Key: $JLA_API_KEY"

// Node 20+ (global fetch, no dependencies)
const res = await fetch(
  "https://api.joblistingsapi.com/v1/jobs?limit=10",
  { headers: { "X-API-Key": process.env.JLA_API_KEY } },
);
const { jobs, next_cursor } = await res.json();
console.log(jobs.length, "jobs;", next_cursor ? "more available" : "end");

# Python 3 — pip install requests
import os, requests

res = requests.get(
    "https://api.joblistingsapi.com/v1/jobs",
    params={"limit": 10},
    headers={"X-API-Key": os.environ["JLA_API_KEY"]},
)
res.raise_for_status()
data = res.json()
print(len(data["jobs"]), "jobs")

GET /jobs returns a page of JobV1 records. Combine any of the filters below; gated filters return 403 on plans that don't include them.

Two pagination modes. offset + total works on every plan and is simplest for shallow, one-off queries. Cursor pagination (Growth+) is stable by id — it won't skip or repeat records when the dataset shifts under you, which makes it the right choice for keeping a mirror.

For incremental sync, pass updated_since with your last successful sync timestamp. The recommended pattern for a local mirror is cursor + updated_since together:

# 1. Initial backfill — walk the cursor to the end
GET /v1/jobs?limit=100&updated_since=2026-06-01T00:00:00Z
  → { "jobs": [...], "next_cursor": "eyJpZCI6..." }
GET /v1/jobs?limit=100&cursor=eyJpZCI6...   # repeat until next_cursor is null

# 2. Incremental — only what changed since your last sync
GET /v1/jobs?limit=100&updated_since=2026-06-11T06:00:00Z&cursor=...

Every record is a JobV1. Taxonomy fields ship on every plan; description_html requires Starter+, and structured_description is Scale-only.

Limits are enforced per minute, per day, and per month. Every response carries X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset. Exceed a window and you get a 429 with a Retry-After header.

Errors use standard HTTP status codes with a JSON body describing what went wrong.

Prefer to poke at it live? The full OpenAPI reference, with a try-it console, is generated from the same schema.