Screen occurrence records for listed species published at a precision that exposes them, in one call

Up to 5000 occurrence records, each a species name and coordinates as published. Our engine's names screen (the one behind a file dropped on passage-data.com) answers: for each species a register lists, which register lists it (status, whether it applies where the records are, the line the register prints) and how many of its records sit at a coordinate finer than a 0.01 degree grid (about 1.1 km), and how many of those a rounding would not protect because another record states the same position. treatment is Chapman 2020's: the category the data holder's documented answers (determinations) reach, with its grid and what it would round and withhold; without answers, the canon's coded refusal (sensitivity.criteria_unevaluated) naming the next question — a listing is not that determination. Every register screened is named with its edition. Nothing sent is kept. Use it instead of one call a record: the door allows 30 calls in 10 seconds.

post/exposure

Request

  • Base URL: https://passage-data.com/api/v1
  • URL: https://passage-data.com/api/v1/exposure
  • Auth: one of:
    • none
    • HTTP bearer
    • API key in header x-api-key

Request body

placestring

ISO 3166 code of where the records are: CA, US, FR, CA-QC, US-CA, GB-SCT. Omit it and the screen places them by their points, and says so.

determinationsobject

The data holder's documented answers to Chapman 2020's questions, by number: {"1.1": true, ...}.

Response

Each listed species with its registers and its exposure, every register screened with its edition, and the Chapman 2020 treatment

queryobject
exposureobject nullable
treatmentobject
outcome_ofstring
packed_asstring
registersobject
outcomesobject
refusedobject

Changes

No recorded changes to this operation across all 1 revision of this API.