Stop parsing. Start processing.

Credentia One files deliver structured, typed, validated candidate data directly to your systems. Every field is labeled. Every date is formatted. Every compliance disclosure is included. Parsing errors drop to zero.

What changes for you

Credentia One does not replace your ATS, your background check vendor, or your internal workflows. It standardizes the input. Instead of receiving a PDF that your system has to guess at, you receive a .credentia.json file: structured data that any system can read without ambiguity.

Your Applicant Tracking System, your HRIS, your screening tools: none of them need to change. Credentia One sits upstream. It is the format candidates use to deliver their data to you.

Verify every file

Each Credentia One file contains a cryptographic token registered at the time of generation. The verification API allows you to confirm that a file is authentic, was generated using the Credentia One standard, and has not been modified. The API is a single endpoint. You send a token hash with your API key. You receive a verification result in milliseconds.

POST https://mbbpynoshxkvhqonyczd.supabase.co/rest/v1/rpc/verify_token

Headers:
  apikey: [your-supabase-anon-key]
  Content-Type: application/json

Body:
{
  "p_api_key": "[your-employer-api-key]",
  "p_token_hash": "[candidate-file-token-hash]"
}

Response (verified):
{
  "verified": true,
  "token_hash": "5549dccc...",
  "country_code": "CA",
  "generated_at": "2026-04-12T12:47:07Z",
  "verified_by": "Your Company"
}

Response (not verified):
{
  "verified": false,
  "error": "Token not found in registry"
}

How it works for employers

Receive

Candidates submit .credentia.json files through your existing channels: email, upload portal, job board. No new infrastructure required.

Verify

Call the verification API with the file's token. Confirm authenticity in milliseconds. Every verification is logged for your records.

Process

Ingest the structured JSON into your ATS, HRIS, or data pipeline. Workday, Greenhouse, SAP, Oracle, or any system that reads JSON.

One-click apply

This is what the future of job applications looks like. A single button on your careers page. No forms, no file uploads, no 20-minute portals. The candidate clicks once, their Credentia One file is submitted, and your systems receive structured, verified data instantly.

Acme Corporation
Senior Product Manager
Toronto, ON | Hybrid

Mockup. Illustrating the candidate experience when employers accept Credentia One files.

Security

Credentia One is a document standard, not a platform. There is no vendor lock-in, no middleware, no data stored on our servers. The .credentia.json file is plain text following a published open schema. Your security team can audit every field. The verification API validates cryptographic hashes. It does not receive, process, or store candidate data. The only data that crosses the wire is a hash string and a verification response.

Credentia One files may contain voluntary compliance disclosures for multiple jurisdictions, including the United States, Canada, the United Kingdom, the European Union, Australia, and New Zealand. Employers are responsible for handling these disclosures in accordance with their applicable local laws, including storing equality and diversity data separately from professional credentials where required.

Works with your stack

Credentia One files can be ingested by any system that reads JSON:

No proprietary connector required. If your system reads JSON, it reads Credentia One.

Pay per job posting

Each registered job posting includes unlimited candidate verifications for 90 days. No per-candidate fees. No platform subscriptions. No minimum commitments. You pay only for the postings you register.

Pilot Program

We are onboarding early employers at introductory rates. Contact us to discuss your hiring volume and get your API key.

Request API access

Tell us about your hiring volume and we will set up your verification API key.