Methods

1. Verify user

This method returns the status of the user. The response of this method should block the minting of a token.

Please follow the guidelines of the method:

Do not cache the server response as the status may change. You can call this method as many times as you need
Call this method only on wallets that are users of the service
You can only call this method before a user action, e.g., harvesting or authorization. We collect behavioral analytics with this method, so don't call without user action.

POST <https://api.usejigger.com/personhood/verify>

Body

secretKey	Required.	string. Your secret key.
userWallet	Required.	string. User wallet address.
deviceId	Optional.	string. Unique device ID
https://docs.unity3d.com/ScriptReference/SystemInfo-deviceUniqueIdentifier.html
clientIP	Optional.	string. IP from which the user made the request
context	Optional.	string[]. The context in which the token is minted, for example: completing a mission, harvesting, roulette, daily bonus.
You can use several tags, for example “harvesting” and “carrots”, “mission complete” and “mission number 7”

Response

ok	boolean. Always true if no errors

Errors

HumanityCheckError

This error appears for banned users who need to pass a humanity check. Redirect the user to the "linkToValidation" link or open it in an iframe.

{
	"name": "HumanityCheckError",
	"message": "Need humanity verification",
	"code": 403,
	"type": "HumanityCheckError",
	"data": {
		"linkToValidation": "<https://verify.usejigger.com/?accessToken=>....",
		"status": "VERIFY" | "PENDING" | "REJECTED"
	}
}

We do not send messages that the user has passed verification and the iframe can be closed. Our suggestion to solve this problem is that the user can close the iframe at any time and click the action again. If it passes the check, the action will be completed successfully, if not, the iframe will open again.