shipapis
StarSubmit an APISubmit API

Jobvetta vs X (Twitter) API

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

APIJobvettaREACHABLE100X (Twitter) APIHEALTHY96
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms85279
P95 · ms2151148
AuthapiKeyapiKey
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified
Free tierFree tier — API key required
Rate limitUnpublished
In directory since2026-07-252026-07-05
operationalpartialdownno data

Jobvetta vs X (Twitter) API: common questions

Which is more reliable, Jobvetta or X (Twitter) API?

Both are neck-and-neck — Jobvetta and X (Twitter) API 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, Jobvetta or X (Twitter) API?

Jobvetta has the lower median latency in our checks — Jobvetta responds in 85 ms versus X (Twitter) API at 279 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 Jobvetta and X (Twitter) API need an API key?

Both ask you to authenticate — Jobvetta uses an API key and X (Twitter) API uses an API key. Each key is free to obtain; the Auth and Card-required rows above spell out the signup terms.

Can I call Jobvetta and X (Twitter) API from the browser?

Yes — both Jobvetta and X (Twitter) API send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are Jobvetta and X (Twitter) API free for commercial use?

Jobvetta has unclear commercial terms, and X (Twitter) API 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.