SUD

Introduction

  • The application access party obtains the details of the worn NFT.

Request URL

Request Method

  • Transmission protocol: HTTPS
  • Request method: POST
  • Parameters are passed in the body in JSON format (see request example).
  • The following must be added to the header: Content-Type: application/json;charset=utf-8
  • The following must be added to the header: Authentication request header Authorization.

Request Header

Header Name Header Value
Authorization Sud-Auth <params>，see Authentication Request Header Authorization Implementation Method
RequestId Unique request ID

Request Parameters

Parameter Name Required Type Description
user_id Yes string User ID
nft_details_tokens Yes array string NFT detail token list

Request Example

{
    "app_id": "xxx",
    "user_id": "xxx",
    "nft_details_tokens": [
        "xxx"
    ]
}

Response Parameters

  • BaseResp
Parameter Name Required Type Description
ret_code Yes int Error Code
ret_msg Yes string Response information
data Yes GetNftDetailsResp Response data
  • GetNftDetailsResp
Parameter Name Required Type Description
nft_details_map Yes map<nft_details_token, GetNftDetails> NFT detail list
  • GetNftDetails
Parameter Name Required Type Description
media_type Yes int32 Media type, 1: image
rich_media_url Yes string Address
chain_type No int64 Chain network type
contract_address No string Contract address
token_id No string NFT token

Response Example

{
    "ret_code": 0,
    "ret_msg": "success",
    "data": {
        "nft_details_map": {
            "xxx" : {
                "media_type": 1,
                "rich_media_url" : "xxx",
                "chain_type": 1,
                "contract_address": "xxx",
                "token_id": "xxx"
            }
        }
    }
}

results matching ""

    No results matching ""