pet.trezy.getPet
Details · query
| Kind | query |
|---|---|
| Authority | trezy.pet |
| Indexed |
Query
query · GETParameters
query stringaturi
string · at-uriHydrate ONE pet by its at-uri, as listed by pet.trezy.getPets. This is the mode the roster uses: the list call returns identifiers and each is fetched here, which keeps a large collection off the wire. Takes precedence over `did`.
did
string · didWhose newest pet to return. Ignored when `aturi` is given. One of the two is required — sending neither refuses, because defaulting to anything here would answer about somebody.
Output
application/jsoncreatedAt
string · datetimeerror
stringPresent instead of a pet. `not found` is the ORIGINAL spelling, with a space, and it stays that way: PetPage branches on it and renaming it would break the public profile page for no gain.
knownValues: not found | bad-request
message
stringname
stringspecies
stringuri
string · at-uriSimilar lexicons
semantic matchLexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.
-
pet.trezy.getPets
queryThe at-uris of a player's pets, newest first, optionally filtered by state. Returns IDs only by default.
-
pet.trezy.getNewPets
queryThe pets adopted in the 7 days before asOf, for the weekly arrivals post. Live pets only: a pet retired inside the same week is not an arrival any more. ⚠ `total` IS THE TRUE COUNT AND `pets` IS ONLY WHAT FITS ON STAGE — the post's number must be how many animals arrived, not how many the renderer could draw. Carries no keeper DID and no pet name, because the post says neither — `#pet` carries `rkey` rather than the at-URI so the caller never even receives the keeper's DID, which sits in the URI