After you submit a stamp observation to our authentication service our API will return a JSON response that looks like this:

{
  "stamp": {
    "serial": "DEVA"
  }, 
  "receipt": "ABCDEFGHIJKLMNOPQRSTUVWXYZ",
  "secure": false,
  "created": "2015-03-24 11:27:33.014149"
}

🚧

Stamp serials for 3D printed stamps

As we said goodbye to our older 3D printed stamps, we no longer have stamp serial names that are commissioned as: "DEV-STAMP" and "DEV-STAMP-B". The default developer stamps commissioned to all new applications are named "DEVA" and "DEVB". You can always rename any stamp directly from your application's dashboard.

Here’s an explanation of what we got back:

“stamp”: {“serial”: “DEVA”}

The “stamp” element in the JSON contains an object denoting the found stamp’s serial number (if a stamp was found). This is what you should use to determine how your app should proceed.

Had the submitted coordinates not matched up with a stamp associated with your map, the response would have been:

“error”: {“message”: “Stamp not found”, “code”: 32}

After "stamp", we see a "receipt" property. The “receipt” is a unique identifier that we can use to locate your API call for troubleshooting requests.

“receipt”: “ABCDEFGHIJKLMNOPQRSTUVWXYZ”

Continuing on, “secure” indicates whether the request was made using https (“true”) or http (“false”).

“secure”: false

Lastly, “created” is the timestamp for the API call.

“created”: “2015-03-24 11:27:33.014149"