Quickstart
This guide walks you through the complete Fribl workflow: analyzing a CV, analyzing a job description, polling for completion, and running a match.Prerequisites
- A Fribl API key (contact Fribl to obtain one)
- A tool for making HTTP requests (cURL, Postman, or any HTTP client)
- Tokens in your workspace — analyzing and matching are billable
This walkthrough consumes a handful of tokens (analyzing one CV and one job, then one match). Check your balance first, and top up in the Fribl Console if needed:See Tokens & Billing for pricing. Failed tasks are refunded automatically, so you only pay for work that completes.
Step 1: Analyze a CV
Submit one or more CVs for analysis. Theinputs field accepts an array of CV text strings.
PENDING status. Save the ID for status polling.
Response
Step 2: Poll for completion
Check the processing status until it reachesCOMPLETED. Continue polling while the task is PENDING, and handle NOT_FOUND explicitly.
Response
Step 3: Analyze a job description
Submit a job description for analysis using the same pattern.Poll
POST /jobs/status for the job as well, using the same pattern as Step 2. Both the CV and job must reach COMPLETED before matching.Step 4: Match the candidate to the job
Once both reachCOMPLETED status, run a match with your preferred scoring weights.
The
jobId and every ID in candidatesIds must belong to the same workspace as the API key you’re using. If the vacancy or a candidate isn’t in your workspace, the match is rejected immediately (404 VACANCY_NOT_FOUND / 422 CANDIDATES_NOT_FOUND) and nothing is charged. See Error Handling.Response
File upload alternative
You can upload CV and job files directly instead of providing text:Next steps
API Reference
Explore all 21 endpoints in detail with interactive examples.
Error Handling
Understand error responses and processing statuses.