Chain

Batch Output Resolver

Read-only batch lookup for up to 100 outpoints.

Page Sections

POST

`/chain/outputs/batch`

Full URL: https://forcex.com/xtract/v1/litecoin/chain/outputs/batch

Credit cost: 1 credit plus 1 credit for each additional outpoint.

curl -X POST \
  -H "Authorization: Bearer fx_live_************" \
  -H "Content-Type: application/json" \
  -d '{
  "outpoints": [
    "5cb06ac174e3afda16f32169ec9ad6bd7e0b91988520ddf49f88700e88426951:0",
    "2d3d4cbb6937777b88e44c87b56445a3f764f87f883c6f39bb6af94dd39f20b3:1"
  ]
}' \
  "https://forcex.com/xtract/v1/litecoin/chain/outputs/batch"

Parameters

No path or query parameters.

Request Body

Content type	Required	Schema
`application/json`	yes	`BatchOutputsRequest`

Example Response

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

{
  "data": {
    "outputs": [
      {
        "outpoint": "5cb06ac174e3afda16f32169ec9ad6bd7e0b91988520ddf49f88700e88426951:0",
        "value_atomic_units": 2500000,
        "spent": false
      }
    ],
    "missing": [
      "2d3d4cbb6937777b88e44c87b56445a3f764f87f883c6f39bb6af94dd39f20b3:1"
    ]
  },
  "meta": {
    "served_from": "indexed_store",
    "credit_cost": 2
  }
}

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`.
`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

This is a read-only POST so clients can send a structured body instead of a very long query string.
Use this with address history when building UTXO-style workflows client-side.