---
title: "Get Non-Fungible Location"
method: POST
path: "/state/non-fungible/location"
tags: ["State"]
---

# Get Non-Fungible Location

`POST /state/non-fungible/location`

Returns location of a given non-fungible ID.

## Request body

- StateNonFungibleLocationRequest — defines upper boundary (inclusive) for queried data. i.e `{ "at_state_version" = {"epoch" = 10} }`, will return data till 10 epoch.
  - `at_ledger_state` LedgerStateSelector, nullable — Optional. This allows for a request to be made against a historic state. If a constraint is specified, the Gateway will resolve the request against the ledger state at that time. If not specified, requests will be made with respect to the top of the committed ledger.
    - `state_version` integer, nullable — If provided, the latest ledger state lower than or equal to the given state version is returned.
    - `timestamp` string, date-time, nullable — If provided, the latest ledger state lower than or equal to the given round timestamp is returned.
    - `epoch` integer, nullable — If provided, the ledger state lower than or equal to the given epoch at round 0 is returned.
    - `round` integer, nullable — If provided must be accompanied with `epoch`, the ledger state lower than or equal to the given epoch and round is returned.
  - `resource_address` string, required — Bech32m-encoded human readable version of the address.
  - `non_fungible_ids` NonFungibleId[], required — limited to max 100 items.

## Response `200`

Non-Fungible ID Location

- StateNonFungibleLocationResponse
  - `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.
  - `resource_address` string, required — Bech32m-encoded human readable version of the address.
  - `non_fungible_ids` StateNonFungibleLocationResponseItem[], required
    - `non_fungible_id` string, required — String-encoded non-fungible ID.
    - `owning_vault_address` string — Bech32m-encoded human readable version of the address.
    - `owning_vault_parent_ancestor_address` string — Bech32m-encoded human readable version of the address.
    - `owning_vault_global_ancestor_address` string — Bech32m-encoded human readable version of the address.
    - `is_burned` boolean, required
    - `last_updated_at_state_version` integer, required — The most recent state version underlying object was modified at.

## 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/revisions/153aecf74342/schema)