When your hiring data stops at the edge of one system, the manual work begins. That gap between what Flo knows about a hire and what your HRIS actually receives is exactly the kind of friction we stay focused on closing. Flo is the fastest shipping company in the legal talent industry, and this one came directly from conversations with recruiting teams who needed their integration data to tell the full story.
Several clients using our API integration flagged a consistent gap: internal fields captured on job applications were not making it through to their HRIS systems. These fields often hold critical information about a hire, things like custom classifications, internal codes, or firm-specific data points that matter downstream. When that information had to be re-entered or tracked separately, it created extra work and introduced opportunities for error.
The API was returning the information teams cared about most from the application, but not all of it. That was the problem we needed to fix.
We updated the API to include internal fields that are enabled on the job application. If your team has configured internal fields at the job application level, those fields now come through in the API response alongside the rest of your application data.
One boundary worth noting: internal fields that are configured for the candidate profile only are not included. The distinction is intentional. This export reflects job application data, and profile-only fields live in a different context.
Full technical documentation is available at docs.florecruit.com. A screenshot from the documentation is below.
For teams running an HRIS integration, this closes a real gap. The data your recruiters capture in Flo during the hiring process now flows through to the systems that depend on it, without manual re-entry in between.
If you rely on internal fields to drive downstream workflows, reporting, or system records, you can now trust that the API is giving you the complete picture of what was collected on the application.
This applies to any client using the API with internal fields enabled on job applications. If you are not seeing the fields you expect in your integration, check your field configuration at the application level and review the updated documentation. And if something still is not coming through the way it should, tell us specifically what is missing.