Skip to content

HrFlow.ai alternative

HireLayer vs HrFlow.ai: stateless endpoints or a data platform

HrFlow.ai and HireLayer are both French and both output ROME occupation codes. HrFlow.ai is built around storage: every parsed CV becomes a Profile inside a Source, and search and scoring run on those stored records. HireLayer returns the JSON and keeps nothing if you ask it to, with public per-credit prices.

API requests processed
2M+
In production since
2024
Parse success rate
~99.7%

A Paris-based HR data platform with parsing, tagging, searching, scoring and AI agents built around stored profile and job objects.

HireLayerHrFlow.ai logo
Parse a CV
HireLayer: Returns JSONHrFlow.ai: Creates a stored Profile
Synchronous result
HireLayer: DefaultHrFlow.ai: Enabled per Source by HrFlow
Where parsing runs
HireLayer: 🇫🇷 ParisHrFlow.ai: AWS in Europe
Connectors
HireLayer: On requestHrFlow.ai: 200+ claimed, Zapier app

Migration from HrFlow.ai

Low
Public sources checked on 15 October 2026 · 24 sources

The differences that matter between two French APIs

ROME support does not separate these two. Where parsing runs, architecture, scope and commercial terms do.

  1. 01

    Stored objects vs request–response

    HrFlow’s parsing endpoint requires a source_key, and parsing a resume creates a Profile stored in that Source; you then configure retention or archive it. HireLayer’s parser needs only the file. Set do_not_store_data=true and the parsed data is not retained.

  2. 02

    Real-time parsing

    HrFlow answers 201 with the result when real-time parsing is enabled, or 202 when the file goes to its parsing queue. Real-time parsing has to be enabled for the Source by HrFlow’s team. HireLayer’s Resume Parser is synchronous for every account.

  3. 03

    Platform breadth

    HrFlow offers searching, scoring, embeddings, upskilling, AI agents and more than 200 connectors (Bullhorn, Greenhouse, Teamtailor, Zapier, Make…). HireLayer has six products, an MCP server and a short list of ready-made integrations on its integrations page, and builds other connectors on request.

  4. 04

    ROME depth

    Both return ROME codes. HrFlow’s ROME 4.0 taggers go down to the 12,107 job-title appellations through its Tagging API. HireLayer returns a ROME code with a prediction score inside every parse.

HrFlow.ai and HireLayer on 30 unseen resumes

On 15 October 2026 we sent 30 fictional resumes in 11 languages, written after our latest release and never seen by our team, to HireLayer and to HrFlow.ai’s Gaia model, the one HrFlow.ai presents as its most accurate. Every printed value was checked in the raw JSON, under scoring rules frozen before the first call.

Measured on 30 resumes, against GaiaHireLayerHrFlow.ai
Printed values returned exactly (of 1,886)95.2%84.5%
Current jobs kept current (of 38)3824
Language levels returned91.7% rightNone
Postal codes as printed (of 21)2115
Time to result, median23.5 s13.6 s, queued
  1. Ongoing jobs stay ongoing

    “Halen”, “obecnie”, “heden”, “Present”: HireLayer kept all 38 current jobs open. Gaia closed 14 of them, usually at the end of the start year.

  2. A CEFR level for every language

    Levels written as “modersmål”, “aktivně” or “gute Kenntnisse” come back as CEFR levels with HireLayer. HrFlow.ai returned the language names with an empty level.

  3. The address the candidate wrote

    HireLayer returned every postal code as printed. HrFlow.ai replaced several with a neighbouring code, such as 75-601 for 75-616 in Koszalin.

  4. Switch without rewriting your integration

    HireLayer answers in HrFlow.ai’s JSON format: point the HrFlow SDK at HireLayer’s HrFlow.ai-compatible API.

The same Turkish resume (cv26: “Eyl 2024 – Halen”, “İyi (B2)”): the current job and the languages as each API returned them.

