When your recruiting team connects Get on Board with an external ATS, internal HR system, or automation layer, the API can now cover more of the work that normally happens inside the company recruitment process: controlling job visibility, moving candidates through phases, and following clearer implementation guidance.
These improvements are available in the private API for company accounts with API access enabled. Your technical team can use them to keep external systems closer to the real state of your jobs and candidates in Get on Board.
What changed
The private API now includes dedicated endpoints for publishing and unpublishing jobs. Use them when your external system needs to restore visibility for an unpublished job or pause a live job without deleting it or rebuilding it from scratch.
We also added an endpoint for candidate movement. Your integration can move an application to another phase in the same process, including regular review phases, hired phases, and discarded phases when a valid discard reason is provided.
The technical API documentation has also been expanded so these workflows are easier to implement. It now gives clearer notes for job publishing flows, candidate phase movement, phase discovery, discard reasons, request examples, response examples, and endpoint relationships.
If your team is comparing a custom API workflow with native ATS exports, the Help article about what data is sent to an external ATS explains the business-level difference.
What you can do now
You can keep more recruiting operations synchronized between Get on Board and the tools your team already uses:
- Republish an owned unpublished job when it should become public again.
- Unpublish an owned live job when it should stop appearing publicly while remaining available for later.
- Move candidates between phases from an external ATS or internal workflow tool.
- Send discard reasons when moving candidates to a discarded phase.
- Use process and phase documentation to mirror your Get on Board pipeline more accurately.
These actions are especially useful when recruiters review candidates in one tool while another system owns workflow automation, reporting, or ATS synchronization.
Availability
These endpoints are live for companies with private API access. Standard API authentication, account permissions, subscription access, job ownership, candidate access, and process rules still apply. If your company is still evaluating access, see how to test Get on Board’s API before purchasing a plan.
Some decisions still belong in the Get on Board recruiter interface, especially when your team needs to review candidate context, adjust process setup, or manage actions that are not yet exposed through the API.
For endpoint names, payload fields, authentication, schemas, and implementation examples, use the API documentation.