See your crew

The fleet roster is the heart of the API: every crew member on your vessels, with their verification status, background-check status, and a count of documents about to expire. Each crew member has a crew_unique_id — the id you pass to read their profile, documents, and compliance.

Requires vessels:fleet:read. Status fields also need crew:status:read, which your management plan includes. Authenticated with your API key as a Bearer token over TLS; reads are not signed.

List everyone on your fleet

cURL

curl -sS "$BASE/api/v2/employers/me/fleet?include_documents_expiring_within_days=30" \
  -H "Authorization: Bearer $CPK_KEY"

Response

{
  "items": [
    {
      "crew_unique_id": "crew_001",
      "name": "A. Crew",
      "vessel_id": "ves_abc",
      "vessel_name": "M/Y Example",
      "role": "Chief Engineer",
      "verification_status": "verified",
      "background_check_status": "completed",
      "documents_expiring": 1,
      "as_of": "2026-06-08T10:00:00Z"
    }
  ],
  "next_cursor": null,
  "expiring_within_days": 30
}

Field	What it is
`crew_unique_id`	The crew member’s id — use it for profile, documents, compliance.
`role`	Their position on this vessel.
`verification_status`	Whether CrewPass has verified the crew member.
`background_check_status`	Standardised status — see Background-check status.
`documents_expiring`	How many current documents expire within the window you asked for.

Tune the expiry window with ?include_documents_expiring_within_days=30 (0–730). verification_status and background_check_status are shown only when that crew member has consented to share status with you.

Paging

Large fleets are paged. When next_cursor is set, pass it back to get the next page:

GET /api/v2/employers/me/fleet?cursor=<next_cursor>&limit=50    # limit up to 200

Find one crew member by email

If you already hold a crew member by email (say, from your own system), resolve them to a crew_unique_id:

cURL

curl -sS "$BASE/api/v2/employers/me/crew/lookup" \
  -H "Authorization: Bearer $CPK_KEY" -H "Content-Type: application/json" \
  -d '{"email":"crew@example.com"}'

Response

{ "crew_unique_id": "crew_001", "status": "verified" }

A crew member who isn’t on one of your vessels returns 404 — you can never use this to discover people outside your fleet.

Get started

Guides

Webhooks

Reference

List everyone on your fleet

Paging

Find one crew member by email

Next

​List everyone on your fleet

​Paging

​Find one crew member by email

​Next

List everyone on your fleet

Paging

Find one crew member by email

Next