HireLayerwork_experiences[0], languages
"work_experiences": [{
  "job_title": "Grafik Tasarımcı",
  "company_name": "Pikselhane Kreatif Ajans",
  "start_date": "2024-09-01",
  "end_date": null,
  "currently_active": true
}],
"languages": [
  { "language": "Türkçe", "level": "Native or Bilingual (C2)" },
  { "language": "İngilizce", "level": "Professional Working Proficiency (B2)" },
  { "language": "Almanca", "level": "Introductory Proficiency (A1)" }
]
HrFlow.aiGaia · profile.experiences[0], languages
"experiences": [{
  "title": "Grafik Tasarımcı",
  "company": "Pikselhane Kreatif Ajans",
  "date_start": "2024-01-01T00:00:00",
  "date_end": "2024-12-31T00:00:00"
}],
"languages": [
  { "name": "almanca", "value": null },
  { "name": "ingilizce", "value": null },
  { "name": "türkçe", "value": null }
]

Where your CVs are processed, and how HireLayer plugs in compared with HrFlow.ai

HireLayer parses in France and keeps AI processing in the EU. Fast mode is in beta and connectors are built on request: the statuses below say exactly that, next to what the other vendor documents.

AI and hosting in France 🇫🇷

HireLayer·where a CV goes

Parsing

Paris data center, France

Files & photos

Stored in Paris

AI models

In-house AI pipeline, processed in the EU

JSON response

Back to your backend; do_not_store_data available

HrFlow.aias documented

Parsing
Partly, with limits:AWS in Europe; the provider may change it without client approval; no France commitment
Documents
Partly, with limits:Each parse creates a Profile in a Source; async parsing keeps data at least 24 h
AI models
Not verified:Own models described; region and any third-party LLM not documented

Fast mode

HireLayer

Beta:Fast mode in beta, enabled per account on request; no published timing

We do not publish timings for the beta. Ask for access and measure it on your own CVs before relying on it.

HrFlow.ai logo

Available:Four parsing models from QuickSilver (500 ms p95 stated) to Chronos (5 s), vendor figures

Integrations

HireLayer has no marketplace apps yet. Every API works from any HTTP step, with an optional webhook on each parse, and the integration guides show the setup for Make, Power Automate, Greenhouse, Workday, Salesforce and other tools. Native connectors are built by our team on request.

HrFlow.ai statuses come from its own documentation and the tools’ marketplaces. “Via API” means no connector exists but the API can be called from that tool.

Ask for a connector
Connector availability: HireLayer and HrFlow.ai
ToolHireLayerHrFlow.ai logo
ATS / HCM appsOn request:Available:Open-source connectors for Bullhorn, Greenhouse, Lever, Recruitee, SmartRecruiters, Teamtailor, Workable and more
ZapierOn request:Available:Zapier app with resume parsing actions
MakeOn request:Available:Verified Make app maintained by HrFlow.ai, with 29 modules
SalesforceOn request:Available:Open-source connector in HrFlow’s catalog; no AppExchange listing found
SAP SuccessFactorsOn request:Available:Open-source connector in HrFlow’s catalog
WorkdayOn request:On request:“Premium” connector available on request
TableauOn request:Via API only:No connector; possible through the API

Feature comparison

HrFlow.ai cells come from its developer documentation, help center, trust center and website. Pricing figures are marked as archived where the live page is gone. Highlighted rows show where one side has a documented edge.

HireLayer edge
9
HrFlow.ai edge
10
Criteria
35
  • Available
  • Partly, with limits
  • Beta
  • In progress
  • On request
  • Via API only
  • Not available
  • Not verified

Checked on 15 October 2026

Pricing and billing
Self-serve startHireLayer edge
Available:

HireLayer:Sign up and get an API key; Free plan with 50 credits / month

Partly, with limits:

HrFlow.ai:Workspace signup; a card is required to activate the API, even for the free tier[10]

Public pricingHireLayer edge
Available:

HireLayer:Free, €24 and €89 monthly plans; one-time packs from €29 for 500 credits

Not available:

HrFlow.ai:Pricing page returns 404; help center points to a quote[11]

Price per CVHireLayer edge
Available:

HireLayer:€0.0445–0.058 per credit on public plans and packs

Not verified:

HrFlow.ai:Was €0.10 per profile parse pay-as-you-go, from €0.07 on annual plans (archive of May 2026)[12]

Billable unit
Available:

HireLayer:1 credit per resume parsed or scored, per search and per skills call, from one balance for all six products; job criteria are free

Partly, with limits:

HrFlow.ai:Per request for parsing; per stored record for search and scoring[11][8]

