RECEIVING IDentification Results
Apart from the general principle of reciprocity - i.e. allowing access to your community’s experts or using the submit identifications API - we do have some basic rules:
When you receive an identification on one of your submissions, be sure to display the expert’s name, e.g. “Identified by Jane Doe.”
If the expertise comes from a third party partner, you should also display that partner’s name - e.g. “Identified by Jane Doe, Wild Orchid Watch.”
If there is no partner’s name, you are not required to include “BioSMART” as the partners_name, but we would prefer it, and will do the same for you.
Please try to avoid writing code that might disrupt the experience of other users of this system, and if you have any questions or concerns about the impact of your code, kindly contact us before testing live.
i. Receiving IDentification Results FOR A USER
This API will show the results for a particular user.
LOGIN
curl -X POST \
https://api.questagame.com/api/login \
-H 'cache-control: no-cache' \
-H 'content-type: multipart/form-data; boundary=----WebKitFormBoundary7MA4YWxkTrZu0gW' \
-H 'x-app-version: 20' \
-F email=email@domain.com \
-F password=password
GET https://api.questagame.com/api/my_latest_sightings
headers: {X-AUTH-KEY: value}
Params:
user_id:
Tells the system whose sightings you’re retrieving.
Accepted value: the user’s ID number
limit:
Determines how may items will be displayed per page.
Accepted value: one or more
Offset:
Allows you to skip items/pages. For example, if you have a limit of 15. And you want to load page 4. The offset value would be 45 (it would skip 45 sightings).
Accepted value: 0 or higher
II. RECEIVING IDENTIFICATION RESULTS FOR A SIGHTING
LOGIN
curl -X POST \
https://api.questagame.com/api/login \
-H 'cache-control: no-cache' \
-H 'content-type: multipart/form-data; boundary=----WebKitFormBoundary7MA4YWxkTrZu0gW' \
-H 'x-app-version: 20' \
-F email=email@domain.com \
-F password=password
GET http://api.questagame.com/api/signtings/[insert sighting ID number here]
headers: {X-AUTH-KEY: value}
