🛑Verify Errors

While using the API or SDK you may encounter errors if you format a request wrong or exceed your rate limit. Below are a list of the errors you may receive, in addition to app-level errors.

Verify error codes are prefixed with verify/ (omitted in the tables below)

Unlockables

These errors occur when creating, editing or requesting unlockables.

HTTP Status	Code	Message
400	unlockable/invalid-name	Unlockable name is already in use
400	unlockable/invalid-json	JSON is invalid
400	unlockable/unsupported-type	Unlockable type is not supported
400	unlockable/webhook-failed	Webhook returned a non 2XX status code
400	unlockable/webhook-timeout	Webhook request timed out (maximum duration is 10s)
400	unlockable/webhook-invalid-url	Webhook URL could not be parsed
400	unlockable/webhook-invalid-protocol	Webhook protocol is invalid or unsupported (supports http, https and ipfs)
400	unlockable/webhook-unroutable	Webhook looks like an internal IP address
400	unlockable/webhook-unexpected-content	Content-Type header must be application/json, text/plain or text/html
403	unlockable/token-expired	Token expired, please complete verification again
404	unlockable/not-found	Unlockable not found

Marketplace integration

These errors occur when passing the marketplace option during verification requests.

HTTP Status	Code	Message
400	marketplace/invalid-slug	Collection slug not found
400	marketplace/invalid-contract	Collection contract not found

Address verification

These errors occur when completing the nonce/challenge process to verify address ownership.

HTTP Status	Code	Message
400	address/invalid-nonce	Invalid nonce
400	address/invalid-nonce-used	Invalid nonce, already used
400	address/invalid-signature	Invalid signature
400	address/invalid-hmac	Invalid HMAC

User

These errors occur when passing a user.id and HMAC to the verification request.

HTTP Status	Code	Message
400	user/invalid-hmac	Invalid HMAC