Extraction quality and coverage
Published accuracy evidenceHireLayer edge
Available:

HireLayer:30-resume benchmark against HrFlow.ai Gaia and Hawk (15 October 2026), run by HireLayer, with the test files, scores and data published

Not available:

HrFlow.ai:Field accuracy percentages and model grades shown without a method[1]

Fields returned
Available:

HireLayer:Contact, experience, education, languages with CEFR level, typed skills, certifications, availability, mobility, driving licences, ROME codes

Available:

HrFlow.ai:Profile info, experiences and educations with skills and tasks, languages, certifications, courses, interests[3]

Candidate photo
Available:

HireLayer:face_url: the candidate photo, including from PDF CVs (a 10-minute link when the file is not stored)

Available:

HrFlow.ai:info.picture returned as a URL[3][1]

Occupation codesHrFlow.ai edge
Partly, with limits:

HireLayer:French ROME codes with a prediction score; no O*NET or ISCO

Available:

HrFlow.ai:ROME 4.0 taggers from 14 families to 12,107 appellations, via the Tagging API[6]

Skills
Available:

HireLayer:Hard, soft or software skill, with domain, subcategory and raw / normalized status

Available:

HrFlow.ai:Skills typed hard or soft, at profile and experience level[3]

Formats and languages
File formats
Available:

HireLayer:15 formats: PDF, DOC, DOCX, ODT, PPT, PPTX, ODP, XLS, RTF, TXT, HTML, Markdown, JPG/JPEG, PNG, BMP

Available:

HrFlow.ai:PDF, PNG, JPG/JPEG, BMP, DOC, DOCX, ODT, RTF, ODP, PPT, PPTX[2]

Size limit
Available:

HireLayer:About 4.5 MB per file (6 MiB encoded) · 100,000 extracted characters

Available:

HrFlow.ai:10 MB[1]

LanguagesHireLayer edge
Available:

HireLayer:70 languages, each covered by HireLayer’s internal tests

Partly, with limits:

HrFlow.ai:“43+ languages” stated, no list[1]

AI and hosting
Where parsing runsHireLayer edge
Available:

HireLayer:🇫🇷 Parsing runs in France, in a Paris data center

Partly, with limits:

HrFlow.ai:AWS in Europe; the provider may change it without client approval; no France commitment[17][18]

Where documents are storedHireLayer edge
Available:

HireLayer:🇫🇷 Files and extracted photos stored in Paris; with do_not_store_data the file is not stored and the photo link expires after 10 minutes

Partly, with limits:

HrFlow.ai:Each parse creates a Profile in a Source; async parsing keeps data at least 24 h[4][19]

Where AI models run
Available:

HireLayer:🇪🇺 HireLayer’s in-house AI pipeline, with processing kept in the EU

Not verified:

HrFlow.ai:Own models described; region and any third-party LLM not documented[1]

Retention control
Available:

HireLayer:do_not_store_data=true per request disables retention

Available:

HrFlow.ai:Auto-delete per Source or Archiving API; retention set by the client[4][19]

Security reports
In progress:

HireLayer:ISO 27001 and SOC 2 in progress

In progress:

HrFlow.ai:ISO 27001 and SOC 2 shown as in progress on the trust center; DPA published[14][20]

Speed
Fast modeHrFlow.ai edge
Beta:

HireLayer:Fast mode in beta, enabled per account on request; no published timing

Available:

HrFlow.ai:Four parsing models from QuickSilver (500 ms p95 stated) to Chronos (5 s), vendor figures[1]

Synchronous resultsHireLayer edge
Available:

HireLayer:Every parse returns JSON in the response

On request:

HrFlow.ai:Real-time parsing must be enabled for the Source by HrFlow[2]

ATS connectors
ATS connectorsHrFlow.ai edge
On request:

HireLayer:Built by HireLayer on request; no marketplace app published

Available:

HrFlow.ai:Open-source connectors for Bullhorn, Greenhouse, Lever, Recruitee, SmartRecruiters, Teamtailor, Workable and more[21][13]

Connectors and tools
ZapierHrFlow.ai edge
On request:

HireLayer:On request; no public Zapier app

Available:

HrFlow.ai:Zapier app with resume parsing actions[22]

