How to check an ID card

Every SAR Duty ID card has a QR code that opens the card's page on the verify site, such as https://verify.sarduty.com/K7Q4M-2XA9H. An app that signs members in, such as SAR Command Assist, can ask SAR Duty the same check as JSON: scan the card, take the code, and get back who it is, their team, and whether they are an active member.

To try your app end to end, scan the sample ID cards: each has a QR code. Sample cards shows what each one answers.

Get the code from a scan

The QR code holds a link like HTTPS://VERIFY.SARDUTY.COM/K7Q4M-2XA9H, in capitals. The code is the last part of the link. Do not open the link. Send the code to SAR Duty's check, whatever site the link names. A forged card can't send your app anywhere else that way.

Codes are 10 letters and numbers, printed under the QR code with a dash in the middle. The check takes them with or without the dash, in either case. Cards made before November 2026 had 8 and moved to 10, and their Wallet passes changed with them. An 8-character code now matches no card.

Ask for the card

GET https://verify.sarduty.com/api/v1/cards/K7Q4M-2XA9H

No key or login. It answers what the verify page shows anyone who has the card in hand, plus where an active member's records live.

Read the answer here, not the card's page. The page answers 200 for every code, even one that matches no card.

What comes back

An active member's card:

{
  "code": "K7Q4M-2XA9H",
  "status": "active",
  "sample": false,
  "member": {
    "name": "Cameron Ruiz",
    "joined_at": "2023-10-30T07:00:00Z",
    "photo_url": "https://verify.sarduty.com/K7Q4M-2XA9H/photo",
    "qualifications": [
      {"name": "First aid", "ends_at": "2027-11-18T08:00:00Z"},
      {"name": "Ground search and rescue", "ends_at": null}
    ]
  },
  "team": {
    "name": "Coast Range SAR",
    "organization": null,
    "refreshed_at": "2026-11-04T03:06:10Z",
    "valid_until": "2027-03-01T06:59:59Z"
  },
  "records": {
    "service": "d4h",
    "api_url": "https://api.ca.d4h.org",
    "team_id": 9100000,
    "member_id": 9110132
  }
}
  • status is active, inactive (the member is retiring or retired), or revoked (the card was replaced, for a lost phone, or the team stopped using ID cards). All three answer 200, so read status, not the HTTP code. Sign in only an active card.
  • sample is true for Coast Range SAR's made-up cards. Never accept one as ID.
  • photo_url is the member's photo, a square PNG. Show it, and compare it with the person: the photo is what a copied code can't fake.
  • qualifications are the ones the team lists on its cards. ends_at is null when one doesn't expire.
  • refreshed_at is when SAR Duty last copied the team's records, so a status can be that far behind.
  • Times are ISO 8601, in UTC, to the second. joined_at and organization can be null.
  • joined_at, left_at, and ends_at are days: the start of that day on the team's clock. A qualification is good through its ends_at day.

A retiring or retired member's card gives member.name, member.left_at, and team: no photo, no qualifications, and no records. left_at is when D4H retired them, and null while they are retiring or when the team gave no date.

A revoked card gives only code, status, and sample.

A code that matches no card answers 404 with {"status": "not_found"}.

New fields can appear in any answer, so ignore the ones you don't know. A change that would break an app gets a new address, /api/v2.

When a member retires

A member's card is never cancelled when they retire. It answers inactive as soon as their team marks them retiring, and stays inactive once they're retired. If they come back, the same card answers active again.

This way the check tells the truth: a retired member, and when. A cancelled card couldn't say that, and couldn't come back if the team made a mistake.

Turn away an inactive card: the person is not an active member. For a revoked card, ask the member for their new one.

Sample cards

Coast Range SAR is a made-up team. Its cards answer like real ones, with "sample": true, and their codes change only when the code format does, as in November 2026, so you can build against them. Their dates move with today's.

