Job::MatchExplanations
Explain how candidates score against the job rubric
Why a candidate is a fit: the job rubric, and the cached score each candidate earned against it with the reasoning per metric. Reads only — unlike getJobSearchScores it never re-dispatches an evaluation, so a candidate nobody has scored comes back as unscored rather than costing a model call. band is null whenever failed_mandatory is non-empty: that score is a must-have override, not an assessment of how good someone is. verdict states the outcome on every row: failed_must_have, not_judged (any status other than scored), or the band for a candidate who passed.
post/api/v1/job/posts/{post_id}/match_explanations
Request
- Base URLhttps://api.flexiple.com (the document declares no server; this is the origin it was published from)
- AuthHTTP bearer
Request body
Response
Explanations
Changes
No recorded changes to this operation across all 1 revision of this API.