MakeHrFlow.ai edge
On request:

HireLayer:On request; no public Make app

Available:

HrFlow.ai:Verified Make app maintained by HrFlow.ai, with 29 modules[23]

SalesforceHrFlow.ai edge
On request:

HireLayer:On request; no AppExchange listing

Available:

HrFlow.ai:Open-source connector in HrFlow’s catalog; no AppExchange listing found[21]

SAP SuccessFactorsHrFlow.ai edge
On request:

HireLayer:On request; no SAP Store listing

Available:

HrFlow.ai:Open-source connector in HrFlow’s catalog[21]

Workday
On request:

HireLayer:On request; no Workday Marketplace listing

On request:

HrFlow.ai:“Premium” connector available on request[21]

Tableau
On request:

HireLayer:On request

Via API only:

HrFlow.ai:No connector; possible through the API

API and integration
Documentation
Available:

HireLayer:Public reference with cURL, Python and Node.js examples, field formats and every error code, plus an OpenAPI spec, llms.txt and an MCP server

Available:

HrFlow.ai:OpenAPI-based reference, public Postman workspace and an interactive playground[2][24]

Request styleHireLayer edge
Available:

HireLayer:REST · multipart file upload · synchronous JSON response

Partly, with limits:

HrFlow.ai:Multipart with a required source_key; 201 real-time or 202 queued[2]

Authentication
Available:

HireLayer:One X-API-Key header for every API

Available:

HrFlow.ai:X-API-KEY plus X-USER-EMAIL; separate read and write key types[7]

Webhooks
Available:

HireLayer:Optional webhook_url on parsing and scoring, each delivery signed

Available:

HrFlow.ai:profile.parsing.success / error and storing events[9]

Official SDKsHrFlow.ai edge
Not available:

HireLayer:No official SDKs; cURL, Python and Node.js examples in the docs

Partly, with limits:

HrFlow.ai:Python (2026 release); JavaScript and PHP not updated since 2022–2023[15][16]

Complementary APIs
Job description parsing
Partly, with limits:

HireLayer:Job text or file → typed, weighted, CV-checkable criteria, free; written in the job’s language: English, French, German, Spanish or Portuguese

Partly, with limits:

HrFlow.ai:Text Parsing API on assembled job text (up to 16 texts a call); no job file endpoint[5]

Candidate–job matching
Available:

HireLayer:Resume Scorer: one job and one or more resumes per call, as files, texts or stored ids; a score, a verdict, and a status and evidence per criterion

Available:

HrFlow.ai:Scoring API ranks Profiles in Sources against Jobs in Boards; Grading for one pair[8]

Skills analysisHrFlow.ai edge
Available:

HireLayer:Skills Normalizer: free text up to 5,000 characters resolved to a taxonomy of 11,061 skills

Available:

HrFlow.ai:Tagging and Taxonomy APIs, embeddings and upskilling[6][8]

Search over a candidate poolHrFlow.ai edge
Available:

HireLayer:Talent Pool Search finds the stored resumes closest to a job, and Job Recommendations the open jobs closest to a resume

Available:

HrFlow.ai:Searching API over stored Profiles[8]

HrFlow.ai pricing vs HireLayer pricing

HrFlow.ai no longer publishes a price list: hrflow.ai/pricing returned 404 when we checked, and the help center asks you to book a demo for a quote. The last public figures are in a web archive snapshot from 19 May 2026.

CVs parsed per month

HireLayer

€89 / month

Scale plan · €0.045 per CV · ≈ $101 / month

HrFlow.ai

HrFlow.ai does not publish a current price list, so the calculator cannot price a monthly volume. The archived pay-as-you-go rate was €0.10 per profile parse.

Lowest published option that covers the volume, at list prices. Excludes enterprise quotes and first-purchase offers. HireLayer credits are shared by all products; this assumes they all go to parsing. Bars compare USD equivalents at the ECB reference rate of 2026-09-30 (€1 = $1.1355).

Reading the numbers

Both vendors price in euros. At HrFlow.ai’s last published pay-as-you-go rate of €0.10 per profile parse, HireLayer’s €0.0445–0.058 per credit is about half or less. HrFlow.ai now quotes on request and adds per-record pricing for search and scoring, so ask for a written quote that covers both before comparing.