Scan them from Sample ID cards, which shows each card's QR code. Its forged card links to another site, with the active card's code. Your app gets the active answer, since it sends the code and never opens the link: the photo is the check.

An active member

https://verify.sarduty.com/api/v1/cards/SAMPX-ACTVX answers 200:

{
  "code": "SAMPX-ACTVX",
  "status": "active",
  "member": {
    "name": "Cameron Ruiz",
    "qualifications": [
      {
        "name": "First aid",
        "ends_at": "2026-12-07T07:00:00Z"
      },
      {
        "name": "Ground search and rescue",
        "ends_at": null
      }
    ],
    "joined_at": "2023-11-18T08:00:00Z",
    "photo_url": "https://verify.sarduty.com/SAMPX-ACTVX/photo"
  },
  "records": {
    "service": "d4h",
    "api_url": "https://api.ca.d4h.org",
    "team_id": 9100000,
    "member_id": 9110132
  },
  "sample": true,
  "team": {
    "name": "Coast Range SAR",
    "valid_until": "2027-03-01T06:59:59Z",
    "organization": "Western Search and Rescue Association",
    "refreshed_at": "2026-11-22T23:25:50Z"
  }
}

A retired member

https://verify.sarduty.com/api/v1/cards/SAMPX-RTRDX answers 200:

{
  "code": "SAMPX-RTRDX",
  "status": "inactive",
  "member": {
    "name": "Robin Tse",
    "left_at": "2026-07-25T07:00:00Z"
  },
  "sample": true,
  "team": {
    "name": "Coast Range SAR",
    "valid_until": null,
    "organization": "Western Search and Rescue Association",
    "refreshed_at": "2026-11-22T23:25:50Z"
  }
}

A replaced card

https://verify.sarduty.com/api/v1/cards/SAMPX-CNCDX answers 200:

{
  "code": "SAMPX-CNCDX",
  "status": "revoked",
  "sample": true
}

No card has this code

https://verify.sarduty.com/api/v1/cards/SAMPX-NCRDX answers 404:

{
  "status": "not_found"
}

Too many misses

20 codes that match no card in 10 minutes from one IP address, here or on the verify page, and that address gets 429 with {"status": "limited"} and a Retry-After header, for up to 10 minutes.

Only codes that could be a card's count. Real cards never count, and nor does anything else your scanner reads, such as another app's QR code. So checking a crowd at a callout can't trip it, even though everyone at a command post shares one address.

Guessing codes

A code is 10 characters from 30 letters and numbers, picked at random: about 590 trillion codes. Codes don't follow a member number or the order cards were made, so one card's code says nothing about another's.

With the limit above, one address gets about 3,000 misses a day. Even 1,000 addresses guessing at once would take about 56 years to find any of 10,000 cards, and a chosen member's card far longer. SAR Duty also watches misses across every address, so guessing spread over many machines gets noticed, and any card it found is replaced.

A guessed code gets no more than the card shows anyone who sees it: a name, a team, a photo, and whether the member is active. It can't pass as the member, because the photo has to match the person in front of you.

No internet

The check needs SAR Duty, and a command post may have no internet. Keep each answer by its code, so a code you've checked before can sign its member in from your saved answer. For a new code, record the scan and the time, check it once you're back online, and flag any that come back not active. A member's status can change either way, so check saved answers again once you're back online too.

More about the member

records says where the team keeps its records: service is d4h for D4H Team Manager or sar_duty_records for SAR Duty Records, and more may come. Both serve D4H's v3 API at api_url, so the member is at:

GET {api_url}/v3/team/{team_id}/members/{member_id}

That needs an access key from the member's own team, from D4H or from SAR Duty Records. Without one, the IDs open nothing.

Matching members you already have

Match on api_url, team_id, and member_id together: a member ID alone can repeat between D4H and SAR Duty Records. Do not match on the name or the team's own ID number, which two teams can share. A member keeps their IDs when their card is replaced, but the card's code changes, so do not store the code as the member's ID.