Overview

• To customize your on-chain quest, Micro3 will require API verification for specific actions.
• After Micro3 transfers the addresses to the projects, the projects will verify them. Once the verification results are available, Micro3 will determine if the specified actions have been completed to pass the tasks.

Specifics

• The TARGET/API URL cannot be modified once the corresponding information has been submitted.
• Micro3 will review the API first to ensure functionality and the pin value.
• The API used for verification must be open.
• Note that the user's address currently only supports EVM.

Get API

https://<domain>/<serverpath>?address=<userAddress>

Request parameter format:

type RequestPayload = {
    // error can be optionally provided when result is false
    error?: {
        // this is the error code you defined to provider more context (e.g. UNKNOWN_ERROR, 0)
        code: string | number;
        // this is the error message you defined to provider more context (e.g. Unknown error occurred)
        message: string;
    };
    data: {
        // whether the user has done the task
        result: boolean;
    };
};

Example:

• If you wish to set up an on-chain Quest, for example, trading volume = $100 on the Micro3 platform, you need to provide this API to Micro3.

• The parameter address=<user address> will always be included in the API Endpoint.

  Get API example:

  • [https://micro3.io/?address=<useraddress>volume=1&ttrade=1](https://micro3.io/?address=<useraddress>&volume=1&ttrade=1)

  Successful Response Example

  Success:
  {
       "data": 
           "result”: true
       }
  }
  

  Failed Response Example

  Failed
  {
      "error": {
          "code": 0,
          "message": "error message"
       },
       "data": 
           "result”: false
       }
  }
  

What is Micro3 ID?

What are the benefits of M3G?