HrFlow.ai published prices

  • Current price listNot published

    Quote through a demo request.

  • Profile Parsing (archived)€0.10 / request

    Pay-as-you-go rate on 19 May 2026; “from €0.07” on the annual HrTech+ plan.

  • Free tier (archived)€0 · 1,000 requests / month per API

    A card is required to activate the API.

  • Search and scoringPer stored record

    Billed on active records rather than requests.

Billing rules

  • Parsing is request-based: successful requests are billed.
  • Searching and scoring are record-based: billed on the active records stored.
  • Indexing, getting and archiving objects are listed as free.

HireLayer published prices

One credit balance for all six products: 1 credit per resume parsed or scored, per search and per skills call; job criteria are free and failed work is not billed.

  • Free50 credits / month€0 / month
  • Starter500 credits / month€24 / month€48.00 per 1,000
  • Scale2,000 credits / month€89 / month€44.50 per 1,000
  • Credit pack500 credits, one-time€29€58.00 per 1,000
  • Credit pack2,000 credits, one-time€99€49.50 per 1,000
  • Credit pack10,000 credits, one-time€449€44.90 per 1,000

Enterprise volumes on quote. Prices from the HireLayer pricing page.

Formats, API design and extraction in detail

What changes when you move from HrFlow.ai’s object model to HireLayer’s endpoints.

01

Sources, Boards and Profiles

HrFlow.ai organizes data in Sources (containers of Profiles) and Boards (containers of Jobs). Parsing writes a Profile into a Source; searching and scoring then work on those stored objects. That design suits teams that want HrFlow.ai to be their HR data layer.

HireLayer needs no container set up first. Parsing, scoring and ranking answer in the response, and your database stays the system of record. Each parse is also kept in the workspace’s resume database, unless you send do_not_store_data=true, and Talent Pool Search can find the stored resumes closest to a job.

02

Formats and jobs

File support is close: both accept PDF, Word, OpenDocument, PowerPoint and common images. HireLayer also takes XLS and TXT; HrFlow.ai OCRs scans and offers a separate OCR endpoint.

For jobs, HrFlow.ai parses assembled text through its Text Parsing API and its guide asks you to rebuild the job text first. HireLayer Job Criteria Extractor also takes text, but returns weighted, CV-checkable criteria rather than a full job object, written in the job’s language when it is English, French, German, Spanish or Portuguese, and in English otherwise.

03

ROME on both sides

HrFlow.ai’s ROME 4.0 taggers classify text at four levels, down to the 12,107 appellations, and are credited to France Travail’s referential. They are a separate Tagging API call.

HireLayer returns rome_jobs inside every parse: ROME occupations predicted from the candidate’s job title, with the appellation code and a prediction score. To tag other texts, HrFlow.ai offers a Tagging API.

04

Security and hosting

HrFlow.ai hosts on AWS in Europe under terms that let it change provider without client approval, keeps asynchronous parsing data for at least 24 hours, publishes a DPA and lists ISO 27001 and SOC 2 as in progress.

HireLayer parses CVs in Paris, France and stores files and extracted photos there. Its in-house AI pipeline processes CV content in the EU, so AI processing stays in Europe but is not pinned to France. The web app is hosted in Europe. Its ISO 27001 and SOC 2 certifications are in progress, and it offers a per-request do_not_store_data flag.

When HireLayer fits, and when HrFlow.ai is the better choice

Both lists come from the comparison above. If most of your requirements sit in the right-hand column, stay where you are.

Choose HireLayer when…

  • Your own database is the system of record and you do not want parsed CVs stored by a vendor.
  • You need synchronous parsing without asking for it to be enabled.
  • You want public prices and a free plan you can start with an API key.
  • You want job criteria and per-criterion matching explanations without managing Boards and Sources.

Stay with HrFlow.ai when…

  • You want a vendor-hosted HR data layer with search and scoring over stored profiles.
  • You need packaged connectors to ATSs, job boards or Zapier and Make.
  • You need ROME tagging of any text, embeddings or AI agents.
  • You want a maintained Python SDK.

The main HrFlow.ai alternatives for resume parsing

