Skip to main content

Kaia to Nodit Migration Guide


KAS (Klaytn API Service) is an API service provided by the Klaytn Foundation to support easy and fast Klaytn DApp development. Even after the rebranding and hard fork to Kaia, KAS features still operate on Kaia, but the API specs and documentation are still based on Klaytn.

Do you have development experience using KAS? Compare Nodit's APIs with KAS APIs through the table below, and check the guide on how to replace the APIs you are using with Nodit APIs.

Comparison of Features Supported by KAS and Nodit

Below is a comparison table that allows you to see at a glance the APIs provided by KAS and the corresponding Nodit APIs. KAS APIs are based on the KAS Reference page. For detailed descriptions of each feature, please refer to the notes below the table.

KAS API CategoryKAS API NameCompatibilityNodit Compatibility NotesDescription
Klaytn Node APIAll Node APIsNode API-
Contract APIQuery all FT contract dataNot supported-
Query list of all NFT contract dataNot supported-
Query list of all NFT contract dataNot supported-
Query list of MT contract dataNot supported-
Get data of a certain FT contractFully supportedGet Token Contract Metadata by Contracts API
Get data of certain NFT contractsFully supportedGet NFT Contract Metadata by Contracts
Get data of certain MT contractsFully supportedGet NFT Contract Metadata by Contracts
Get the number of NFT ownersFully supportedQuery using the Get NFT Holders by Contract API with count=true
Get the number of MT ownersFully supportedQuery using the Get NFT Holders by Contract API with count=true
Update metadata of a certain FT contractNot supported
Update metadata of a certain NFT contractNot supported-
Token APIQuery all token data for certain NFT contractsFully supportedGet NFT Metadata by Contract
Get token data for NFT data by EOAFully supportedGet NFTs Owned By Account
Query token data for certain NFTsFully supportedMost Metadata fields can be queried equivalently via the Get NFT Metadata by Token IDs API, but owner information for the token must be queried separately via the Get NFT Holders by Token ID API.
Query information of all tokens for certain MTsFully supportedGet NFT Metadata by Contract
* This is the ERC1155 case under the Ethereum standard; in Nodit it is included under the NFT category.
Get data of MT contracts for certain EOAsFully supportedGet NFTs Owned By Account
* This is the ERC1155 case under the Ethereum standard; in Nodit it is included under the NFT category.
Get token data for MT data by EOAFully supportedMost Metadata fields can be queried equivalently via the Get NFT Metadata by Token IDs API, but owner information for the token must be queried separately via the Get NFT Holders by Token ID API.
* This is the ERC1155 case under the Ethereum standard; in Nodit it is included under the NFT category.
Get contract data by EOAPartially supportedNodit supports separate queries for FT contracts and NFT contracts. To compose an equivalent response, you can call the Get Tokens Owned By Account API and Get NFTs Owned By Account API individually, then combine the returned contract information.
Get data of certain tokens for certain EOAsPartially supportedNodit supports separate queries for FT and NFT. To compose an equivalent response, you can call the Get Tokens Owned By Account API and Get NFTs Owned By Account API individually, then combine the returned token information.
Update metadata of a certain NFT TokenNot supported-
Update metadata of a certain MT TokenNot supported-
Token Ownership APIQuery list of all owners for certain MTsFully supportedGet NFT Transfers By TokenId
* This is the ERC1155 case under the Ethereum standard; in Nodit it is included under the NFT category.
Query ownership change history for certain NFTsFully supportedGet NFT Transfers By TokenId
Token Ownership APIQuery received and sent transfers of tokens with transaction hashNot supportedA separate Transaction query API for querying only asset transfers is not provided. You can query general information about a transaction via the Get Transaction By Hash API, and it is possible to implement secondary queries using the contract information included in the response.
Query received and sent transfers of tokensPartially supportedThe ability to query by specifying an asset type in a single API is not provided. You can obtain a similar response by using the Get Token Transfers by Account API for FT and the Get NFT Transfers By Account API for NFT respectively.
Wallet APIAllNot supportedKAS's Wallet API is a feature that manages accounts on behalf of users. Nodit, which provides APIs for multiple public chains, does not separately offer this feature for security reasons. It is recommended to generate and manage keys directly using a wallet application or account creation functions.
KIP-7 API (FT)AllNot supportedNodit does not provide a separate service layer for contract deployment or management on behalf of users. It is recommended to refer to the contract direct deployment method using development tools to deploy a standard token contract written by the user to the network, then call that contract to mint or manage tokens.
KIP-17 API (NFT)AllNot supportedNodit does not provide a separate service layer for contract deployment or management on behalf of users. It is recommended to refer to the contract direct deployment method using development tools to deploy a standard token contract written by the user to the network, then call that contract to mint or manage tokens.
KIP-37 API (NFT 1155)AllNot supportedNodit does not provide a separate service layer for contract deployment or management on behalf of users. It is recommended to refer to the contract direct deployment method using development tools to deploy a standard token contract written by the user to the network, then call that contract to mint or manage tokens.
Metadata APIAllNot supportedNodit does not provide a separate service layer for contract deployment or management on behalf of users. It is recommended to refer to the contract direct deployment method using development tools to deploy a standard token contract written by the user to the network, then call that contract to mint or manage tokens.

How are KAS Node API and Nodit Node API different?

Both APIs provide the same functionality. Both APIs aim to allow users to use the interfaces natively provided by a node client without running a node themselves, and the node client interfaces provided by the proxied nodes are identical. With Nodit's Kaia Node API, you can use all of the eth, net, web3, debug, kaia, klay, and subscription namespaces. Try integrating Kaia Node API using Nodit's robust nodes with 99.9% uptime.

How do I use Nodit Node API?

Refer to the Nodit Quickstart page to find the Kaia node endpoint in the Nodit console. You can use that endpoint to call the Node API. Simple test calls can be executed directly from the subpages under Kaia.

Yes, all Kaia-related features including Node API and Web3 Data API are available for free. However, the free plan has restrictions on the number of API calls and usage. Please refer to the Pricing page for details on usage per plan.

Nodit provides a common development environment across multiple public chain environments. Therefore, it does not provide a separate service layer for managing contracts or minting histories for issuing accounts or assets, and recommends managing account creation or contract management directly at the application level to ensure there are no security risks. If you are new to blockchain and find direct development difficult, go to the Tutorial tab to check out the various tutorials and learning content for beginners provided by Nodit.

I want to develop a high-performance application leveraging Kaia's high usage. Can I use a dedicated node?

Nodit supports Kaia Dedicated nodes. You can use a high-performance node environment in an isolated dedicated environment. For details on Dedicated nodes, please refer to the Elastic Node page.