Certification verification
A certification claim is checked at the issuer's own verification service. Most issuers require the credential ID; some allow a name search. The issuer key comes from GET /v1/issuers.
curl -X POST https://api.primarycheck.com/v1/verifications \
-H "Authorization: Bearer pc_live_…" \
-H "Content-Type: application/json" \
-d '{
"person": {
"firstName": "Amy",
"lastName": "Kowalski",
"dob": "1976-02-14"
},
"claims": [
{
"type": "certification",
"issuer": "aha_bls",
"credentialId": "245512345678"
}
],
"purpose": "employment",
"consent": {
"consentId": "cons_8f1…"
}
}'Certification issuers
| Issuer key | Credential | Lookup by |
|---|---|---|
aha_bls | AHA BLS / ACLS / PALS eCard | eCard code |
nremt | National Registry of EMTs | name + state, registry number |
comptia | CompTIA A+/Network+/Security+ | verification code |
pmi | PMP, CAPM | name, certificate number |
aws | AWS certifications | validation number |
microsoft | Microsoft certifications | transcript share code |
cisco | CCNA, CCNP | certificate verification code |
google_cloud | Google Cloud certifications | credential ID |
nasm | NASM CPT | name |
servsafe | ServSafe | certificate number |
cchest | Cardiology / dialysis boards (CCHT, BONENT) | name, certificate |
Issuers with no public lookup are routed to issuer outreach on the same engine as employment. Field checks: credential exists, name matches, not expired. See claim types.