Overview

Updated September 8, 2026

The Orbit API lets an account read its own jobs and put them wherever it wants them: a careers page on your own domain, an intranet, a partner site. Wipperoz is the production tool; you are the origin. Your domain gets the search equity, your brand gets the candidate, and we do not sit between you and your hiring.

What it does

• Reads your jobs. GET /v1/jobs returns the roles your account has published, with closed and expired ones marked as such, so a page you built can render its own closed state instead of breaking links it already published.
• Hands candidates to the hosted apply page. Every job carries an applyLink. Send candidates there. The apply page records that they came from your site, so applications from your careers page and from Wipperoz are separable in your analytics.
• Takes your jobs in. POST /v1/jobs creates a role from your own system — an ATS, an internal tool — as a draft, and POST /v1/jobs/{jobId}/publish takes it live. Editing and closing are there too, so a role that changes upstream can change here.
• Stays yours. Every response is scoped to the account whose key made the request. There is no cross-account read, no cross-account write, and no “all jobs” endpoint.

What it does not do

• Take applications over the API. The consent a candidate gives on the hosted apply page is what lets Wipperoz mint their Virtual CV and email a claim invitation. A form you built and posted to us would have us acting on consent we never saw. Link to applyLink instead; it is the whole design.
• Hold your job-board credentials or post to boards for you. Distribution to boards is a feed you point a board at, not credentials you hand us.
• Publish without being asked. Creating a role and publishing it are two calls, because publishing spends your credits. Nothing goes live, or costs anything, on a call you did not make.

Who it is for

• A recruiter or an engineer wiring a careers site to the roles an account publishes in Orbit.
• An agency evaluating whether Orbit fits an existing ATS or MCP workflow.

What you need

1. An Orbit account with at least one published role.
2. An API key, created in Orbit → Settings → API keys, with the scope that matches the job: read jobs for a careers site, read and manage jobs to post roles as well. The next page walks through it.

Base URLs and versioning

Every path starts with /v1. A public API consumed by other people’s sites cannot change in place, so a breaking change will arrive as /v2 with /v1 still answering.