---
title: "Get Subintent Status"
method: POST
path: "/transaction/subintent-status"
tags: ["Transaction"]
---

# Get Subintent Status

`POST /transaction/subintent-status`

Returns if the given subintent has been finalized.

## Request body

- TransactionSubintentStatusRequest
  - `subintent_hash` string, required — Bech32m-encoded hash.

## Response `200`

Transaction Status

- TransactionSubintentStatusResponse
  - `ledger_state` LedgerState, required — The ledger state against which the response was generated. Can be used to detect if the Network Gateway is returning up-to-date information.
    - `network` string, required — The logical name of the network
    - `state_version` integer, required — The state version of the ledger. Each transaction increments the state version by 1.
    - `proposer_round_timestamp` string, required — The proposer round timestamp of the consensus round when this transaction was committed to ledger. This is not guaranteed to be strictly increasing, as it is computed as an average across the validator set. If this is significantly behind the current timestamp, the Network Gateway is likely reporting out-dated information, or the network has stalled.
    - `epoch` integer, required — The epoch number of the ledger at this state version.
    - `round` integer, required — The consensus round in the epoch that this state version was committed in.
  - `subintent_status` 'Unknown' | 'CommittedSuccess', required — The finalization status of this subintent. Each subintent can only be *successfully* committed once, but unlike a transaction intent, could be committed as a failure zero or more times first.
  - `subintent_status_description` string, required — An additional description to clarify the `subintent_status`.
  - `finalized_at_state_version` integer, nullable — The state version when the subintent was finalized (committed as a success). This field is only present if the status is `CommittedSuccess`.
  - `finalized_at_transaction_intent_hash` string — Bech32m-encoded hash.

## Other responses

- `4XX` — Client-originated request error

---

[API](https://skmtc.net/radixdlt/apis/radix-gateway-api-babylon.md) · [All operations](https://skmtc.net/radixdlt/apis/radix-gateway-api-babylon/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/radixdlt/radix-gateway-api-babylon/versions/153aecf74342/schema)