{
  "aid": "radixdlt.com:main-v1.10.5",
  "name": "Radix Gateway API - Babylon",
  "type": "Index",
  "description": "This API is exposed by the Babylon Radix Gateway to enable clients to efficiently query current and historic\nstate on the RadixDLT ledger, and intelligently handle transaction submission.\n\nIt is designed for use by wallets and explorers, and for light queries from front-end dApps.\nFor exchange/asset integrations, back-end dApp integrations, or simple use cases, you should consider using\nthe Core API on a Node. A Gateway is only needed for reading historic snapshots of ledger states or a more robust set-up.\n\nThe Gateway API is implemented by the [Network Gateway](https://github.com/radixdlt/babylon-gateway),\nwhich is configured to read from [full node(s)](https://github.com/radixdlt/babylon-node) to extract\nand index data from the network.\n\nThis document is an API reference documentation, visit [User Guide](https://docs.radixdlt.com/) to learn more\nabout how to run a Gateway of your own.\n\n## Migration guide\n\nPlease see [the latest release notes](https://github.com/radixdlt/babylon-gateway/releases).\n\n## Integration and forward compatibility guarantees\n\nAll responses may have additional fields added at any release, so clients are advised to use JSON parsers which\nignore unknown fields on JSON objects.\n\nWhen the Radix protocol is updated, new functionality may be added, and so discriminated unions returned by the\nAPI may need to be updated to have new variants added, corresponding to the updated data. Clients may need to update\nin advance to be able to handle these new variants when a protocol update comes out.\n\nOn the very rare occasions we need to make breaking changes to the API, these will be warned in advance with\ndeprecation notices on previous versions. These deprecation notices will include a safe migration path.\nDeprecation notes or breaking changes will be flagged clearly in release notes for new versions of the Gateway.\n\nThe Gateway DB schema is not subject to any compatibility guarantees, and may be changed at any release. DB changes\nwill be flagged in the release notes so clients doing custom DB integrations can prepare.\n",
  "url": "https://raw.githubusercontent.com/jentic/jentic-public-apis/refs/heads/main/apis/openapi/radixdlt.com/main/v1.10.5/apis.json",
  "tags": [
    "radixdlt.com",
    "main"
  ],
  "created": "2026-04-11",
  "modified": "2026-04-11",
  "specificationVersion": "0.19",
  "access": "3rd-Party",
  "maintainers": [
    {
      "FN": "Jentic",
      "X-github": "jentic",
      "url": "https://github.com/jentic"
    }
  ],
  "apis": [
    {
      "aid": "radixdlt.com:main-v1.10.5",
      "name": "Radix Gateway API - Babylon",
      "description": "This API is exposed by the Babylon Radix Gateway to enable clients to efficiently query current and historic\nstate on the RadixDLT ledger, and intelligently handle transaction submission.\n\nIt is designed for use by wallets and explorers, and for light queries from front-end dApps.\nFor exchange/asset integrations, back-end dApp integrations, or simple use cases, you should consider using\nthe Core API on a Node. A Gateway is only needed for reading historic snapshots of ledger states or a more robust set-up.\n\nThe Gateway API is implemented by the [Network Gateway](https://github.com/radixdlt/babylon-gateway),\nwhich is configured to read from [full node(s)](https://github.com/radixdlt/babylon-node) to extract\nand index data from the network.\n\nThis document is an API reference documentation, visit [User Guide](https://docs.radixdlt.com/) to learn more\nabout how to run a Gateway of your own.\n\n## Migration guide\n\nPlease see [the latest release notes](https://github.com/radixdlt/babylon-gateway/releases).\n\n## Integration and forward compatibility guarantees\n\nAll responses may have additional fields added at any release, so clients are advised to use JSON parsers which\nignore unknown fields on JSON objects.\n\nWhen the Radix protocol is updated, new functionality may be added, and so discriminated unions returned by the\nAPI may need to be updated to have new variants added, corresponding to the updated data. Clients may need to update\nin advance to be able to handle these new variants when a protocol update comes out.\n\nOn the very rare occasions we need to make breaking changes to the API, these will be warned in advance with\ndeprecation notices on previous versions. These deprecation notices will include a safe migration path.\nDeprecation notes or breaking changes will be flagged clearly in release notes for new versions of the Gateway.\n\nThe Gateway DB schema is not subject to any compatibility guarantees, and may be changed at any release. DB changes\nwill be flagged in the release notes so clients doing custom DB integrations can prepare.\n",
      "image": "https://cdn.document360.io/50e78792-5410-4ac9-aa43-4612b4d33953/Images/Documentation/radix-logo-banner.png",
      "baseURL": "https://mainnet.radixdlt.com",
      "humanURL": "https://github.com/jentic/jentic-public-apis/tree/main/apis/openapi/radixdlt.com/main/v1.10.5",
      "version": "v1.10.5",
      "tags": [
        "radixdlt.com",
        "main"
      ],
      "properties": [
        {
          "type": "OpenAPI",
          "name": "OpenAPI definition",
          "url": "https://raw.githubusercontent.com/jentic/jentic-public-apis/refs/heads/main/apis/openapi/radixdlt.com/main/v1.10.5/openapi.json",
          "mediaType": "application/openapi+json"
        },
        {
          "type": "GitHubRepo",
          "url": "https://github.com/jentic/jentic-public-apis/tree/main/apis/openapi/radixdlt.com/main/v1.10.5"
        }
      ]
    }
  ]
}