About Credentia One
Why Credentia One exists
Every day, millions of job seekers fill out the same forms, answer the same questions, and re-enter the same data across dozens of employer portals. The average application takes 15 to 20 minutes. For someone submitting 20 applications a day, that is nearly seven hours of repetitive data entry.
The employer side is no better. Applicant Tracking Systems ingest resumes as unstructured PDFs, attempt to parse them (often badly), and present recruiters with mangled, incomplete data. The result is a system where both sides lose time.
Credentia One exists to fix the transport layer. Not the hiring decision, not the identity verification, not the interview process. Just the way professional data moves from one person to another.
For candidates
You fill out one form. You download one file. You use that file everywhere. No more re-typing your phone number into Workday for the fourteenth time this week. No more copy-pasting your work history into a text box that reformats it badly. Your .credentia.json file is your complete professional record in a format that any system can read without errors.
For employers
You receive structured, machine-readable candidate data instead of a PDF that your ATS has to guess at. Every field is labeled, typed, and validated. Parse errors drop to zero. Your existing systems, whether Workday, Greenhouse, SAP, or anything else, can ingest a Credentia One file with no ambiguity.
For the ecosystem
The Credentia One schema is open source under the Apache 2.0 license. The candidate tool is free and will remain free. The verification API is a commercial service that ensures file integrity and funds the ongoing development of the standard.
The standard currently supports compliance disclosures for the United States, Canada, the United Kingdom, the European Union, Australia, and New Zealand, with additional regions planned.
How it is built
Credentia One is a static website. The candidate form runs entirely in your browser. No account required. No data stored on our servers. When you generate your file, a cryptographic hash is registered with our verification service so employers can confirm your file was generated using the Credentia One standard. That hash contains no personal information.
Employers access the verification API through a simple REST endpoint. Each API key is tied to registered job postings. Verification responses are logged for audit purposes. No candidate data passes through the verification service. Only cryptographic hashes are checked.
The compliance disclosures in each Credentia file are conditional. The form detects which countries a candidate has selected for work authorization and displays only the relevant disclosure sections. A candidate applying in Canada and Australia sees Canadian Employment Equity and Australian Equal Opportunity sections. A candidate applying only in the United States sees only the EEOC section. No one is asked to fill in forms for jurisdictions that do not apply to them.