# Integration guide

{% hint style="success" %}
Do you work at a Bank, Financial Institution or a Cryptocurrency Exchange? Its easy to integrate XRPSCAN in your application. We support deep links for accounts, transactions, ledgers, amendments, NFTs and validator nodes. All pages support desktop as well as mobile layouts.
{% endhint %}

## Account

To link to an account, construct a URL like this:

{% code title="Mainnet" %}

```
https://xrpscan.com/account/{ACCOUNT}
```

{% endcode %}

{% code title="Testnet" %}

```
https://testnet.xrpscan.com/account/{ACCOUNT}
```

{% endcode %}

> [`https://xrpscan.com/account/rGeyCsqc6vKXuyTGF39WJxmTRemoV3c97h`](https://xrpscan.com/account/rGeyCsqc6vKXuyTGF39WJxmTRemoV3c97h)

`ACCOUNT` in the XRP Ledger is identified by an address in the Base58 format. An account address has the following properties:

* A string of length between 25 to 35 characters.
* Starts with the character `r`.
* Is case sensitive.
* Uses alphanumeric characters, excluding the number `0` capital letter `O`, capital letter `I`, and lowercase letter `l`.

## Transaction

To link to an transaction, construct a URL like this:

{% code title="Mainnet" %}

```
https://xrpscan.com/tx/{TRANSACTION_HASH}
```

{% endcode %}

{% code title="Testnet" %}

```
https://testnet.xrpscan.com/tx/{TRANSACTION_HASH}
```

{% endcode %}

> [`https://xrpscan.com/tx/5A9E938DB7DA6193446A383898C7A66518E9FCE65DFFD82DF0B7E65844F3EB61`](https://xrpscan.com/tx/5A9E938DB7DA6193446A383898C7A66518E9FCE65DFFD82DF0B7E65844F3EB61)

`TRANSACTION_HASH` in the XRP Ledger is identified by a 64 characters long string. A transaction hash has the following properties:

* A string exactly 64 characters in length.
* Hex character set: `0-9` and `A-F`.
* Not case sensitive, but typically written in upper case letters.

In lieu of transaction hash, it is also possible to use Compact Transaction Identifier (`CTID`) to link to a transaction.

> [`https://xrpscan.com/tx/C2D1AC8600270000`](https://xrpscan.com/tx/C2D1AC8600270000)

## Token

To link to a Token issued on XRPL, construct a URL like this:

{% code title="Mainnet" %}

```
https://xrpscan.com/token/{TOKEN_CODE}.{TOKEN_ISSUER}
```

{% endcode %}

{% code title="Testnet" %}

```
https://testnet.xrpscan.com/token/{TOKEN_CODE}.{TOKEN_ISSUER}
```

{% endcode %}

> [`https://xrpscan.com/token/RLUSD.rMxCKbEDwqr76QuheSUMdEGf4B9xJ8m5De`](https://xrpscan.com/token/RLUSD.rMxCKbEDwqr76QuheSUMdEGf4B9xJ8m5De)

`TOKEN_ISSUER` is the r-Address of the account that issued the token. `TOKEN_CODE` is the Token code.  `TOKEN_CODE` can be any of the following:

* 3-character ISO 4217 currency code
* 3-character non standard currency code
* 160-bit (40-character) hexadecimal currency code
* 4-character to 40-character decoded currency code

## Ledger

To link to a Transaction, construct a URL like this:

{% code title="Mainnet" %}

```
https://xrpscan.com/ledger/{LEDGER_INDEX}
```

{% endcode %}

{% code title="Testnet" %}

```
https://testnet.xrpscan.com/ledger/{LEDGER_INDEX}
```

{% endcode %}

> [`https://xrpscan.com/ledger/81234567`](https://xrpscan.com/ledger/81234567)

`LEDGER_INDEX` in the XRP Ledger is identified by a 32 bit unsigned integer. string. A ledger index has the following properties:

* A number between `32,570` and `4,294,967,295`.
* Must be less than the last closed ledger index.

## NFT

To link to a NFT, construct a URL like this:

{% code title="Mainnet" %}

```
https://xrpscan.com/nft/{NFTOKEN_ID}
```

{% endcode %}

{% code title="Testnet" %}

```
https://testnet.xrpscan.com/nft/{NFTOKEN_ID}
```

{% endcode %}

> [`https://xrpscan.com/nft/000B00004B50699E253C5098DEFE3A0872A79D129172F4965B974D9E00000004`](https://xrpscan.com/nft/000B00004B50699E253C5098DEFE3A0872A79D129172F4965B974D9E00000004)

`NFTOKEN_ID` in the XRP Ledger is identified by a 64 characters long string. A NFToken ID has the following properties:

* A string exactly 64 characters in length.
* Hex character set: `0-9` and `A-F`.

## Validator

To link to a Validator, construct a URL like this:

{% code title="Mainnet" %}

```
https://xrpscan.com/validator/{VALIDATOR_PUBLIC_KEY}
```

{% endcode %}

{% code title="Testnet" %}

```
https://testnet.xrpscan.com/validator/{VALIDATOR_PUBLIC_KEY}
```

{% endcode %}

> [`https://xrpscan.com/validator/nHDB2PAPYqF86j9j3c6w1F1ZqwvQfiWcFShZ9Pokg9q4ohNDSkAz`](https://xrpscan.com/validator/nHDB2PAPYqF86j9j3c6w1F1ZqwvQfiWcFShZ9Pokg9q4ohNDSkAz)

`VALIDATOR_PUBLIC_KEY` in the XRP Ledger is identified by upto 53 characters long string in Base68 format. A Validator public key has the following properties:

* A string in Base58, upto 53 characters in length.
* Starts with the character `n`, commonly followed by `H`.
* Is case sensitive.
* Uses alphanumeric characters, excluding the number `0` capital letter `O`, capital letter `I`, and lowercase letter `l`.

## Amendment

To link to an Amendment, construct a URL like this:

{% code title="Mainnet" %}

```
https://xrpscan.com/amendment/{AMENDMENT_ID}
```

{% endcode %}

{% code title="Testnet" %}

```
https://testnet.xrpscan.com/amendment/{AMENDMENT_ID}
```

{% endcode %}

> [`https://xrpscan.com/amendment/30CD365592B8EE40489BA01AE2F7555CAC9C983145871DC82A42A31CF5BAE7D9`](https://xrpscan.com/amendment/30CD365592B8EE40489BA01AE2F7555CAC9C983145871DC82A42A31CF5BAE7D9)

`AMENDMENT_ID` in the XRP Ledger is identified by upto 64 charcters long string. An Amendment ID has the following properties:

* A string exactly 64 characters in length.
* Hex character set: `0-9` and `A-F`.
* Case sensitive.