Verify with Rankix API

Check a candidate's published Rankix badge from your own hiring tools - an ATS, a spreadsheet, a script. One public endpoint, no key.

What it returns

Exactly what the candidate's public badge page shows: their score and band, and how many of their profile claims Rankix has verified. It only answers for candidates who have published a badge, and stops answering the moment they switch it off. Nothing else about the candidate is available through it.

Request

The handle is the last part of the badge link the candidate shared with you (/badge/ada-lovelace → ada-lovelace).

GET /api/v1/badges/{handle}

curl https://<your Rankix host>/api/v1/badges/ada-lovelace

Response

{
  "apiVersion": "1",
  "handle": "ada-lovelace",
  "name": "Ada Lovelace",
  "headline": "Platform engineer",
  "score": { "value": 712, "outOf": 1000, "band": "Strong", "updatedAt": "2026-10-01T10:00:00.000Z" },
  "verification": {
    "claims": 12,
    "verified": 7,
    "partiallyVerified": 2,
    "verifiedShare": 0.58,
    "byType": [
      { "type": "skills", "claims": 8, "verified": 5, "partiallyVerified": 2 },
      { "type": "certifications", "claims": 2, "verified": 2, "partiallyVerified": 0 }
    ]
  },
  "methodologyVersion": "1.1",
  "badgeUrl": "https://<your Rankix host>/badge/ada-lovelace",
  "retrievedAt": "2026-10-03T09:00:00.000Z"
}

score: The candidate's Rankix Score on the 0-1000 scale and its band. null until they have a score.
verification.claims: How many claims (skills, roles, projects, certifications, education) are on the profile.
verification.verified: Claims a Rankix check confirmed: a reviewed document or certificate, or a GitHub repository the candidate proved they control.
verification.partiallyVerified: Claims a reviewer could confirm only in part.
verification.verifiedShare: verified ÷ claims, 0-1. null when there are no claims, rather than a misleading 0.
methodologyVersion: The scoring method the score was computed with. Changes are published in the Rankix Score changelog.
badgeUrl: The human-readable badge page for the same data.

Errors and caching

404 not_found - no published badge has that handle (it may have been switched off).
503 unavailable - Rankix couldn't look it up; retry shortly.
Responses may be cached for up to 5 minutes. Any origin may call it from a browser (CORS is open); it never needs credentials.
The response carries apiVersion. Fields won't change meaning within a version.

Reading it responsibly

A score summarizes how well-evidenced a profile is, not whether someone fits your role. Use it to decide what to look at first, and read the evidence before deciding. How the Rankix Score works