Skip to main content
SmartTag is used from the animal record, by hand. Nothing is sent on a schedule. Only an organization admin can set it up or change it, under Settings → Advanced & security → Integrations. SmartTag charges nothing for this.

What it does

What you need

An API key from SmartTag, and nothing else. Their key is issued per customer and every pet sent with it lands in that customer’s account, so there is no organization ID to type: the key is the account. In RescueConsole, you need to be an Organization admin to set it up, and to have Change on Animals to press the buttons.

Setting it up

1

Ask SmartTag for a key

Their API documentation is public. Ask them for a key for your organization.
2

Add the integration

In RescueConsole, open Settings → Advanced & security → Integrations, find SmartTag under Microchip registries, and add it.
3

Paste the key

Enter the API key and press Save it. It is stored and never shown again.
4

Check the server

The Server box starts on SmartTag’s live server. Change it to their sandbox only while you are testing with a development key.
5

Test the connection

Test the connection asks SmartTag to confirm the key and reports back in their own words.

What moves

The buttons are on the SmartTag microchip registration card on the animal’s Profile tab. The card is there only once SmartTag is connected and the animal has a microchip number. Nothing is sent until you press a button on it. Check with SmartTag answers in one of two ways:
  • Not registered with SmartTag. Registering it adds a new record.
  • This microchip is ALREADY registered with SmartTag. Registering it replaces the details on that record with yours.
Then the card offers a Register to button for the adopter, when one is on file, and one for your organization, each with the name on it, and asks you to confirm before it sends. Registering to the adopter sends SmartTag their name, phone, email and address, with your organization as the second contact. With no adopter on file, the chip can be registered to your organization for now and to the adopter later. Asked before, at the foot of the card, lists each registration: the date, who it was to, and Accepted or Refused with SmartTag’s words.

When it goes wrong

Test the connection answers Connection successful or Connection failed, with the reason, such as SmartTag refused the API key. On the card, a registration SmartTag refuses is shown in their words and listed under Asked before as Refused. Two refusals are RescueConsole’s own, before anything is sent:
  • Your organization has no email address on file, and SmartTag will not take a registration without one. Add it under Settings, Organization.
  • The adopter’s name, then has no email address on file, and SmartTag will not take a registration without one. Add it to their record, or register the chip to your organization instead.
This is built from SmartTag’s published documentation and has not yet been run against their servers, because they had not issued a key when it was written. Check the first registration against their records before you rely on it.