Animals whose chip registry has closed or changed hands

curl --request GET \
  --url https://{organization}.rescueconsole.com/api/animals/animals/chip-registries \
  --header 'Authorization: Bearer <token>'

const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};

fetch('https://{organization}.rescueconsole.com/api/animals/animals/chip-registries', options)
  .then(res => res.json())
  .then(res => console.log(res))
  .catch(err => console.error(err));

import requests

url = "https://{organization}.rescueconsole.com/api/animals/animals/chip-registries"

headers = {"Authorization": "Bearer <token>"}

response = requests.get(url, headers=headers)

print(response.text)

{
  "results": [
    {
      "registry": "<string>",
      "state": "closed",
      "advice": "<string>",
      "count": 123,
      "animals": [
        {
          "id": "<string>",
          "name": "<string>",
          "microchip_number": "<string>",
          "microchip_vendor": "<string>",
          "status": "<string>",
          "outcome_date": "2023-12-25",
          "matched_on": "name"
        }
      ]
    }
  ],
  "total": 123,
  "registries_known": 123
}

{
  "error": "house_trained must be 1, 0 or null (not assessed)"
}

{
  "error": "house_trained must be 1, 0 or null (not assessed)"
}

Animals

Animals whose chip registry has closed or changed hands

The animals you need to do something about, grouped by the registry they are with, most urgent first. A closed registry means the chip is registered nowhere and the number leads to nothing when somebody scans it; there is no bulk transfer to any other registry, so the answer is to look each number up and register it again. Animals in the bin are left out; animals that have been adopted are not, because those are the ones living behind a door. Needs read on Animals.

GET

api

animals

chip-registries

Animals whose chip registry has closed or changed hands

curl --request GET \
  --url https://{organization}.rescueconsole.com/api/animals/animals/chip-registries \
  --header 'Authorization: Bearer <token>'

const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};

fetch('https://{organization}.rescueconsole.com/api/animals/animals/chip-registries', options)
  .then(res => res.json())
  .then(res => console.log(res))
  .catch(err => console.error(err));

import requests

url = "https://{organization}.rescueconsole.com/api/animals/animals/chip-registries"

headers = {"Authorization": "Bearer <token>"}

response = requests.get(url, headers=headers)

print(response.text)

{
  "results": [
    {
      "registry": "<string>",
      "state": "closed",
      "advice": "<string>",
      "count": 123,
      "animals": [
        {
          "id": "<string>",
          "name": "<string>",
          "microchip_number": "<string>",
          "microchip_vendor": "<string>",
          "status": "<string>",
          "outcome_date": "2023-12-25",
          "matched_on": "name"
        }
      ]
    }
  ],
  "total": 123,
  "registries_known": 123
}

{
  "error": "house_trained must be 1, 0 or null (not assessed)"
}

{
  "error": "house_trained must be 1, 0 or null (not assessed)"
}

Authorizations

Authorization

string

header

required

An API key from Settings, API keys. It starts with rc_live_.

Response

Grouped by registry. An empty results list means nothing matched what we know about, which is not the same as every chip having been checked.

results

object[]

Show child attributes

total

integer

registries_known

integer

How many registries this check knows about at all, so a reader can tell silence from coverage.

Using the API

Endpoints

Animals whose chip registry has closed or changed hands

Authorizations

Response