Introduction

A REST API for job data normalised from 106 ATS platforms — search, bulk sync, company enrichment, and geocoding.

Jobo Enterprise is a REST API over job postings collected from 106 applicant tracking systems and job boards and normalised into a single schema. You get resource-oriented URLs, JSON bodies, conventional status codes, and one job shape across every endpoint — instead of building and maintaining a scraper per platform.

curl -G "https://connect.jobo.world/api/jobs" \
  -H "X-Api-Key: $JOBO_API_KEY" \
  --data-urlencode "q=software engineer" \
  --data-urlencode "page_size=5"

Base URL is https://connect.jobo.world; authentication is an X-Api-Key header. Get a key, then run the quickstart.

---

What you can do

Search jobs

Full-text and typed filtered queries with facets. Page-based and relevance-ranked, for anything a person is looking at.

Stream the feed

Cursor-paginated bulk delivery plus expired-id detection — the way to keep your own datastore in sync.

Enrich companies

Funding, leadership, ratings, technologies, and H-1B data. The profile endpoint needs no API key.

Resolve locations

Turn messy free-text locations into canonical city, region, country, and coordinates.

Auto Apply — a callback-driven API for submitting applications — is published as a contract preview and is not yet accepting traffic.

---

Start here

Quickstart

First authenticated response in about five minutes.

Core concepts

Job identity, freshness, and the expiry window that catches integrations out.

Client libraries

Official Python, Node, and .NET clients.

---

Two things to know up front

Filter values are matched literally. An unrecognised filter value — or a misspelled parameter name — is not an error. You get 200 with either zero results or silently unfiltered results. Send the canonical values from Enums and check total when a filter appears to have done nothing.

GET /api/jobs/expired only looks back 7 days. The feed returns active jobs only, so expired postings vanish rather than being flagged. A sync running less often than weekly will silently accumulate dead rows. See Core concepts.

---

Support

• Email — [e-mail]. Include the x-correlation-id from the response header; it identifies the exact request in our logs.
• Status — jobo.world/status for uptime and incidents.
• Changes — Changelog. The API is unversioned and additive; see Versioning.

Looking for data exports, outbound database feeds, or transformation pipelines? Those are dashboard features — see jobo.world/outbound-feed and jobo.world/pipelines.