> For the complete documentation index, see [llms.txt](https://taskoncommunitys-organization.gitbook.io/entity-hub-for-business-end/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/entity-hub-for-business-end/community-hub/set-up-community-tasks/api-task/api-support-for-flexible-task-configuration.md).
# API Support for Flexible Task Configuration
To enable more flexible task configurations, TaskOn provides two types of APIs: one for verifying user task completion and another for determining the number of points to be awarded. These APIs allow project teams to deeply integrate their task systems with custom business logic, enabling tailored task and incentive structures.
1. ✅ **User Task Completion Verification (Check API)**
This API is used to notify TaskOn whether a specific user has completed a task, ideal for scenarios where task completion can only be validated by the project team.
**Common Use Cases**:
* Users complete actions within the project’s system, such as registering an account, passing verification, or reaching a specific level.
* Users perform on-chain actions, such as staking, minting, or voting.
* Task completion requires cross-platform or multi-step validation, which must be uniformly assessed by the project team.\
When a user clicks *Verify*, TaskOn sends user information to your API, and you return the task status. If validated, the user receives a completion mark.
1. 🎁 **User Reward Distribution Confirmation (Reward API)**
This API facilitates the distribution of specified point rewards to users upon task completion, suitable for scenarios where you wish to control the reward distribution logic.
\
**Common Use Cases**:
* **Trading Competitions**: You host an incentive campaign based on trading volume, distributing point rewards according to users’ trading performance.
* **Referral Campaigns**: You create a “referral registration” task, awarding points based on the number of successful referrals per user.
* **Daily Check-in Tasks**: Users complete daily check-ins, with rewards determined by consecutive check-in days (e.g., 10 points for 3 consecutive days, 30 points for 7 consecutive days).
* **Contribution Incentives**: Users engage in activities like posting or answering questions in communities or forums, tracked by your backend. When claiming rewards, points are awarded based on their recorded activity level.\
When a user clicks *Verify*, TaskOn sends user information to your API, and you return the points the user should receive.
---
# 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/entity-hub-for-business-end/community-hub/set-up-community-tasks/api-task/api-support-for-flexible-task-configuration.md?ask=&goal=
```
`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.