Chain

Get Transaction

Transaction detail by transaction id.

Page Sections

GET

`/chain/transaction/{txid}`

Full URL: https://forcex.com/xtract/v1/litecoin/chain/transaction/{txid}

Credit cost: 1 credit by default. Include expansions add cost.

curl -H "Authorization: Bearer fx_test_************" \
  "https://forcex.com/xtract/v1/litecoin/chain/transaction/9567c654d507c6f439971960d3c233429d02e292115dae5d1eec5f5031ce19e6?include=inputs,outputs"

Parameters

Name	Location	Required	Type	Description
`txid`	path	yes	string	—
`include`	query	no	string \| null	—

Request Body

No request body.

Example Response

Representative trimmed response. Use the OpenAPI schema for the exhaustive field contract.

{
  "data": {
    "txid": "9567c654d507c6f439971960d3c233429d02e292115dae5d1eec5f5031ce19e6",
    "block_height": 3118767,
    "fee_atomic_units": 1280,
    "size_bytes": 242,
    "vsize": 141
  },
  "included": {
    "inputs": [],
    "outputs": []
  },
  "meta": {
    "served_from": "indexed_store",
    "included_expansions": [
      "inputs",
      "outputs"
    ],
    "credit_cost": 5
  }
}

Documented Responses

Status	Description
`200`	Successful Response
`400`	Bad request. The `error.code` field identifies the specific cause: `bad_request` (general validation failure, including malformed dates, out-of-order ranges, and request-body validation), `range_too_large` (date range exceeds the per-grain cap), `ambiguous_time_range` (legacy `from`/`to` and new `start`/`end` supplied with differing values), or `invalid_include` (unsupported expansion in `?include=`).
`401`	Authentication required, or the supplied Bearer token is invalid or revoked. `error.code` = `auth_required`.
`402`	Payment-tier gate. `error.code` identifies which gate fired: `subscription_required` (no active subscription on the account), `subscription_inactive` (subscription exists but is not active), `include_all_requires_paid_tier` (sandbox keys cannot request `?include=all`), `include_set_requires_paid_tier` (the requested include set exceeds the per-request cost cap for sandbox keys), `historical_scan_requires_paid_tier` (sandbox keys cannot scan outside the recent window), or `deep_pagination_requires_paid_tier` (sandbox keys cannot page beyond the depth cap).
`403`	Authenticated but the key lacks the required scope. `error.code` = `scope_insufficient`.
`404`	Entity not found. `error.code` = `not_found`. Returned on direct entity GETs only — the `/chain/search` endpoint returns 200 with an empty/`not_found`-shaped body instead.
`422`	Defense-in-depth: the runtime maps standard request-shape validation errors to 400, so partners normally see 400 instead of 422. This status is declared so any edge-case validation path that bypasses the override is still typed.
`429`	Rate limit or credit budget exceeded. `error.code` identifies the window: `rate_limit_exceeded` (per-second or per-minute), `quota_exceeded_daily` (sandbox per-day budget), or `quota_exceeded` (per-subscription-period). The body carries a `window` field (`second`, `minute`, `day`, or `month`) naming the failing limit. Responses include the standard `Retry-After` header.
`500`	Internal server error. `error.code` = `internal_error`. Reference `meta.request_id` when contacting support.
`503`	Service or downstream data store is temporarily unavailable, or the endpoint is not implemented in this API version. `error.code` identifies the cause: `data_unavailable` (chain tip not yet populated), `audit_unavailable` (request completed but audit could not be acknowledged — safe to retry), `plan_misconfigured` (operational issue on the API side; not a tier problem), or `endpoint_not_available` (the route is reserved and not yet served in this version).

Integration Notes

`txid` must be a 64-character lowercase hexadecimal transaction id.
Use includes when rendering transaction detail pages.