Gateway API v0

You can query the state of the Alphanet and send transactions by calling different endpoints of the API available under https://alphanet.radixdlt.com/v0. This is a pre-release version of the Gateway API that will be available at Babylon.

Please note that, just like the alphanet wallet, it looks nothing like what you can expect on Babylon!

You can find the full specs of this API here. We suggest importing this file inside something like PostMan to not have to remember each endpoint and required parameters.

Transaction endpoints

Submitting a transaction

After signing and notarizing your transaction intent, you can send its hex representation to this endpoint to submit it to the network.

POST https://alphanet.radixdlt.com/v0/transaction/submit

JSON body:

{
  "notarized_transaction_hex": "<string>"
}

Fetching a transaction’s status

After submitting a transaction, you will get an “intent hash”. With this, you can query the fetch the receipt of the transaction by using the following endpoint:

POST https://alphanet.radixdlt.com/v0/transaction/receipt

JSON body:

{
  "intent_hash": "<string>"
}

Querying the state of the network

Getting the current epoch

You can get the current epoch of the network with the following endpoint. You should not specify a body.

POST https://alphanet.radixdlt.com/v0/state/epoch

Fetching package data

To query the code of a particular package, you can use the following endpoint:

POST https://alphanet.radixdlt.com/v0/state/package

JSON body:

{
  "package_address": "<string>"
}

Fetching component data

You can fetch the state of a particular component, and the content of its associated vaults by querying the following endpoint:

POST https://alphanet.radixdlt.com/v0/state/component

JSON body:

{
  "component_address": "<string>"
}

Fetching resource data

You can get information about a resource manager, like its total supply and metadata, by query the following endpoint:

POST https://alphanet.radixdlt.com/v0/state/resource

JSON body:

{
  "resource_address": "<string>"
}

Fetching specific non-fungible data

To get information about an individual non-fungible token, such as its associated data, you can query the following endpoint:

POST https://alphanet.radixdlt.com/v0/state/non-fungible

JSON body:

{
  "resource_address": "<string>",
  "non_fungible_id_hex": "<string>"
}
Note that you have to provide the non fungible ID in its hex-encoded format!