Product

Jobo for REST API

Job data in a single API call.

The Jobo API serves live job listings over HTTPS, normalised into one schema whichever applicant tracking system or career site they came from. Search returns filtered, relevance-ranked pages; Feed streams the whole matching set in batches of up to 1,000 with a resumable cursor; a third endpoint lists recently expired job IDs so a copy of the data stays current. Authentication is an API key in the X-Api-Key header.

REST API logoREST APIYour first request
bash
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"

What can you do with the REST API integration?

Search live jobs or pull the bulk feed with one HTTP request. Everything else on this page is built on it.

01

One schema for every source

A job from Greenhouse and a job from Workday come back in the same shape: title, company, locations, compensation, employment type, work model, experience level and the listing URL.

02

Search and Feed

Search answers a filtered question a page at a time. Feed walks every matching job with a cursor, for backfills and nightly syncs.

03

Expired jobs, free

GET /api/jobs/expired returns recently closed job IDs so a downstream copy can drop them. It never consumes credits.

04

Pay for jobs, not requests

Billing is per job returned. An empty result, a failed request and a rate-limited request cost nothing, and a single job fetched by ID is unmetered.

05

A sandbox that costs nothing

A sandbox key returns fictional jobs for free, so an integration can be wired up and tested before it touches a balance.

How do you connect REST API to Jobo?

One-time setup. After this, the data keeps itself current.

  1. 1

    Create an API key

    Sign up, open Developers → API Keys in the dashboard and create a key. New accounts start with a $5 balance and need no credit card. The key is shown once, so export it straight away.

    bash
    export JOBO_API_KEY="your_api_key_here"
  2. 2

    Make a request

    Send the key in the X-Api-Key header. This searches for software engineering jobs and returns the first five.

    bash
    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"
  3. 3

    Read the response

    Jobs come back in the jobs array. Response headers report what the request cost and what is left: X-Credits-Deducted, X-Credits-Balance, and the rate-limit headers.

  4. 4

    Move to Feed for volume

    To copy many jobs rather than answer one query, POST your filters to /api/jobs/feed, then send back only the cursor from each response until has_more is false.

    bash
    curl -X POST "https://connect.jobo.world/api/jobs/feed" \
      -H "X-Api-Key: $JOBO_API_KEY" \
      -H "Content-Type: application/json" \
      -d '{"sources": ["greenhouse"], "batch_size": 1000}'

What goes wrong with REST API, and how do you fix it?

The things people actually hit when running Jobo in REST API.

A filter returns 200 with zero jobs
Filter values are lowercase, hyphenated and matched exactly, and an unrecognised value is not an error. Check the spelling against the documented values: full-time rather than full_time, onsite rather than on-site.
HTTP 402 on a search
The balance cannot cover the request. The check runs before the request and prices the whole requested page, so retrying fails identically. Top up, or lower page_size.
HTTP 429 or 503
Wait for the number of seconds in the Retry-After header, then retry. These are the only responses worth retrying automatically.
The feed returns 409 feed_cursor_restart_required
The cursor can no longer be continued. Discard it and start a new scan; retrying the same cursor will not succeed.

How do you get the most out of REST API?

  • Keep the key on a server. Anything that runs in a browser can be read by whoever opens the page.
  • Use Feed, not paged Search, when you want every matching job. Feed bills a job once per 30 days however often it is delivered again.
  • Persist the feed cursor after every batch so a crashed sync resumes instead of starting over.
  • Set a response timeout of at least 120 seconds on feed requests.

Start pulling live jobs into REST API

One API key covers every integration, and the same job index sits behind all of them.