Jobs · head-to-head
Reed vs Upwork
Reed's Jobseeker API searches the UK's reed.co.uk job listings by keyword, location, salary band, and contract type, returning employer and description data for each match. Access needs a free registered API key sent as the HTTP Basic-auth username, confirmed live by a genuine 401 challenge that also echoed a wildcard CORS header back.
Upwork's public API is now a single GraphQL endpoint covering the freelance marketplace it once exposed as separate REST resources — job postings, proposals, contracts, time tracking, and messaging — authenticated via OAuth 2.0 (Authorization Code Grant with PKCE). A live probe confirmed the stored docs URL still redirects to the current GraphQL reference and that the gateway itself returns a genuine 401 challenge to unauthenticated calls, with no Access-Control-Allow-Origin header on either that request or a follow-up preflight. Registering an application is free, gated only by Upwork's own review and a 300-request-per-minute-per-IP rate limit.
| Reed | Upwork | |
|---|---|---|
| Authentication | API Key | OAuth |
| Pricing | free | free |
| Formats | JSON | JSON, GraphQL |
| CORS | yes | no |
| HTTPS | Yes | Yes |
Reed supports CORS, while Upwork doesn't — pick Reed for direct browser calls.