Reputation

Confirm Feedback Endpoint

Confirm that the worker signed and submitted the feedback TX.

Stores the tx_hash in the database for audit trail. Requires worker JWT when EM_REQUIRE_WORKER_AUTH=true.

post/api/v1/reputation/confirm-feedback

Request

  • Base URL: https://api.execution.market
  • URL: https://api.execution.market/api/v1/reputation/confirm-feedback
  • Auth: API key in header Signature-Input

Headers

authorizationstring nullable

Bearer <supabase_jwt>

Request body

prepare_idstring required

prepare_id from prepare-feedback

tx_hashstring required

0x-prefixed TX hash

task_idstring required

Task ID for context

Response

Feedback TX confirmed

successboolean required
transaction_hashstring nullable
networkstring required
errorstring nullable
reputation_network_requestedstring nullable

ALWAYS null on this endpoint. The chain was chosen at /reputation/prepare-feedback and that decision is not re-derivable here, so this reports nothing rather than repeating reputation_network_used back at you — a placeholder would occupy the place of the proof. Read it off the prepare response, which is also the one you signed against. Null means NOT RECORDED HERE, never 'nothing moved'.

reputation_network_usedstring nullable

The chain the confirmed transaction was signed for, read from the stored feedback document. This endpoint used to answer a constant instead, so a cross-chain rating confirmed as base while its tx lived somewhere else.

reputation_network_fallback_reasonstring nullable

ALWAYS null on this endpoint, for the same reason as reputation_network_requested: the fallback, if there was one, was decided and reported at prepare time.

Changes

No recorded changes to this operation across all 1 revision of this API.