openData Studio中文
Categories

Jobs & Careers apps and their data APIs

Job boards and career apps — the search, listing, application and profile APIs behind every vacancy feed.

Job-board and career apps form the catalog's largest category, and they share a common spine: a search feed, a posting detail, an apply write and a candidate profile. Indeed personalises the hunt with POST /v1/jobs/recommendations and employer messaging, Naukri runs OTP sign-in then GET /v1/jobs/search plus saved jobs, and OCC covers Mexico's market behind an OAuth token with /v1/me/resume.

Differentiation sits on top of that spine. Glassdoor exposes employer reviews and salary estimates, InfoJobs Brasil returns a per-posting match score, hh shows who viewed a CV and reveals recruiter phone numbers, LinkedIn serves profile-view analytics, and Glints pairs its GraphQL search with a recruiter chat socket. Auth is consistently OTP or OAuth2 session tokens; the apply endpoints always require sign-in.

Frequently asked questions

What do the job-app APIs in this category have in common?

All thirteen expose the same four-stage flow: a paginated job search (GET /v1/jobs/search or a GraphQL equivalent), a posting detail lookup, an apply or quick-apply write, and a candidate profile resource. On top of that spine each board adds its own data — salary estimates, match scores, employer reviews or recruiter chat.

Which job apps expose salary data?

Glassdoor returns salary estimates from POST /v1/salaries/estimates; most search feeds also carry advertised pay bands — Naukri, apna, Shine, Pintarnya, OCC and InfoJobs all return min/max salary fields per posting where employers disclosed them.

How do these apps authenticate jobseekers?

The common pattern is phone-number OTP (apna, Shine, Naukri, Pintarnya) or OAuth2/email sign-in (Indeed, LinkedIn, OCC, hh, InfoJobs, Glassdoor, Glints, Jobstreet). Anonymous browse usually works for search; apply, profile and message endpoints always require the session token.

Apps in Jobs & Careers