> For the complete documentation index, see [llms.txt](https://taskoncommunitys-organization.gitbook.io/guide-book/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://taskoncommunitys-organization.gitbook.io/guide-book/community-hub/task-system/task-templates/api-task/taskon-performance-based-api-verification-guide.md).

# TaskOn Performance-Based API Verification Guide

## **Overview**

This task template is ideal for trading competitions, allowing you to **sync points** to TaskOn. For example, users with higher trading volume can earn more points, motivating them to strive for greater achievements.The system supports two types of user identifiers:

**1.1 Supported ID Types**

1. **Social Media Account ID**
   1. Twitter handle (e.g., taskonxyz)
   2. Discord ID (e.g., 1084460817220641111)
   3. Telegram ID (e.g., 6881505111)
   4. Email Address (e.g., <abc@gmail.com>)
2. **Blockchain Wallet Address**
   1. Supported chains: EVM, Solana, Starknet, Sui, Tron, BTC, Aptos, Nibiru

## **Integration Guide**

**2.1 Quick Start**

* **Demo project**: <https://github.com/Taskon-xyz/taskon-verification-demo>
* Features:&#x20;
  * **One-click** Vercel deployment
  * Ready-to-use application template
  * Complete integration example

**2.2 API Specifications**

**Endpoint**

`GET https://<domain>/<serverpath>?address=<identifier>`

**Response Format**

`{  "result": { "point": 100 // Indicates task completion result } }`

**Important Notes**

* All API endpoints must be publicly accessible
* Optional bearer token support for TaskOn-exclusive access
* All identifiers are converted to **lowercase** for consistency
* Always return HTTP 200 status code
* Use `point` integer to indicate task completion result

**2.3 Example Request**

`GET <https://your-app.vercel.app/api/task/verification?address=0xd5045deea369d64ab7efab41ad18b82eeabcdefg`>

## **Task Configuration Steps**

**3.1. Slect API Task**

* Go to the TaskOn dashboard and click on the "API Task" tab.
* Click on the "Performance-Based Task" button.

**3.2 Click on the "Set API URL" button.**

**3. Fill the api url**

* URL: If you use this repo and vercel, it shoud be like this: `https://xxx.vercel.app/api/task/verification`
* \[Optional] Bearer Token: Enable this to restrict API access to TaskOn only.

**4. Verify Configuration & Confirm Your Settings**

* **Purpose:** Ensure everything works smoothly.
* **Provide:** User ID that has points reward

\
After verification, it's all done.&#x20;

## How it works

From the user side, users need to manually claim points for the first task completion. Afterward, points can be updated automatically via API when users click the refresh button.

![](https://ontology.larksuite.com/space/api/box/stream/download/asynccode/?code=NjcyMWRmZmM3ZGQ1YTk4MTAyZTVlMTcwZTIzYjYxOTJfZmNiQkNEbndrUEV2dndxUXpleG5KZUNUaXg3ZllIRGVfVG9rZW46VUo2Z2JuWkhSb255V3Z4ZFc2NXVITmtPc3ZoXzE3MzUwOTIwMjI6MTczNTA5NTYyMl9WNA)

![](https://ontology.larksuite.com/space/api/box/stream/download/asynccode/?code=ZWU5NmY3MmRmODdkMjkyNWQwYTE5YzcyMjc5MjJkMjRfZTRzb3RQd3BOT2FzYlZDd3o4V3JuNm4yVThxbWxveVhfVG9rZW46SURjMGJQSnpHb0VsNW14VUVtZ3V1ZEFYc2FjXzE3MzUwOTIwMjI6MTczNTA5NTYyMl9WNA)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://taskoncommunitys-organization.gitbook.io/guide-book/community-hub/task-system/task-templates/api-task/taskon-performance-based-api-verification-guide.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.