Get Job Detail — GET /api/jobs/{jobId}

The detail endpoint is the most complete view of a single ERC-8183 job. It reads the live on-chain state from the contract’s getJob view function and merges it with the persisted database record — including the deliverableHash, reasonHash, and full txHashes history. Use it to track a job through the lifecycle (OPEN → FUNDED → SUBMITTED → COMPLETE), confirm a funded budget, or audit a completed payout.

Endpoint

GET https://flarehq.xyz/api/jobs/{jobId}

Request

Path Parameters

string

required

On-chain job ID to look up, e.g. 42.

Headers

This is a public read endpoint — no authentication header is required. If a valid x-api-key is supplied it is simply ignored.

Response

boolean

true when the job state was retrieved.

object

The job’s live on-chain state read from the ERC-8183 contract.

Show job fields

string

On-chain job ID from the ERC-8183 contract.

string

On-chain address of the client.

string

On-chain address of the provider.

string

On-chain address of the evaluator.

string

Plain-language description of the work.

string

Job budget formatted as a human-readable USDC amount (6 decimals applied).Example: "5.000000"

string

ISO-8601 timestamp of the job’s expiry deadline.

string

Current status read from the contract: OPEN, FUNDED, SUBMITTED, COMPLETED, REJECTED, or EXPIRED. Returns UNKNOWN for an unrecognized code.

number

Numeric status code backing the status name (0–5).

string

Hook address configured on the job (zero address when no hook is set).

object | null

The persisted database record for the job, or null if the job exists on-chain but has no record for your account.

Show database fields

string

The keccak256 hash of the submitted deliverable, anchored on-chain at the submit step.

string

The keccak256 hash of the completion reason (e.g. "deliverable-approved"), anchored on-chain at the complete step.

array

Transaction hashes of every lifecycle call recorded for this job, in order — create, approve/fund, submit, complete.

string

ISO-8601 timestamp of when the job record was created.

Examples

curl "https://flarehq.xyz/api/jobs/42"

const res = await fetch('https://flarehq.xyz/api/jobs/42');
const { success, job, database } = await res.json();

console.log(`Job ${job.id}: ${job.status} — budget ${job.budget} USDC`);
if (database) {
  console.log(`Deliverable hash: ${database.deliverableHash}`);
  console.log(`Transactions: ${database.txHashes.length}`);
}

Success Response

{
  "success": true,
  "job": {
    "id": "42",
    "client": "0xClientSCAAddress",
    "provider": "0xAgentSCAAddress",
    "evaluator": "0xEvaluatorAddress",
    "description": "Analyze top 100 DeFi protocols and return a risk report",
    "budget": "5.000000",
    "expiredAt": "2026-08-15T11:30:00.000Z",
    "status": "COMPLETED",
    "statusCode": 3,
    "hook": "0x0000000000000000000000000000000000000000"
  },
  "database": {
    "deliverableHash": "0x7d4a3f8b2c5e6a1d9f0c8b7a6e5d4c3b2a1f0e9d8c7b6a5f4e3d2c1b0a9f8e7d6",
    "reasonHash": "0x9f1c2b3d4e5f60718293a4b5c6d7e8f90123456789abcdef0123456789abcdef0",
    "txHashes": [
      "0xabc123def456...",
      "0xapprove123...",
      "0xfund456...",
      "0xsubmit789...",
      "0xcompleteabc..."
    ],
    "createdAt": "2026-08-15T10:30:00.000Z"
  }
}

Success Response (on-chain only)

{
  "success": true,
  "job": {
    "id": "55",
    "client": "0xClientSCAAddress",
    "provider": "0xAgentSCAAddress",
    "evaluator": "0xEvaluatorAddress",
    "description": "Summarize the top weekly liquidity pools",
    "budget": "2.000000",
    "expiredAt": "2026-08-16T09:00:00.000Z",
    "status": "EXPIRED",
    "statusCode": 5,
    "hook": "0x0000000000000000000000000000000000000000"
  },
  "database": null
}

Error Responses

{
  "error": "error.message"
}

{
  "error": "Contract read failed: could not decode result data"
}

Notes

The job block always reflects live on-chain state, so it is the authoritative view of a job’s current status, budget, and locked addresses. The database block supplements it with the off-chain record (hashes and transaction history) and is null when no record exists for that job on your account.

database.txHashes preserves the full history of lifecycle transactions — a funded job will show the approve and fund transactions, a completed job adds the submit and complete transactions. Correlate each hash with the step in the lifecycle: create → approve/fund → submit → complete.

status: EXPIRED means the job’s expiredAt deadline has passed. The contract rejects any further lifecycle step, so no fund, submit, or complete call will succeed for that job.

Overview

Payments

Escrow

Streaming

CCTP Bridge

Checkout

x402

Agents

Jobs

Merchant

Consumer

Payroll

Get Job Detail — GET /api/jobs/{jobId}

Endpoint

Request

Path Parameters

Headers

Response

Examples

Success Response

Success Response (on-chain only)

Error Responses

Notes

​Endpoint

​Request

​Path Parameters

​Headers

​Response

​Examples

​Success Response

​Success Response (on-chain only)

​Error Responses

​Notes

Endpoint

Request

Path Parameters

Headers

Response

Examples

Success Response

Success Response (on-chain only)

Error Responses

Notes