Trade Trust Finality

How final an L2 transaction is, via core-engine.

Get transaction finality

get

Confirmation depth and L1 settlement for one transaction. Read confirmations and l1Settled; final means only "mined" here.

Authorizations

X-API-KeystringRequired

AWS API Gateway key, required only on the api-sandbox and api-v2 servers. It is checked by the gateway, before the request reaches this service, so it does not substitute for the bearer token - those two headers are read by different layers. Omit it when port-forwarding to a pod.

AuthorizationstringRequired

OAuth2 bearer token from the shared BaaS auth server.

Every endpoint in this subset requires one. Note the security filter runs BEFORE routing, so an unauthenticated request to a path that does not exist also answers 401, not 404 - a 404 is only visible to an authenticated caller.

Path parameters

txHashstringRequired

Responses

200

OK

*/*

Standard BaaS response envelope. Mirrors the shape used across the microservices so callers get a consistent contract on L2 as on L1.

successbooleanOptional

errorCodestringOptional

messagestringOptional

get/tradetrust/finality/{txHash}

GET /z2/tradetrust/finality/{txHash} HTTP/1.1
Host: api-sandbox.zetrix.com
X-API-Key: YOUR_API_KEY
Authorization: Bearer YOUR_SECRET_TOKEN
Accept: */*

200

OK

{
  "success": true,
  "errorCode": "text",
  "message": "text",
  "data": {
    "l2Block": 1,
    "confirmations": 1,
    "l1Settled": true,
    "final": true
  }
}