Veterans

Search for unpaired veterans

Changed on

Searches for unpaired veterans based on provided criteria. Currently only supports searching for unpaired veterans (paired=false). The search uses the unpaired_veterans_by_last_name view which filters veterans where guardian.id is empty. That view emits [flight.status, name.last.toUpperCase()] and keeps spaces and punctuation. The lastname query is uppercased to match that key. It is not passed through the /search name-index helper, which strips spaces, apostrophes, and periods and leaves case unchanged.

get/veterans/search

Request

  • Base URL: https://sshf-api-330507742215.us-central1.run.app
  • URL: https://sshf-api-330507742215.us-central1.run.app/veterans/search
  • Auth: OAuth 2 (implicit, authorization URL https://accounts.google.com/o/oauth2/v2/auth)

Query parameters

pairedboolean

Whether to search for paired veterans (currently not implemented)

status'Active' | 'Flown' | 'Deceased' | 'Removed' | 'Future-Spring' | 'Future-Fall' | 'Future-PostRestriction'

Flight status filter for the search

lastnamestring

Last name prefix. Uppercased to match unpaired_veterans_by_last_name. Spaces and punctuation are kept, so "Le Roy" and "le roy" share a key and "LeRoy" does not.

limitinteger

Maximum number of results to return

Response

Search completed successfully

idstring

Document ID

namestring

Full name of the veteran (first + last)

citystring

City and state of residence (city, state)

flightstring

Flight ID assignment

prefsstring

Guardian preference notes

Changes