When your company uses an external ATS integration such as Lever, Greenhouse, or Ashby, Get on Board sends supported applications with the standard candidate and application data that the connected ATS can receive.
This article explains the business-level behavior. For field-level API details, use the API documentation or your ATS provider’s documentation.
Data that is sent
In general, ATS exports can include:
- Candidate name and contact details
- Resume or CV data when the integration can send it
- The job or posting the candidate applied to
- Application context supported by the provider
The exact fields vary by ATS:
- Lever supports candidate exports through Lever’s Data API and can include additional mapped fields when your setup supports them.
- Greenhouse receives the standard candidate details and resume information supported by its integration flow.
- Ashby receives standard application fields such as name, email, phone, and resume. It can also receive answers to synced Ashby application-form questions when they use supported text, boolean, single-select, or multi-select fields. If your Ashby form requires unsupported fields, missing answers, changed choices, or mandatory surveys, the export may need configuration changes before it succeeds.
Data that is not sent
Superpower AI insights, smart filters, scorecards, and other Get on Board-only review tools stay inside Get on Board. Mandatory Ashby surveys are not part of the native ATS export.
If your team needs a custom data flow beyond the native ATS integration, check whether your plan includes API access and review the API documentation.
More from Integrations and developer tools
