Scanner API Guidelines
Development guide prepared for the implementation of additional functions after NFT holder verification.
Introduction
This document is a development guideline prepared for implementing additional functions after NFT holder verification.
Understanding of SDKs such as web3.js and ethers may be required to implement blockchain-related functions.
If you develop an API endpoint server by referring to this document, you can add the features of the example below.
Check how many NFTs the user who authenticated the wallet has Send NFTs or tokens to users recognized by the scanner Offline Stamp tour using FAVORLET and FAVORLET Scanner Access check and record management at offline holder party Various functions suitable for other situations
Please refer to the Basic usage guideline page for basic usage guide for FAVORLET scanner.
How to set End point URL

You can receive a request to the registered API server after scanning the user's authentication QR code by putting it in the service endpoint URL on the scanner setting screen.
On the scanner settings screen, you can set in the following three ways.
If only the
collection contract addressis entered: Only the scanner's NFT holder will be verified.If you only put the
service endpoint URL: Skip scanner's NFT holder verification and send request to API server.If you put both the
collection contract addressandservice endpoint URL: Send a request to the API server after verifying the scanner's NFT holder.
Either the collection contract address or the service endpoint URL must be entered
Flow
The flow of communication between FAVORLET, Scanner, and Server is as below.

FAVORLET users generate a verification QR.
The scanner checks the QR code whether it is valid or not and passes the wallet address and other information to the endpoint URL (API server) you set.
The requested API server responds with a scanner for success or failure.
Specifications
Request
This is the data that FAVORLET scanner request to the API server set as the service endpoint URL.
Method: POST
Header: Content-Type:application/json
Body
Parameter Description
walletAddress
string
This is the wallet address delivered through QR verification.
contractAddress
string
This is the address registered in the collection contract address on the scanner settings screen.
If left blank, no data will appear.
signature
string
This is the data for verifying whether walletAddress and expireTime have changed. The usage of the value is optional, see below for detailed explanation.
expireTime
string
The expiration date for the QR code generated by the user. The format is YYYY-MM-DDTHH:mm:ss.sssZ.
Response
This is the data that the API server you set as the service endpoint URL should respond with FAVORLET scanner.
Header: Content-Type:application/json
Case1: success
Case2: fail
Screenshot

Parameter Description
success
boolean
์์ฒญ์ ๋ํ ์ฑ๊ณต ์ฌ๋ถ์ด๋ฉฐ true๋๋ false๋ฅผ ๋ฐํํด์ผ ํฉ๋๋ค.
title
string
์ค์บ๋์์ ์์ฒญ ๊ฒฐ๊ณผ ํ์ ์ ๋ชฉ์ ํ์๋๋ ํ ์คํธ์ ๋๋ค.
reason
string
์ค์บ๋์์ ์์ฒญ ๊ฒฐ๊ณผ ํ์ ์ค๋ช ์ ํ์๋๋ ํ ์คํธ์ ๋๋ค.
API ์๋ฒ ์์ (Node.js)
1. Node.js ์ค์น
2. ํ๋ก์ ํธ ํด๋ ์์ฑ ๋ฐ ์ด๋
3. ํจํค์ง ์ค์น
4. index.js ํ์ผ ์์ฑ
5. ํฐ๋ฏธ๋์์ ์คํ
6. ์ ํฐ๋ฏธ๋์์ ํ ์คํธ
7. ๊ฒฐ๊ณผ ํ์ธ
Last updated