Sterling Candidates API
Candidate (subject) records that screenings are run against.
Candidate (subject) records that screenings are run against.
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.curl "https://apis.io/api/v1/apis/sterling-check-candidates-api"
curl "https://apis.io/api/v1/apis?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
openapi: 3.2.0
info:
title: Sterling Authentication Candidates API
description: 'The Sterling API integrates background and identity screening into your platform and manages the process end to end. It is a RESTful, OAuth2-secured API: you exchange a Client ID and Client Secret for an access token, then create candidates, look up the screening packages available to your account, initiate screenings (orders), invite candidates by email or hosted link, retrieve results/reports (PDF or HTML), and receive real-time status updates via webhook callbacks.
ACCESS IS GATED. Credentials are provisioned per screening region (US, EMEA, Canada, or APAC) by request through Sterling; there is a separate set of credentials for the sandbox/integration environment and for production.
GROUNDING AND MODELING NOTE: The documented, confirmed operations are the OAuth token exchange, GET /packages, POST /candidates, POST /screenings (including the invite object and the callbackUri for webhooks), and the availability of results/reports with per-item statuses. The remaining operations in this document (list/retrieve/cancel screenings, retrieve/update candidates, retrieve a package, report retrieval paths, recurring screening management, and standalone webhook subscription management) are HONESTLY MODELED on Sterling''s documented order lifecycle and are marked in each operation description with "[MODELED]". The API request host is also modeled: exact hosts are provisioned with your credentials. The OAuth host auth.sterlingcheck.app and the documentation host apidocs.sterlingcheck.app are confirmed; api.sterlingcheck.app is a representative modeled base.
Sterling is a First Advantage company (First Advantage completed its $2.2B acquisition of Sterling Check Corp on October 31, 2024).'
version: '2.0'
contact:
name: Sterling (a First Advantage company)
url: https://www.sterlingcheck.com/services/api/
x-documentation: https://apidocs.sterlingcheck.app/
x-developer-portal: https://developer.sterlingcheck.app/
x-acquisition: First Advantage completed acquisition of Sterling Check Corp on 2024-10-31 ($2.2B).
servers:
- url: https://api.sterlingcheck.app/v2
description: Production (MODELED representative host - exact host provisioned with production credentials)
- url: https://api-sandbox.sterlingcheck.app/v2
description: Sandbox / Integration (MODELED representative host - exact host provisioned with sandbox credentials)
security:
- oAuth2ClientCredentials: []
- bearerAuth: []
tags:
- name: Candidates
description: Candidate (subject) records that screenings are run against.
paths:
/candidates:
post:
operationId: createCandidate
tags:
- Candidates
summary: Create a candidate
description: '[CONFIRMED] Create a candidate (the subject of a screening). Minimum fields are first name, last name, email, and clientReferenceId. Additional PII (date of birth, address history, government IDs, etc.) may be required depending on the package the candidate will be screened with.'
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/CandidateCreate'
responses:
'201':
description: The created candidate.
content:
application/json:
schema:
$ref: '#/components/schemas/Candidate'
'400':
$ref: '#/components/responses/BadRequest'
'401':
$ref: '#/components/responses/Unauthorized'
/candidates/{candidateId}:
get:
operationId: getCandidate
tags:
- Candidates
summary: Retrieve a candidate
description: '[MODELED] Retrieve a candidate record by ID.'
parameters:
- $ref: '#/components/parameters/CandidateId'
responses:
'200':
description: A candidate.
content:
application/json:
schema:
$ref: '#/components/schemas/Candidate'
'401':
$ref: '#/components/responses/Unauthorized'
'404':
$ref: '#/components/responses/NotFound'
patch:
operationId: updateCandidate
tags:
- Candidates
summary: Update a candidate
description: '[MODELED] Update mutable fields on a candidate record before a screening is submitted.'
parameters:
- $ref: '#/components/parameters/CandidateId'
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/CandidateCreate'
responses:
'200':
description: The updated candidate.
content:
application/json:
schema:
$ref: '#/components/schemas/Candidate'
'401':
$ref: '#/components/responses/Unauthorized'
'404':
$ref: '#/components/responses/NotFound'
components:
schemas:
Candidate:
allOf:
- $ref: '#/components/schemas/CandidateCreate'
- type: object
properties:
id:
type: string
createdAt:
type: string
format: date-time
Error:
type: object
properties:
code:
type: string
message:
type: string
CandidateCreate:
type: object
required:
- firstName
- lastName
- email
- clientReferenceId
properties:
firstName:
type: string
lastName:
type: string
middleName:
type: string
email:
type: string
format: email
clientReferenceId:
type: string
description: Your own reference identifier for the candidate.
phone:
type: string
dateOfBirth:
type: string
format: date
addresses:
type: array
items:
$ref: '#/components/schemas/Address'
Address:
type: object
properties:
line1:
type: string
line2:
type: string
city:
type: string
region:
type: string
postalCode:
type: string
country:
type: string
responses:
BadRequest:
description: The request was malformed or missing required fields.
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
Unauthorized:
description: Missing or invalid access token.
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
NotFound:
description: The requested resource was not found.
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
parameters:
CandidateId:
name: candidateId
in: path
required: true
schema:
type: string
securitySchemes:
oAuth2ClientCredentials:
type: oauth2
description: OAuth2 client credentials grant using your Client ID and Client Secret.
flows:
clientCredentials:
tokenUrl: https://auth.sterlingcheck.app/oauth/token
scopes: {}
bearerAuth:
type: http
scheme: bearer
description: The access token returned from the OAuth token exchange, sent as a Bearer token.