HireLayer is our product, so it comes first. The other vendors are listed with who they fit and their published entry price, from the comparison pages checked on 15 October 2026.

  1. 1.HireLayer

    Best for a small ATS or HR tech startup that wants a self-serve JSON API, with resume parsing, job criteria, explained matching and ranking under one key and no sales call or annual contract.

    Free plan with 50 credits a month, then €24 a month

  2. 2.Affinda

    Best for self-hosting, a choice of hosting region and certified security.

    US$0.10 per document self-serve

  3. 3.RChilli

    Best for packaged Oracle, SAP SuccessFactors, Salesforce and ServiceNow apps.

    US$75 a month for 500 credits

  4. 4.Textkernel

    Best for ISCO and O*NET occupation codes and Bullhorn integrations.

    From US$99 a month

  5. 5.DaXtra

    Best for staffing agencies that buy parsing inside their ATS.

    Not published (sales-led)

  6. 6.APILayer Resume Parser

    Best for a marketplace API to try on a few CVs.

    Free tier of 100 requests a month, then from $29.99

  7. 7.Eden AI

    Best for switching between third-party parsing providers behind one API.

    The provider’s price plus a platform fee

Moving from HrFlow.ai to HireLayer

HireLayer answers in HrFlow.ai’s JSON format: point HrFlow’s SDK or your HTTP calls at HireLayer and change the key, and the code that reads your profiles stays. Each source_key becomes a HireLayer workspace, so profiles of different sources stay apart; a HireLayer-Workspace header you send takes its place. For now this covers synchronous parsing calls only. Plan more work only if you rely on HrFlow.ai search or scoring over stored profiles.

Estimated effort

Low
Before · HrFlow.ai Profile ParsingPOST /v1/profile/parsing/file
curl -X POST https://api.hrflow.ai/v1/profile/parsing/file \
  -H "X-API-KEY: YOUR_HRFLOW_KEY" \
  -H "X-USER-EMAIL: you@example.com" \
  -F "source_key=YOUR_SOURCE_KEY" \
  -F "file=@resume.pdf" \
  -F "sync_parsing=1" \
  -F "reference=cand_123"
After · HireLayer, HrFlow.ai-compatible APIPOST /api/hrflow/v1/profile/parsing/file
curl -X POST https://hirelayer.co/api/hrflow/v1/profile/parsing/file \
  -H "X-API-KEY: YOUR_HIRELAYER_KEY" \
  -H "X-USER-EMAIL: you@example.com" \
  -F "source_key=YOUR_SOURCE_KEY" \
  -F "file=@resume.pdf" \
  -F "sync_parsing=1" \
  -F "reference=cand_123"

Field mapping

The HrFlow.ai-compatible API returns HrFlow.ai’s own paths. To move to Resume Parser’s native response, which adds contract types, CEFR levels and ROME codes, map the paths below (HrFlow.ai Profile object reference → HireLayer API reference).

HrFlow.ai response fields and their HireLayer equivalents
HrFlow.aiHireLayer
referenceapplication_id
info.first_name / .last_nameresume.info_candidate.first_name / .last_name
info.emailresume.info_candidate.email
info.phoneresume.info_candidate.phone_number
info.location.textresume.info_candidate.location.full_addressplus city, postal code, coordinates
experiences[].company / .titleresume.work_experiences[].company_name / .job_title
experiences[].date_start / .date_endresume.work_experiences[].start_date / .end_dateISO datetime → ISO date
experiences_durationresume.info_candidate.experience_levelyears → bracket
educations[].school / .titleresume.educations[].school_name / .degree_title
skills[].name / .typeresume.skills[].skill_title / .skill_typehard / soft → hard, soft or software
languages[].nameresume.languages[].languageplus CEFR level
textresume.info_resume.text

Migration steps

  1. STEP 01

    Change the URL and the key

    Set the API URL to https://hirelayer.co/api/hrflow/v1/ in HrFlow’s SDK or your HTTP client and use your HireLayer key.

  2. STEP 02

    Remove queue handling

    Every parse answers 201 with the profile in the response, so the 202 path and polling go away. Your reference, tags and metadatas come back in the profile.

  3. STEP 03

    Decide on retention

    Pass do_not_store_data=true if parsed data must not be retained, and stop the archiving jobs you ran on HrFlow.ai Sources.

  4. STEP 04

    Replace scoring

    Extract criteria once per job with Job Criteria Extractor, then score candidates with Resume Scorer, turning on precise_ranking for a shortlist.

