shipapis
StarSubmit an APISubmit API

jobdata API vs Landing.jobs

Same instrument, two spec sheets — measured, not claimed.

APIjobdata APIHEALTHY91Landing.jobsHEALTHY91
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms640645
P95 · ms13454235
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

jobdata API vs Landing.jobs: common questions

Which is more reliable, jobdata API or Landing.jobs?

Both are neck-and-neck — jobdata API and Landing.jobs each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, jobdata API or Landing.jobs?

jobdata API has the lower median latency in our checks — jobdata API responds in 640 ms versus Landing.jobs at 645 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.

Do jobdata API and Landing.jobs need an API key?

Landing.jobs needs no key, while jobdata API requires a free API key. If you want to start calling without signup, reach for Landing.jobs first.

Can I call jobdata API and Landing.jobs from the browser?

Only Landing.jobs is browser-friendly — it returns CORS headers over HTTPS. jobdata API needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are jobdata API and Landing.jobs free for commercial use?

jobdata API has unclear commercial terms, and Landing.jobs has unclear commercial terms. We track service terms and the data license as separate fields — see the Commercial use and Data license rows above, and confirm both before shipping either in a paid product.