Skip to main content

Build the Web Frontend

Once your contract is deployed it is highly likely that you will want to interact with it from a web frontend. To simplify this we have built NEAR JavaScript API. While the near-api-js actually allows you to do a multitude of things, here we will focus on how to use it to interact with a contract. Particularly, how to:

  1. Connect your frontend to the contract.
  2. Sign-in users in your app using the NEAR wallet.
  3. Call methods in the contract.

Adding NEAR API JSโ€‹

In order to use near-api-js you will need to first add it to your project.

npm i near-api-js

Connecting to a Contractโ€‹

The first step on using a smart contract from a web-frontend is connecting to it. Connecting to the smart contract is actually composed by 3 simple steps:

  1. Connecting to the NEAR network (testnet or mainnet)
  2. Initializing a Wallet, representing the user's wallet
  3. Initializing a Contract, representing the contract itself

In our examples we always do this within the initContract method:


Then, we use initContract in the web-app logic to set up a "flow", i.e. a simple if where we decide what to do if the user is logged in or not.


When initializing the Contract object in the snippet above we are passing a dictionary: nearConfig. In that dictionary we set: the network to which we want to connect (testnet in our snippet), and where to store the user's login information (we store the user's keys in the website's local storage).

Calling View Methodsโ€‹

Once we have setup the connection to the NEAR network and defined the Contract object we can readily call view methods. View methods are those that perform read-only operations, and do not change the contract's state.

Because of their read-only nature, view methods are free to call, and do not require the user to be logged in.


The snippet above if part of our donation example. On it, we are calling total_donations and get_donation_list to retrieve the last 10 recorded donations. These methods only read from the contract, so they can be used readily without the user needing to log in.

User Sign-inโ€‹

In order to interact with non-view methods it is necessary to first sign in using a NEAR wallet. Signing in is as simple as requesting the walletConnection object to for signing in. Once we want to logout the user, we simply need to request the walletConnection to sign out.


Signing in actually means that the user's wallet creates and stores an access key in the web's local storage. By default, such key enables to expend a maximum of 0.25โ“ƒ on GAS for calling our contract without asking the user to sign them. However, if you attach money to any call, the user will be redirected to the wallet to confirm the transaction.


You can use walletConnection.account().function_call to call any method in any contract. However, the user will be redirected to the wallet and asked to accept the call.

Calling Change Methodsโ€‹

Only after the user logs-in they can start calling change methods. Programmatically, calling change methods is similar to calling view methods, only that now you can attach money to the call, and specify how much GAS you want to use. It is important to notice that, if you ask for money to be attached in the call, then the user will be redirected to the NEAR wallet to accept the transaction.


Remember that you can use walletConnection.account().function_call to call methods in any contract. However, the user will be redirected to the wallet and asked to accept the call.

Wallet Redirectionโ€‹

If you attach money to a change call, then the user will be redirected to their wallet to accept the transaction. After accepting, the user will be brought back to your website, with the resulting transaction hash being pass as part of the url (i.e.

If the method invoked returned a result, you can use the transaction hash to retrieve the result from the network. Assuming you created the near object as in the example above, then you query the result by doing:


Handling Data Typesโ€‹

When calling methods in a contract, or receiving results from them, you will need to correctly encode/decode parameters. For this, it is important to know how the contracts encode timestamps (u64) and money amounts (u128).


The block timestamp in a smart contract is encoded using nanoseconds (i.e. 19 digits: 1655373910837593990). In contrast, from javascript returns a timestamp in milliseconds (i.e 13 digits: 1655373910837). Make sure to convert between milliseconds and nanoseconds to properly handle time variables.


Smart contracts speak in yocto NEAR, where 1โ“ƒ = 10^24yocto, and the values are always encoded as strings.

  • Convert from NEAR to yocto before sending it to the contract using near-api-js.utils.format.parseNearAmount(amount.toString()).
  • Convert a response in yoctoNEAR to NEAR using near-api-js.utils.format.formatNearAmount(amount)

If the contract returns a Balance instead of a U128, you will get a "scientific notation" number instead of a string (e.g. 10^6 instead of "1000000"). In this case, you can convert the value to NEAR by doing:

function formatAmount(amount) {
let formatted = amount.toLocaleString('fullwide', { useGrouping: false })
formatted = utils.format.formatNearAmount(formatted)
return Math.floor(formatted * 100) / 100

Leveraging NEAR API JSโ€‹

NEAR API JS does not limit itself to simply calling methods in a contract. In fact, you can use it to transform your web-app into a rich user experience. While we will not cover these topics in depth, it is important for you to know that with NEAR API JS you can also:

Check the cookbook to learn how to supercharge your webapp.