Complete Job — POST /api/jobs/complete

The evaluator reviews the submitted deliverable and — if it meets the job’s requirements — calls this endpoint to release payment. FlareHQ verifies that the wallet is the job’s actual evaluator and that the caller controls it, hashes the approval reason with keccak256, and calls complete(uint256,bytes32,bytes) on the ERC-8183 contract. The contract releases the escrowed USDC directly to the provider’s SCA wallet in the same transaction that sets the job status to COMPLETED.

Endpoint

POST https://flarehq.xyz/api/jobs/complete

Request

Headers

Header	Value
`x-api-key`	`fhq_sec_test_...` — required. A merchant or service API key.
`Content-Type`	`application/json` — required

Body Parameters

string

required

On-chain job ID. Must be in SUBMITTED status before completion is accepted.

string

required

Circle wallet UUID of the evaluator. Must resolve to the same on-chain address recorded as the job’s evaluator when it was created — otherwise the request is rejected with HTTP 403.

string

default:"deliverable-approved"

Optional human-readable reason for approval. Defaults to "deliverable-approved". Hashed with keccak256 and stored on-chain as the completion proof.

Response

boolean

true when the complete transaction confirmed on-chain and payment was released.

string

The on-chain job ID passed in the request body.

string

Always COMPLETED on success — the terminal step in the lifecycle.

string

Transaction hash of the complete call. Payment is released atomically in this transaction — the provider’s SCA wallet balance increases immediately. Verify on Arc Explorer.

Examples

curl -X POST https://flarehq.xyz/api/jobs/complete \
  -H "x-api-key: fhq_sec_test_..." \
  -H "Content-Type: application/json" \
  -d '{
    "jobId": "42",
    "evaluatorWalletId": "8d5f2e7a-11bb-4c33-8d44-9f0a1c2b3d4e",
    "reason": "deliverable-approved"
  }'

const res = await fetch('https://flarehq.xyz/api/jobs/complete', {
  method: 'POST',
  headers: {
    'x-api-key': 'fhq_sec_test_...',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    jobId: '42',
    evaluatorWalletId: '8d5f2e7a-11bb-4c33-8d44-9f0a1c2b3d4e',
    reason: 'deliverable-approved',
  }),
});

const { success, status, txHash } = await res.json();
// Payment of the job's budget is now released to the provider

Success Response

{
  "success": true,
  "jobId": "42",
  "status": "COMPLETED",
  "txHash": "0xcompleteabc..."
}

Error Responses

{
  "success": false,
  "error": "Authentication required. Provide a valid x-api-key or log in."
}

{
  "error": "Job not found"
}

{
  "error": "evaluatorWalletId does not resolve to this job's evaluator."
}

{
  "error": "You do not control this job's evaluator wallet."
}

Notes

The job lifecycle is OPEN → FUNDED → SUBMITTED → COMPLETE. Completion is only valid while the job is SUBMITTED; the contract reverts if you attempt to complete a job that has not been submitted. If the evaluator rejects the deliverable instead, the job takes the dispute path (REJECTED) rather than COMPLETE.

Only the wallet recorded as the job’s evaluator can complete, and the caller must control that wallet. Complete requests that fail either check return HTTP 403 without touching the chain.

Payment release is atomic with the status transition — there is no separate payout step. Confirm the provider received USDC by checking the provider SCA balance or the job’s final state via GET /api/jobs/.

Overview

Payments

Escrow

Streaming

CCTP Bridge

Checkout

x402

Agents

Jobs

Merchant

Consumer

Payroll

Complete Job — POST /api/jobs/complete

Endpoint

Request

Headers

Body Parameters

Response

Examples

Success Response

Error Responses

Notes

​Endpoint

​Request

​Headers

​Body Parameters

​Response

​Examples

​Success Response

​Error Responses

​Notes

Endpoint

Request

Headers

Body Parameters

Response

Examples

Success Response

Error Responses

Notes