Each crew member on your fleet carries a background-check status. It appears on the fleet roster alongside verification status, so you can see at a glance who has cleared and who is still in progress.
Ordering a background check through the API is part of the v2 write surface, which is deferred and currently disabled. When the write surface ships, issuing a check is a mutating request and requires HMAC request signing (see Authentication). Today this page is read-only: you read a crew member’s standardised background-check status, but you cannot initiate a check.
Requires crew:status:read (included in your management plan). It’s part of the crew roster response. Authenticated with your API key as a Bearer token over TLS; reads are not signed.

​
Where you see it

{
  "crew_unique_id": "crew_001",
  "verification_status": "verified",
  "background_check_status": "completed",
  "...": "..."
}

​
The status values

CrewPass normalises every provider’s vocabulary into one standard set:
StatusMeaning
pendingA check exists but hasn’t started.
awaitingWaiting on information from the crew member.
in-progressBeing processed.
completedCleared.
declinedDid not clear.
expiredA previously completed check has lapsed.
null means there’s no background check on record for that crew member.
CrewPass never tells you who ran the check, and never invents an ETA — you get the standardised state and nothing more. Ordering a check through the API is a later version; today this is read-only.

​
Next

  • Webhooks — receive a crew.status.changed event when this moves.