Parse without creating a stored object

The request carries no Source and asks for no retention (do_not_store_data, which comes with a paid plan), so application_id comes back null. The trimmed response below is complete in itself.

RequestPOST /api/v4/resumes/parse
curl -X POST https://hirelayer.co/api/v4/resumes/parse \
  -H "X-API-Key: $HIRELAYER_API_KEY" \
  -F "file=@yanis-belkacem-cv.pdf" \
  -F "do_not_store_data=true"
Response (trimmed)200 OK · application/json
{
  "application_id": null,
  "request_id": "4e8a2d61-9f3c-4b17-8d05-6c1b7a9e2f38",
  "stored": false,
  "already_stored": false,
  "resume": {
    "info_resume": {
      "language": "EN"
    },
    "info_candidate": {
      "full_name": "Yanis Belkacem",
      "job_title": "Industrial maintenance technician",
      "experience_level": "3 to 5 years",
      "driver_license": ["B"],
      "location": { "city": "Lille", "country_code": "FR", "postal_code": "59000" }
    },
    "work_experiences": [
      {
        "company_name": "Nordéclair Packaging",
        "job_title": "Maintenance technician",
        "contract_type": "Permanent contract",
        "start_date": "2022-02-01",
        "end_date": null,
        "currently_active": true,
        "experience_duration": 44
      }
    ],
    "skills": [
      {
        "skill_title": "Preventive Maintenance",
        "skill_type": "Hard skill",
        "status": "normalized",
        "domain": "Engineering & Manufacturing",
        "subcategory": "Industrial maintenance"
      }
    ]
  },
  "warnings": [],
  "credits_used": 1
}
do_not_store_data=true
Parsed data is not retained; there is no profile to archive later.
resume.info_resume.language
Detected document language as an ISO 639-1 code.
resume.work_experiences[].experience_duration
Months per role, next to ISO start and end dates.

Run your own CVs through HireLayer and HrFlow.ai

The only comparison that settles quality is yours. Take 20 to 50 permissioned CVs that look like your real intake, scans included, parse them with both APIs and compare the fields you store.

  1. 1Create a free account: 50 credits a month, no plan to pick.
  2. 2Parse the same sample with HrFlow.ai and keep its JSON.
  3. 3Run the loop on the right and diff the fields side by side.
