What information can we obtain?

You can retrieve various user-related data from the blockchain, depending on what data is stored on the blockchain and accessible through appropriate queries or APIs. Here are some typical types of data you can obtain:

  1. Wallet Address: Every blockchain user has a unique wallet address that serves for identification. You can use it for user identity verification.

  2. Transaction History: You can check the transaction history associated with a user's wallet address. This includes both incoming and outgoing transactions, along with details like the amount, date, and the recipient's or sender's address.

  3. Account Balance: You can check a user's current account balance on the blockchain, which can be useful for determining if the user meets specific access conditions.

  4. NFT Tokens: If you use non-fungible tokens (NFTs), you can check which NFTs a user owns in their collection.

  5. Transaction Set Data: For more advanced applications, you can collect data about sets of transactions a user has made or is associated with. This may include data about smart contracts or recorded operations.

  6. Interaction History with Contracts: If a user has interacted with specific smart contracts on the blockchain, you can gather data about those interactions, such as invoked functions and passed parameters.

  7. Token Metadata: In the case of NFTs, each token may contain metadata describing its properties and appearance. These metadata can be used in games or applications to create interactive experiences.

  8. Voting or Delegation History: If you're working on a blockchain that supports voting or delegation, you can access a user's history of votes or delegations to verify their participation in these processes.

The availability of this information will depend on the blockchain your application operates on and the available developer tools and interfaces. It's essential to follow privacy and data protection rules when collecting and using this information.

Example of an Endpoint Used in our 'Users' Explorer to retrieve information about a user and data that was filled up in our Marketplace

GET user-service/profiles?queryParameters

Returns information about the selected profiles according to the given query parameters - e.g. wallet addresses and roles, it can be sorted according to the creation date, and the updated date and there can be a limit of the returned profiles array.


Authorization Headers:

  • There is no need for authorization, it is a public endpoint.

Query parameters:




(number, optional): The number of records to skip in the response.


(number, optional): The maximum number of records to return in the response.


(string, optional) Sort by a specific wallet to retrieve information.


(string, optional) Elympics identifier for optimal user identification.


(string, optional) Role of the user.

createdAt (sort)

(string, optional) Sort by the user's creation date on our platform.

updatedAt (sort)

(string, optional) Sort by the user's last update date.

visitedAt (sort)

(string, optional) Sort by the user's last visit date.

Example cURL
curl 'https://api.metaproprotocol.com/users-service/profiles?wallets=0x832735f45299c8b6f7263e758cadba766459cd21&limit=9999' \
  -H 'authority: api.metaproprotocol.com' \
  -H 'accept: */*' \
  -H 'accept-language: pl-PL,pl;q=0.9,en-US;q=0.8,en;q=0.7' \
  -H 'cache-control: no-cache' \
  -H 'origin: https://metapromarket.com' \
  -H 'pragma: no-cache' \
  -H 'referer: https://metapromarket.com/' \
  -H 'sec-ch-ua: "Not.A/Brand";v="8", "Chromium";v="114", "Google Chrome";v="114"' \
  -H 'sec-ch-ua-mobile: ?0' \
  -H 'sec-ch-ua-platform: "Linux"' \
  -H 'sec-fetch-dest: empty' \
  -H 'sec-fetch-mode: cors' \
  -H 'sec-fetch-site: cross-site' \
  -H 'user-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/ Safari/537.36' \
Example response body (200 OK)
    "results": [
            "_id": "631e4bb31e8b6a43b8a53d71",
            "id": "7c291368-c590-411c-b226-7a2b89010747",
            "userId": "7c291368-c590-411c-b226-7a2b89010747",
            "role": [
            "addresses": [
                    "wallet": "0x832735f45299c8b6f7263e758cadba766459cd21",
                    "chainId": 56,
                    "userId": "7c291368-c590-411c-b226-7a2b89010747",
                    "createdAt": "2022-09-11T20:57:23.777Z",
                    "updatedAt": "2022-09-11T20:57:23.777Z"
            "socialMedia": [],
            "createdAt": "2022-09-11T20:57:23.784Z",
            "updatedAt": "2023-09-28T05:51:28.642Z",
            "visitedAt": "2023-09-28T05:51:28.642Z",
            "personalDetails": {
                "username": "Meta Dude",
                "bio": "MetaDude is an integral part of our team, responsible for crafting the core assets that define our digital projects.\nWith a remarkable blend of artistic vision and technical expertise, MetaDude brings to life visually stunning 3D models, textures, animations, and audio assets.",
                "avatar": "https://prdmetaprousers.blob.core.windows.net/avatars/fbd27456-3bf6-4f9d-b2b5-cce06d1a453e.jpeg",
                "banner": "https://prdmetaprousers.blob.core.windows.net/banners/dc08d8ad-e45a-4198-9c26-786ef6739ca5.jpeg"
    "count": 1
Example of the response body (400 Bad Request)
   "statusCode": 400,
       "messages": [
            "Incorrect username or wallet address"
       "error": "Bad Request"
Example of the response body (404 Not found)
    "statusCode": 404,
    "messages": [
      "Not Found"
    "error": "Not Found"
Additional information regarding the wallet address path
  • When there is an invalid wallet address syntax, then a 400 error code will be thrown

  • When the wallet address is valid but does not exist in the registry, then a 404 error code will be thrown

Last updated