Submit Task Work
API integration guide for submitting evidence for a committed project task
Submit Task Work
Submitting task work allows a contributor to provide evidence of completion for a task they have committed to. This updates the on-chain state with the contributor's submission, making it available for manager assessment. The transaction confirms the submission in the database with the contributor's evidence.
Summary
| Property | Value |
|---|---|
| System | Project |
| Role | Contributor |
| Type Key | task_submit |
| Build Endpoint | POST /api/v2/tx/project/contributor/task/action |
| DB Sync | Yes |
| Service Fee | 0 ADA |
| Est. Wallet Cost | ~0.35 ADA |
The estimated wallet cost covers the transaction fee only. This is a lightweight transaction with no service fee or additional deposits.
Build Transaction
Endpoint
POST /api/v2/tx/project/contributor/task/action
Request Body
{
"alias": "contributor1",
"project_id": "a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4",
"project_info": "PR #42 merged: onboarding flow complete",
"initiator_data": {
"usedAddresses": ["addr1qx2fxv2umyhttkxyxp8x0dlpdt3k6cwng5pxj3jhsydzer3n0d3vllmyqwsx5wktcd8cc3sq835lu7drv2xwl2wywfgse35a3x"],
"changeAddress": "addr1qx2fxv2umyhttkxyxp8x0dlpdt3k6cwng5pxj3jhsydzer3n0d3vllmyqwsx5wktcd8cc3sq835lu7drv2xwl2wywfgse35a3x"
}
}| Field | Type | Required | Description |
|---|---|---|---|
alias | string (Alias) | Yes | The contributor's access token alias. Must have already committed to a task in this project. |
project_id | string (GYMintingPolicyId) | Yes | 56-character hex policy ID returned from project creation. |
project_info | string | No | Evidence for the submission, such as a link to a pull request or description of completed work. Maximum 140 characters. |
initiator_data | WalletData | No | Object containing usedAddresses (string[]) and changeAddress (string). If omitted, the Gateway resolves wallet data from the authenticated session. |
Response
{
"unsigned_tx": "84a800..."
}The response contains the unsigned transaction CBOR, ready for the user's wallet to sign.
Register Transaction
After the user signs and submits the transaction, register it with the state machine:
POST /api/v2/tx/register
{
"tx_hash": "64-char hex hash from wallet.submitTx()",
"tx_type": "task_submit"
}No metadata is required. On confirmation, the state machine records the task submission in the database with the contributor's evidence.
Note: Task Leave and Task Update sub-actions have build endpoints but are not yet tracked by the state machine. The on-chain effects of those actions still work, but they will not trigger database sync or state transitions.
Related API Endpoints
| Endpoint | Description |
|---|---|
GET /api/v2/projects/{project_id}/tasks | Fetch all tasks including submission status per contributor |
Example: Full Lifecycle
const API_URL = "https://api.andamio.io";
// 1. Build
const buildRes = await fetch(`${API_URL}/api/v2/tx/project/contributor/task/action`, {
method: "POST",
headers: {
"Content-Type": "application/json",
"X-API-Key": API_KEY,
"Authorization": `Bearer ${userJwt}`,
},
body: JSON.stringify({
alias: "contributor1",
project_id: projectId,
project_info: "PR #42 merged: onboarding flow complete",
initiator_data: {
usedAddresses: [walletAddress],
changeAddress: walletAddress,
},
}),
});
const { unsigned_tx } = await buildRes.json();
// 2. Sign
const signedTx = await wallet.signTx(unsigned_tx);
// 3. Submit
const txHash = await wallet.submitTx(signedTx);
// 4. Register
await fetch(`${API_URL}/api/v2/tx/register`, {
method: "POST",
headers: {
"Content-Type": "application/json",
"X-API-Key": API_KEY,
"Authorization": `Bearer ${userJwt}`,
},
body: JSON.stringify({
tx_hash: txHash,
tx_type: "task_submit",
}),
});
// 5. Monitor (SSE)
const events = new EventSource(
`${API_URL}/api/v2/tx/stream/${txHash}`
);
events.addEventListener("state_change", (e) => {
const data = JSON.parse(e.data);
console.log(`State: ${data.old_state} → ${data.new_state}`);
});
events.addEventListener("complete", (e) => {
const data = JSON.parse(e.data);
console.log(`Final: ${data.final_state}`);
events.close();
});See Also
- Transaction State Machine -- Lifecycle overview
- Contributor: Commit to Task -- Commit before submitting
- Manager: Assess Tasks -- What happens after submission