v50

latestOpenAPI 3.0.0The Radix License, Version 1.0raw.githubusercontent.com2026-04-0736336265.6 KB
Extensions

Resolve implicit requirement target from global non-fungible id

Access rules can include implicit requirements referencing special system-reserved resource addresses, which have specific meanings for the Radix Engine and are not part of the standard authorization zone system. These implicit requirements typically store their details as a hash, which means the subject of the requirement can't be easily resolved. This is where this endpoint comes in. It can resolve the subject of the implicit requirements, using a database of reverse hash lookups populated from ledger data.

The following resource addresses are supported:

  • Secp256k1 Signature Resource
  • Ed25519 Signature Resource
  • Package of Direct Caller Resource
  • Global Caller Resource
  • System Execution Resource

When querying, you must provide a pair of the following for each requirement to resolve:

  • resource_address (one of the above)
  • non_fungible_id, of the requirement.

You can query a maximum of 100 implicit requirements at a time.

See the documentation on implicit-requirements for more information.

post/extensions/implicit-requirements/lookup

Request body

Example request

{
  "requirements": [
    {
      "resource_address": "<sample-implicit-requirement-resource-address>",
      "non_fungible_id": "<sample-implicit-requirement-non-fungible-id>"
    }
  ]
}

Response

List of resolved implicit requirements.