POST /receipt

POST https://api.trustware.io/api/v1/route-intent/:intentId/receipt Submit the transaction hash after your signing infrastructure (or the user’s wallet) has broadcast the transaction. This is the handoff point: from the moment Trustware receives the hash, it begins tracking the cross-chain route through to final settlement. Submit this call immediately after broadcast, before any other operation. Implement retry logic around this call. If it fails and is never submitted, Trustware cannot track the route.

Path parameters

Parameter	Description
`intentId`	The `intentId` returned by `POST /route`.

Request

{
  "txHash": "0x4c8f91363c5f5e3ac2154f94995f5beac2993cc595af552c2681538af627e05d"
}

Field	Required	Description
`txHash`	Yes	The transaction hash from the broadcast.

Response

{
  "data": {
    "ok": true,
    "transaction_id": "bc5a5e82-1ecb-453b-bf78-c7c3ccdc3223"
  }
}

Field	Description
`ok`	`true` if the receipt was accepted.
`transaction_id`	Trustware’s internal transaction record ID.

Idempotency

This call is idempotent. Retrying with the same intentId and txHash is safe and will return the same response. If the broadcast succeeds but the receipt call fails, retry until you receive a successful response.

If you broadcast the transaction but never submit the receipt, Trustware cannot track or report the status of the route. Capture the transaction hash immediately after broadcast and submit it before any other operation.

Getting Started

Endpoints

Path parameters

Request

Response

Idempotency

​Path parameters

​Request

​Response

​Idempotency

Path parameters

Request

Response

Idempotency