Parse a folder of CVs with HireLayerbash · 1 credit per successful parse
mkdir -p hirelayer
for f in sample/*; do
  curl -s -X POST https://hirelayer.co/api/v4/resumes/parse \
    -H "X-API-Key: $HIRELAYER_API_KEY" \
    -F "file=@$f" \
    -o "hirelayer/$(basename "$f").json"
done

HireLayer vs HrFlow.ai: questions buyers ask

How can I replace HrFlow.ai’s resume parsing API without rewriting my integration?

Switch to HireLayer, which answers in HrFlow.ai’s JSON format. Set the API URL to https://hirelayer.co/api/hrflow/v1/ in HrFlow’s SDK or your HTTP client and use your HireLayer key: the code that reads your profiles stays, and each resume costs 1 credit. This covers synchronous parsing; plan more work only if you rely on HrFlow.ai search or scoring over stored profiles. The step-by-step guide is at https://hirelayer.co/api-docs/migrate-from-hrflow.

Is HireLayer hosted in France like HrFlow.ai?

HireLayer parses CVs in Paris, France and stores files and photos there; its in-house AI pipeline processes CV content in the EU. HrFlow.ai is also a Paris company but documents hosting on AWS in Europe, without a France commitment, and its terms let it change the hosting provider.

How much does HrFlow.ai cost?

HrFlow.ai no longer publishes prices; its pricing page returned 404 on 1 October 2026 and the help center points to a quote. A web archive snapshot from 19 May 2026 listed Profile Parsing at €0.10 per request pay-as-you-go, and from €0.07 on the annual HrTech+ plan. HireLayer’s paid plans and packs cost €0.0445–0.058 per credit.

Does HireLayer store the CVs it parses?

Only if you let it. Pass do_not_store_data=true and parsed data is not retained. HrFlow.ai’s profile parsing stores a Profile in a Source by design, which you can auto-delete or archive.

Do both APIs return ROME codes?

Yes. HireLayer returns ROME occupations for the candidate’s job title, with their appellation code and a prediction score, inside the parse. HrFlow.ai offers ROME 4.0 taggers, down to the appellation level, through its Tagging API.

Does HireLayer have connectors like HrFlow.ai?

A shorter list. HireLayer’s integrations page covers Make, Power Automate, Google Sheets, ChatGPT and Claude (through its MCP server) and the main ATSs and HR suites through their APIs. Other connectors are built on request, and every API can be called from your backend or an HTTP step. HrFlow.ai publishes ready-made connectors and a Zapier app today.

Which one is more accurate, HireLayer or HrFlow.ai?

On HireLayer’s 15 October 2026 benchmark of 30 unseen fictional resumes in 11 languages, HireLayer returned 95.2% of the 1,886 printed values exactly, HrFlow.ai Gaia 84.5% and HrFlow.ai Hawk 73.3%. HireLayer kept all 38 current jobs open (Gaia closed 14) and returned a CEFR level for languages, where HrFlow.ai left the level empty. HireLayer ran the test, so the resumes, scores and data are published to check or rerun; HrFlow.ai shows field accuracy figures without a method.

What are the best HrFlow.ai alternatives?

The main HrFlow.ai alternatives for resume parsing are HireLayer, for a small ATS or HR tech startup that wants a self-serve JSON API, with resume parsing, job criteria, explained matching and ranking under one key and no sales call or annual contract; Affinda, for self-hosting, a choice of hosting region and certified security; RChilli, for packaged Oracle, SAP SuccessFactors, Salesforce and ServiceNow apps; Textkernel, for ISCO and O*NET occupation codes and Bullhorn integrations; and DaXtra, for staffing agencies that buy parsing inside their ATS. APILayer and Eden AI are lighter options for small volumes or for switching providers. For a small ATS that wants to start without a sales call or an annual contract, HireLayer has a free plan with 50 credits a month and monthly plans you can cancel, and one credit covers OCR, skills and location on each CV. Which one fits depends on how you buy (self-serve or annual contract), your monthly CV volume and whether you also need job parsing and matching, so test two or three of them on your own CVs.

Sources and method

Checked on 15 October 2026

HrFlow.ai facts come from its own public pages and documentation, opened on the date above. Third-party sources are labelled. Accuracy and speed figures are reported as each vendor states them; none of them, including ours, is an independent benchmark.

Prices are list prices in each vendor’s currency. USD equivalents use the ECB reference rate of 2026-09-30.

Offers change. If a fact here is out of date, tell us through the contacts in our legal notice and we will re-check it.

HrFlow.ai and the other product names and logos on this page are trademarks of their respective owners, shown only to identify the products compared.

  1. [1]HrFlow.ai Parsing API page
  2. [2]HrFlow.ai docs: parse a resume
  3. [3]HrFlow.ai docs: the Profile object
  4. [4]HrFlow.ai docs: Sources
  5. [5]HrFlow.ai docs: job parsing
  6. [6]HrFlow.ai docs: Tagging API and ROME 4.0
  7. [7]HrFlow.ai docs: API authentication
  8. [8]HrFlow.ai docs: API overview
  9. [9]HrFlow.ai docs: webhooks
  10. [10]HrFlow.ai docs: create and manage your account
  11. [11]HrFlow.ai help center: pricing
  12. [12]HrFlow.ai pricing page, web archive of 19 May 2026
  13. [13]HrFlow.ai Data Studio
  14. [14]HrFlow.ai trust center
  15. [15]hrflow Python package
  16. [16]HrFlow.ai repositories (Riminder)
  17. [17]HrFlow.ai help center: commitment to security
  18. [18]HrFlow.ai general terms and conditions of sale
  19. [19]HrFlow.ai help center: IA security and data protection (FR)
  20. [20]HrFlow.ai data processing agreement for parsing
  21. [21]HrFlow.ai connectors catalog (GitHub)
  22. [22]HrFlow.ai on Zapier
  23. [23]HrFlow.ai on Make
  24. [24]HrFlow.ai public Postman workspace