Anchor API

Introduction This document describes KAS (Klaytn API Service) Anchor API. Anchor API provides features sending metadata available to verify data reliability to ensure the reliability of service chain data to Klaytn main chain. For more details on using the Anchor API, please refer to Tutorial. # Error Codes ## 400: Bad Request | Code | Messages | | --- | --- | | 1071010 | data don't exist 1071615 | its value is out of range; size 1072100 | same payload ID or payload was already anchored 1072101 | all configured accounts have insufficient funds |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Anchor API

Introduction This document describes KAS (Klaytn API Service) Anchor API. Anchor API provides features sending metadata available to verify data reliability to ensure the reliability of service chain data to Klaytn main chain. For more details on using the Anchor API, please refer to Tutorial. # Error Codes ## 400: Bad Request | Code | Messages | | --- | --- | | 1071010 | data don't exist 1071615 | its value is out of range; size 1072100 | same payload ID or payload was already anchored 1072101 | all configured accounts have insufficient funds |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Anchor API

Introduction This document describes KAS (Klaytn API Service) Anchor API. Anchor API provides features sending metadata available to verify data reliability to ensure the reliability of service chain data to Klaytn main chain. For more details on using the Anchor API, please refer to Tutorial. # Error Codes ## 400: Bad Request | Code | Messages | | --- | --- | | 1071010 | data don't exist 1071615 | its value is out of range; size 1072100 | same payload ID or payload was already anchored 1072101 | all configured accounts have insufficient funds |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Anchor API

Introduction This document describes KAS (Klaytn API Service) Anchor API. Anchor API provides features sending metadata available to verify data reliability to ensure the reliability of service chain data to Klaytn main chain. For more details on using the Anchor API, please refer to Tutorial. # Error Codes ## 400: Bad Request | Code | Messages | | --- | --- | | 1071010 | data don't exist 1071615 | its value is out of range; size 1072100 | same payload ID or payload was already anchored 1072101 | all configured accounts have insufficient funds |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Anchor API

Introduction This document describes KAS (Klaytn API Service) Anchor API. Anchor API provides features sending metadata available to verify data reliability to ensure the reliability of service chain data to Klaytn main chain. For more details on using the Anchor API, please refer to Tutorial. # Error Codes ## 400: Bad Request | Code | Messages | | --- | --- | | 1071010 | data don't exist 1071615 | its value is out of range; size 1072100 | same payload ID or payload was already anchored 1072101 | all configured accounts have insufficient funds |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Anchor API

Introduction This document describes KAS (Klaytn API Service) Anchor API. Anchor API provides features sending metadata available to verify data reliability to ensure the reliability of service chain data to Klaytn main chain. For more details on using the Anchor API, please refer to Tutorial. # Error Codes ## 400: Bad Request | Code | Messages | | --- | --- | | 1071010 | data don't exist 1071615 | its value is out of range; size 1072100 | same payload ID or payload was already anchored 1072101 | all configured accounts have insufficient funds |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Anchor API

Introduction This document describes KAS (Klaytn API Service) Anchor API. Anchor API provides features sending metadata available to verify data reliability to ensure the reliability of service chain data to Klaytn main chain. For more details on using the Anchor API, please refer to Tutorial. # Error Codes ## 400: Bad Request | Code | Messages | | --- | --- | | 1071010 | data don't exist 1071615 | its value is out of range; size 1072100 | same payload ID or payload was already anchored 1072101 | all configured accounts have insufficient funds |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Anchor API

Introduction This document describes KAS (Klaytn API Service) Anchor API. Anchor API provides features sending metadata available to verify data reliability to ensure the reliability of service chain data to Klaytn main chain. For more details on using the Anchor API, please refer to Tutorial. # Error Codes ## 400: Bad Request | Code | Messages | | --- | --- | | 1071010 | data don't exist 1071615 | its value is out of range; size 1072100 | same payload ID or payload was already anchored 1072101 | all configured accounts have insufficient funds |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Anchor API

Introduction This document describes KAS (Klaytn API Service) Anchor API. Anchor API provides features sending metadata available to verify data reliability to ensure the reliability of service chain data to Klaytn main chain. For more details on using the Anchor API, please refer to Tutorial. # Error Codes ## 400: Bad Request | Code | Messages | | --- | --- | | 1071010 | data don't exist 1071615 | its value is out of range; size 1072100 | same payload ID or payload was already anchored 1072101 | all configured accounts have insufficient funds |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Anchor API

Introduction This document describes KAS (Klaytn API Service) Anchor API. Anchor API provides features sending metadata available to verify data reliability to ensure the reliability of service chain data to Klaytn main chain. For more details on using the Anchor API, please refer to Tutorial. # Error Codes ## 400: Bad Request | Code | Messages | | --- | --- | | 1071010 | data don't exist 1071615 | its value is out of range; size 1072100 | same payload ID or payload was already anchored 1072101 | all configured accounts have insufficient funds |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Anchor API

Introduction This document describes KAS (Klaytn API Service) Anchor API. Anchor API provides features sending metadata available to verify data reliability to ensure the reliability of service chain data to Klaytn main chain. For more details on using the Anchor API, please refer to Tutorial. # Error Codes ## 400: Bad Request | Code | Messages | | --- | --- | | 1071010 | data don't exist 1071615 | its value is out of range; size 1072100 | same payload ID or payload was already anchored 1072101 | all configured accounts have insufficient funds |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Anchor API

Introduction This document describes KAS (Klaytn API Service) Anchor API. Anchor API provides features sending metadata available to verify data reliability to ensure the reliability of service chain data to Klaytn main chain. For more details on using the Anchor API, please refer to Tutorial. # Error Codes ## 400: Bad Request | Code | Messages | | --- | --- | | 1071010 | data don't exist 1071615 | its value is out of range; size 1072100 | same payload ID or payload was already anchored 1072101 | all configured accounts have insufficient funds |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Anchor API

Introduction This document describes KAS (Klaytn API Service) Anchor API. Anchor API provides features sending metadata available to verify data reliability to ensure the reliability of service chain data to Klaytn main chain. For more details on using the Anchor API, please refer to Tutorial. # Error Codes ## 400: Bad Request | Code | Messages | | --- | --- | | 1071010 | data don't exist 1071615 | its value is out of range; size 1072100 | same payload ID or payload was already anchored 1072101 | all configured accounts have insufficient funds |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Anchor API

Introduction This document describes KAS (Klaytn API Service) Anchor API. Anchor API provides features sending metadata available to verify data reliability to ensure the reliability of service chain data to Klaytn main chain. For more details on using the Anchor API, please refer to Tutorial. # Error Codes ## 400: Bad Request | Code | Messages | | --- | --- | | 1071010 | data don't exist 1071615 | its value is out of range; size 1072100 | same payload ID or payload was already anchored 1072101 | all configured accounts have insufficient funds |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-17 API

Introduction The KIP-17 API helps BApp (Blockchain Application) developers to manage contracts and tokens created in accordance with the KIP-17 standard, which is Klaytn's technical speficication for Non-Fungible Tokens. The functionality of the multiple endpoints enables you to do the following actions: - deploy smart contracts - manage the entire life cycle of an NFT from minting, to sending and burning - get contract or token data - authorize a third party to execute token transfers - view token ownership history For more details on KAS, please refer to KAS Docs. If you have any questions or comments, please leave them in the Klaytn Developers Forum. alias When a method of the KIP-17 API requires a contract address, you can use the contract alias. You can give the contract an alias when deploying, and use it in place of the complicated address. # Fee Payer Options KAS KIP-17 supports four ways to pay the transaction fees.
1. Only using KAS Global FeePayer Account
Sends all transactions using KAS Global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer Account
Sends all transactions using User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account
Sends transactions using User FeePayer Account by default, and switches to the KAS Global FeePayer Account when balances are insufficient. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account
Sends transactions the default way, paying the transaction fee from the user's account. { \"options\": { \"enableGlobalFeePayer\": false } }
# Error Code This section contains the errors that might occur when using the KIP-17 API. KAS uses HTTP status codes. More details can be found in this link.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-17 API

Introduction The KIP-17 API helps BApp (Blockchain Application) developers to manage contracts and tokens created in accordance with the KIP-17 standard, which is Klaytn's technical speficication for Non-Fungible Tokens. The functionality of the multiple endpoints enables you to do the following actions: - deploy smart contracts - manage the entire life cycle of an NFT from minting, to sending and burning - get contract or token data - authorize a third party to execute token transfers - view token ownership history For more details on KAS, please refer to KAS Docs. If you have any questions or comments, please leave them in the Klaytn Developers Forum. alias When a method of the KIP-17 API requires a contract address, you can use the contract alias. You can give the contract an alias when deploying, and use it in place of the complicated address. # Fee Payer Options KAS KIP-17 supports four ways to pay the transaction fees.
1. Only using KAS Global FeePayer Account
Sends all transactions using KAS Global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer Account
Sends all transactions using User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account
Sends transactions using User FeePayer Account by default, and switches to the KAS Global FeePayer Account when balances are insufficient. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account
Sends transactions the default way, paying the transaction fee from the user's account. { \"options\": { \"enableGlobalFeePayer\": false } }
# Error Code This section contains the errors that might occur when using the KIP-17 API. KAS uses HTTP status codes. More details can be found in this link.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-17 API

Introduction The KIP-17 API helps BApp (Blockchain Application) developers to manage contracts and tokens created in accordance with the KIP-17 standard, which is Klaytn's technical speficication for Non-Fungible Tokens. The functionality of the multiple endpoints enables you to do the following actions: - deploy smart contracts - manage the entire life cycle of an NFT from minting, to sending and burning - get contract or token data - authorize a third party to execute token transfers - view token ownership history For more details on KAS, please refer to KAS Docs. If you have any questions or comments, please leave them in the Klaytn Developers Forum. alias When a method of the KIP-17 API requires a contract address, you can use the contract alias. You can give the contract an alias when deploying, and use it in place of the complicated address. # Fee Payer Options KAS KIP-17 supports four ways to pay the transaction fees.
1. Only using KAS Global FeePayer Account
Sends all transactions using KAS Global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer Account
Sends all transactions using User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account
Sends transactions using User FeePayer Account by default, and switches to the KAS Global FeePayer Account when balances are insufficient. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account
Sends transactions the default way, paying the transaction fee from the user's account. { \"options\": { \"enableGlobalFeePayer\": false } }
# Error Code This section contains the errors that might occur when using the KIP-17 API. KAS uses HTTP status codes. More details can be found in this link.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-17 API

Introduction The KIP-17 API helps BApp (Blockchain Application) developers to manage contracts and tokens created in accordance with the KIP-17 standard, which is Klaytn's technical speficication for Non-Fungible Tokens. The functionality of the multiple endpoints enables you to do the following actions: - deploy smart contracts - manage the entire life cycle of an NFT from minting, to sending and burning - get contract or token data - authorize a third party to execute token transfers - view token ownership history For more details on KAS, please refer to KAS Docs. If you have any questions or comments, please leave them in the Klaytn Developers Forum. alias When a method of the KIP-17 API requires a contract address, you can use the contract alias. You can give the contract an alias when deploying, and use it in place of the complicated address. # Fee Payer Options KAS KIP-17 supports four ways to pay the transaction fees.
1. Only using KAS Global FeePayer Account
Sends all transactions using KAS Global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer Account
Sends all transactions using User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account
Sends transactions using User FeePayer Account by default, and switches to the KAS Global FeePayer Account when balances are insufficient. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account
Sends transactions the default way, paying the transaction fee from the user's account. { \"options\": { \"enableGlobalFeePayer\": false } }
# Error Code This section contains the errors that might occur when using the KIP-17 API. KAS uses HTTP status codes. More details can be found in this link.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-17 API

Introduction The KIP-17 API helps BApp (Blockchain Application) developers to manage contracts and tokens created in accordance with the KIP-17 standard, which is Klaytn's technical speficication for Non-Fungible Tokens. The functionality of the multiple endpoints enables you to do the following actions: - deploy smart contracts - manage the entire life cycle of an NFT from minting, to sending and burning - get contract or token data - authorize a third party to execute token transfers - view token ownership history For more details on KAS, please refer to KAS Docs. If you have any questions or comments, please leave them in the Klaytn Developers Forum. alias When a method of the KIP-17 API requires a contract address, you can use the contract alias. You can give the contract an alias when deploying, and use it in place of the complicated address. # Fee Payer Options KAS KIP-17 supports four ways to pay the transaction fees.
1. Only using KAS Global FeePayer Account
Sends all transactions using KAS Global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer Account
Sends all transactions using User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account
Sends transactions using User FeePayer Account by default, and switches to the KAS Global FeePayer Account when balances are insufficient. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account
Sends transactions the default way, paying the transaction fee from the user's account. { \"options\": { \"enableGlobalFeePayer\": false } }
# Error Code This section contains the errors that might occur when using the KIP-17 API. KAS uses HTTP status codes. More details can be found in this link.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-17 API

Introduction The KIP-17 API helps BApp (Blockchain Application) developers to manage contracts and tokens created in accordance with the KIP-17 standard, which is Klaytn's technical speficication for Non-Fungible Tokens. The functionality of the multiple endpoints enables you to do the following actions: - deploy smart contracts - manage the entire life cycle of an NFT from minting, to sending and burning - get contract or token data - authorize a third party to execute token transfers - view token ownership history For more details on KAS, please refer to KAS Docs. If you have any questions or comments, please leave them in the Klaytn Developers Forum. alias When a method of the KIP-17 API requires a contract address, you can use the contract alias. You can give the contract an alias when deploying, and use it in place of the complicated address. # Fee Payer Options KAS KIP-17 supports four ways to pay the transaction fees.
1. Only using KAS Global FeePayer Account
Sends all transactions using KAS Global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer Account
Sends all transactions using User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account
Sends transactions using User FeePayer Account by default, and switches to the KAS Global FeePayer Account when balances are insufficient. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account
Sends transactions the default way, paying the transaction fee from the user's account. { \"options\": { \"enableGlobalFeePayer\": false } }
# Error Code This section contains the errors that might occur when using the KIP-17 API. KAS uses HTTP status codes. More details can be found in this link.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-17 API

Introduction The KIP-17 API helps BApp (Blockchain Application) developers to manage contracts and tokens created in accordance with the KIP-17 standard, which is Klaytn's technical speficication for Non-Fungible Tokens. The functionality of the multiple endpoints enables you to do the following actions: - deploy smart contracts - manage the entire life cycle of an NFT from minting, to sending and burning - get contract or token data - authorize a third party to execute token transfers - view token ownership history For more details on KAS, please refer to KAS Docs. If you have any questions or comments, please leave them in the Klaytn Developers Forum. alias When a method of the KIP-17 API requires a contract address, you can use the contract alias. You can give the contract an alias when deploying, and use it in place of the complicated address. # Fee Payer Options KAS KIP-17 supports four ways to pay the transaction fees.
1. Only using KAS Global FeePayer Account
Sends all transactions using KAS Global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer Account
Sends all transactions using User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account
Sends transactions using User FeePayer Account by default, and switches to the KAS Global FeePayer Account when balances are insufficient. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account
Sends transactions the default way, paying the transaction fee from the user's account. { \"options\": { \"enableGlobalFeePayer\": false } }
# Error Code This section contains the errors that might occur when using the KIP-17 API. KAS uses HTTP status codes. More details can be found in this link.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-17 API

Introduction The KIP-17 API helps BApp (Blockchain Application) developers to manage contracts and tokens created in accordance with the KIP-17 standard, which is Klaytn's technical speficication for Non-Fungible Tokens. The functionality of the multiple endpoints enables you to do the following actions: - deploy smart contracts - manage the entire life cycle of an NFT from minting, to sending and burning - get contract or token data - authorize a third party to execute token transfers - view token ownership history For more details on KAS, please refer to KAS Docs. If you have any questions or comments, please leave them in the Klaytn Developers Forum. alias When a method of the KIP-17 API requires a contract address, you can use the contract alias. You can give the contract an alias when deploying, and use it in place of the complicated address. # Fee Payer Options KAS KIP-17 supports four ways to pay the transaction fees.
1. Only using KAS Global FeePayer Account
Sends all transactions using KAS Global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer Account
Sends all transactions using User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account
Sends transactions using User FeePayer Account by default, and switches to the KAS Global FeePayer Account when balances are insufficient. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account
Sends transactions the default way, paying the transaction fee from the user's account. { \"options\": { \"enableGlobalFeePayer\": false } }
# Error Code This section contains the errors that might occur when using the KIP-17 API. KAS uses HTTP status codes. More details can be found in this link.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-17 API

Introduction The KIP-17 API helps BApp (Blockchain Application) developers to manage contracts and tokens created in accordance with the KIP-17 standard, which is Klaytn's technical speficication for Non-Fungible Tokens. The functionality of the multiple endpoints enables you to do the following actions: - deploy smart contracts - manage the entire life cycle of an NFT from minting, to sending and burning - get contract or token data - authorize a third party to execute token transfers - view token ownership history For more details on KAS, please refer to KAS Docs. If you have any questions or comments, please leave them in the Klaytn Developers Forum. alias When a method of the KIP-17 API requires a contract address, you can use the contract alias. You can give the contract an alias when deploying, and use it in place of the complicated address. # Fee Payer Options KAS KIP-17 supports four ways to pay the transaction fees.
1. Only using KAS Global FeePayer Account
Sends all transactions using KAS Global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer Account
Sends all transactions using User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account
Sends transactions using User FeePayer Account by default, and switches to the KAS Global FeePayer Account when balances are insufficient. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account
Sends transactions the default way, paying the transaction fee from the user's account. { \"options\": { \"enableGlobalFeePayer\": false } }
# Error Code This section contains the errors that might occur when using the KIP-17 API. KAS uses HTTP status codes. More details can be found in this link.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-17 API

Introduction The KIP-17 API helps BApp (Blockchain Application) developers to manage contracts and tokens created in accordance with the KIP-17 standard, which is Klaytn's technical speficication for Non-Fungible Tokens. The functionality of the multiple endpoints enables you to do the following actions: - deploy smart contracts - manage the entire life cycle of an NFT from minting, to sending and burning - get contract or token data - authorize a third party to execute token transfers - view token ownership history For more details on KAS, please refer to KAS Docs. If you have any questions or comments, please leave them in the Klaytn Developers Forum. alias When a method of the KIP-17 API requires a contract address, you can use the contract alias. You can give the contract an alias when deploying, and use it in place of the complicated address. # Fee Payer Options KAS KIP-17 supports four ways to pay the transaction fees.
1. Only using KAS Global FeePayer Account
Sends all transactions using KAS Global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer Account
Sends all transactions using User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account
Sends transactions using User FeePayer Account by default, and switches to the KAS Global FeePayer Account when balances are insufficient. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account
Sends transactions the default way, paying the transaction fee from the user's account. { \"options\": { \"enableGlobalFeePayer\": false } }
# Error Code This section contains the errors that might occur when using the KIP-17 API. KAS uses HTTP status codes. More details can be found in this link.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-17 API

Introduction The KIP-17 API helps BApp (Blockchain Application) developers to manage contracts and tokens created in accordance with the KIP-17 standard, which is Klaytn's technical speficication for Non-Fungible Tokens. The functionality of the multiple endpoints enables you to do the following actions: - deploy smart contracts - manage the entire life cycle of an NFT from minting, to sending and burning - get contract or token data - authorize a third party to execute token transfers - view token ownership history For more details on KAS, please refer to KAS Docs. If you have any questions or comments, please leave them in the Klaytn Developers Forum. alias When a method of the KIP-17 API requires a contract address, you can use the contract alias. You can give the contract an alias when deploying, and use it in place of the complicated address. # Fee Payer Options KAS KIP-17 supports four ways to pay the transaction fees.
1. Only using KAS Global FeePayer Account
Sends all transactions using KAS Global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer Account
Sends all transactions using User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account
Sends transactions using User FeePayer Account by default, and switches to the KAS Global FeePayer Account when balances are insufficient. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account
Sends transactions the default way, paying the transaction fee from the user's account. { \"options\": { \"enableGlobalFeePayer\": false } }
# Error Code This section contains the errors that might occur when using the KIP-17 API. KAS uses HTTP status codes. More details can be found in this link.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-17 API

Introduction The KIP-17 API helps BApp (Blockchain Application) developers to manage contracts and tokens created in accordance with the KIP-17 standard, which is Klaytn's technical speficication for Non-Fungible Tokens. The functionality of the multiple endpoints enables you to do the following actions: - deploy smart contracts - manage the entire life cycle of an NFT from minting, to sending and burning - get contract or token data - authorize a third party to execute token transfers - view token ownership history For more details on KAS, please refer to KAS Docs. If you have any questions or comments, please leave them in the Klaytn Developers Forum. alias When a method of the KIP-17 API requires a contract address, you can use the contract alias. You can give the contract an alias when deploying, and use it in place of the complicated address. # Fee Payer Options KAS KIP-17 supports four ways to pay the transaction fees.
1. Only using KAS Global FeePayer Account
Sends all transactions using KAS Global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer Account
Sends all transactions using User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account
Sends transactions using User FeePayer Account by default, and switches to the KAS Global FeePayer Account when balances are insufficient. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account
Sends transactions the default way, paying the transaction fee from the user's account. { \"options\": { \"enableGlobalFeePayer\": false } }
# Error Code This section contains the errors that might occur when using the KIP-17 API. KAS uses HTTP status codes. More details can be found in this link.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-17 API

Introduction The KIP-17 API helps BApp (Blockchain Application) developers to manage contracts and tokens created in accordance with the KIP-17 standard, which is Klaytn's technical speficication for Non-Fungible Tokens. The functionality of the multiple endpoints enables you to do the following actions: - deploy smart contracts - manage the entire life cycle of an NFT from minting, to sending and burning - get contract or token data - authorize a third party to execute token transfers - view token ownership history For more details on KAS, please refer to KAS Docs. If you have any questions or comments, please leave them in the Klaytn Developers Forum. alias When a method of the KIP-17 API requires a contract address, you can use the contract alias. You can give the contract an alias when deploying, and use it in place of the complicated address. # Fee Payer Options KAS KIP-17 supports four ways to pay the transaction fees.
1. Only using KAS Global FeePayer Account
Sends all transactions using KAS Global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer Account
Sends all transactions using User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account
Sends transactions using User FeePayer Account by default, and switches to the KAS Global FeePayer Account when balances are insufficient. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account
Sends transactions the default way, paying the transaction fee from the user's account. { \"options\": { \"enableGlobalFeePayer\": false } }
# Error Code This section contains the errors that might occur when using the KIP-17 API. KAS uses HTTP status codes. More details can be found in this link.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-17 API

Introduction The KIP-17 API helps BApp (Blockchain Application) developers to manage contracts and tokens created in accordance with the KIP-17 standard, which is Klaytn's technical speficication for Non-Fungible Tokens. The functionality of the multiple endpoints enables you to do the following actions: - deploy smart contracts - manage the entire life cycle of an NFT from minting, to sending and burning - get contract or token data - authorize a third party to execute token transfers - view token ownership history For more details on KAS, please refer to KAS Docs. If you have any questions or comments, please leave them in the Klaytn Developers Forum. alias When a method of the KIP-17 API requires a contract address, you can use the contract alias. You can give the contract an alias when deploying, and use it in place of the complicated address. # Fee Payer Options KAS KIP-17 supports four ways to pay the transaction fees.
1. Only using KAS Global FeePayer Account
Sends all transactions using KAS Global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer Account
Sends all transactions using User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account
Sends transactions using User FeePayer Account by default, and switches to the KAS Global FeePayer Account when balances are insufficient. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account
Sends transactions the default way, paying the transaction fee from the user's account. { \"options\": { \"enableGlobalFeePayer\": false } }
# Error Code This section contains the errors that might occur when using the KIP-17 API. KAS uses HTTP status codes. More details can be found in this link.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-17 API

Introduction The KIP-17 API helps BApp (Blockchain Application) developers to manage contracts and tokens created in accordance with the KIP-17 standard, which is Klaytn's technical speficication for Non-Fungible Tokens. The functionality of the multiple endpoints enables you to do the following actions: - deploy smart contracts - manage the entire life cycle of an NFT from minting, to sending and burning - get contract or token data - authorize a third party to execute token transfers - view token ownership history For more details on KAS, please refer to KAS Docs. If you have any questions or comments, please leave them in the Klaytn Developers Forum. alias When a method of the KIP-17 API requires a contract address, you can use the contract alias. You can give the contract an alias when deploying, and use it in place of the complicated address. # Fee Payer Options KAS KIP-17 supports four ways to pay the transaction fees.
1. Only using KAS Global FeePayer Account
Sends all transactions using KAS Global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer Account
Sends all transactions using User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account
Sends transactions using User FeePayer Account by default, and switches to the KAS Global FeePayer Account when balances are insufficient. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account
Sends transactions the default way, paying the transaction fee from the user's account. { \"options\": { \"enableGlobalFeePayer\": false } }
# Error Code This section contains the errors that might occur when using the KIP-17 API. KAS uses HTTP status codes. More details can be found in this link.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-17 API

Introduction The KIP-17 API helps BApp (Blockchain Application) developers to manage contracts and tokens created in accordance with the KIP-17 standard, which is Klaytn's technical speficication for Non-Fungible Tokens. The functionality of the multiple endpoints enables you to do the following actions: - deploy smart contracts - manage the entire life cycle of an NFT from minting, to sending and burning - get contract or token data - authorize a third party to execute token transfers - view token ownership history For more details on KAS, please refer to KAS Docs. If you have any questions or comments, please leave them in the Klaytn Developers Forum. alias When a method of the KIP-17 API requires a contract address, you can use the contract alias. You can give the contract an alias when deploying, and use it in place of the complicated address. # Fee Payer Options KAS KIP-17 supports four ways to pay the transaction fees.
1. Only using KAS Global FeePayer Account
Sends all transactions using KAS Global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer Account
Sends all transactions using User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account
Sends transactions using User FeePayer Account by default, and switches to the KAS Global FeePayer Account when balances are insufficient. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account
Sends transactions the default way, paying the transaction fee from the user's account. { \"options\": { \"enableGlobalFeePayer\": false } }
# Error Code This section contains the errors that might occur when using the KIP-17 API. KAS uses HTTP status codes. More details can be found in this link.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-17 API

Introduction The KIP-17 API helps BApp (Blockchain Application) developers to manage contracts and tokens created in accordance with the KIP-17 standard, which is Klaytn's technical speficication for Non-Fungible Tokens. The functionality of the multiple endpoints enables you to do the following actions: - deploy smart contracts - manage the entire life cycle of an NFT from minting, to sending and burning - get contract or token data - authorize a third party to execute token transfers - view token ownership history For more details on KAS, please refer to KAS Docs. If you have any questions or comments, please leave them in the Klaytn Developers Forum. alias When a method of the KIP-17 API requires a contract address, you can use the contract alias. You can give the contract an alias when deploying, and use it in place of the complicated address. # Fee Payer Options KAS KIP-17 supports four ways to pay the transaction fees.
1. Only using KAS Global FeePayer Account
Sends all transactions using KAS Global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer Account
Sends all transactions using User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account
Sends transactions using User FeePayer Account by default, and switches to the KAS Global FeePayer Account when balances are insufficient. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account
Sends transactions the default way, paying the transaction fee from the user's account. { \"options\": { \"enableGlobalFeePayer\": false } }
# Error Code This section contains the errors that might occur when using the KIP-17 API. KAS uses HTTP status codes. More details can be found in this link.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-17 API

Introduction The KIP-17 API helps BApp (Blockchain Application) developers to manage contracts and tokens created in accordance with the KIP-17 standard, which is Klaytn's technical speficication for Non-Fungible Tokens. The functionality of the multiple endpoints enables you to do the following actions: - deploy smart contracts - manage the entire life cycle of an NFT from minting, to sending and burning - get contract or token data - authorize a third party to execute token transfers - view token ownership history For more details on KAS, please refer to KAS Docs. If you have any questions or comments, please leave them in the Klaytn Developers Forum. alias When a method of the KIP-17 API requires a contract address, you can use the contract alias. You can give the contract an alias when deploying, and use it in place of the complicated address. # Fee Payer Options KAS KIP-17 supports four ways to pay the transaction fees.
1. Only using KAS Global FeePayer Account
Sends all transactions using KAS Global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer Account
Sends all transactions using User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account
Sends transactions using User FeePayer Account by default, and switches to the KAS Global FeePayer Account when balances are insufficient. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account
Sends transactions the default way, paying the transaction fee from the user's account. { \"options\": { \"enableGlobalFeePayer\": false } }
# Error Code This section contains the errors that might occur when using the KIP-17 API. KAS uses HTTP status codes. More details can be found in this link.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-17 API

Introduction The KIP-17 API helps BApp (Blockchain Application) developers to manage contracts and tokens created in accordance with the KIP-17 standard, which is Klaytn's technical speficication for Non-Fungible Tokens. The functionality of the multiple endpoints enables you to do the following actions: - deploy smart contracts - manage the entire life cycle of an NFT from minting, to sending and burning - get contract or token data - authorize a third party to execute token transfers - view token ownership history For more details on KAS, please refer to KAS Docs. If you have any questions or comments, please leave them in the Klaytn Developers Forum. alias When a method of the KIP-17 API requires a contract address, you can use the contract alias. You can give the contract an alias when deploying, and use it in place of the complicated address. # Fee Payer Options KAS KIP-17 supports four ways to pay the transaction fees.
1. Only using KAS Global FeePayer Account
Sends all transactions using KAS Global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer Account
Sends all transactions using User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account
Sends transactions using User FeePayer Account by default, and switches to the KAS Global FeePayer Account when balances are insufficient. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account
Sends transactions the default way, paying the transaction fee from the user's account. { \"options\": { \"enableGlobalFeePayer\": false } }
# Error Code This section contains the errors that might occur when using the KIP-17 API. KAS uses HTTP status codes. More details can be found in this link.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-17 API

Introduction The KIP-17 API helps BApp (Blockchain Application) developers to manage contracts and tokens created in accordance with the KIP-17 standard, which is Klaytn's technical speficication for Non-Fungible Tokens. The functionality of the multiple endpoints enables you to do the following actions: - deploy smart contracts - manage the entire life cycle of an NFT from minting, to sending and burning - get contract or token data - authorize a third party to execute token transfers - view token ownership history For more details on KAS, please refer to KAS Docs. If you have any questions or comments, please leave them in the Klaytn Developers Forum. alias When a method of the KIP-17 API requires a contract address, you can use the contract alias. You can give the contract an alias when deploying, and use it in place of the complicated address. # Fee Payer Options KAS KIP-17 supports four ways to pay the transaction fees.
1. Only using KAS Global FeePayer Account
Sends all transactions using KAS Global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer Account
Sends all transactions using User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account
Sends transactions using User FeePayer Account by default, and switches to the KAS Global FeePayer Account when balances are insufficient. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account
Sends transactions the default way, paying the transaction fee from the user's account. { \"options\": { \"enableGlobalFeePayer\": false } }
# Error Code This section contains the errors that might occur when using the KIP-17 API. KAS uses HTTP status codes. More details can be found in this link.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-17 API

Introduction The KIP-17 API helps BApp (Blockchain Application) developers to manage contracts and tokens created in accordance with the KIP-17 standard, which is Klaytn's technical speficication for Non-Fungible Tokens. The functionality of the multiple endpoints enables you to do the following actions: - deploy smart contracts - manage the entire life cycle of an NFT from minting, to sending and burning - get contract or token data - authorize a third party to execute token transfers - view token ownership history For more details on KAS, please refer to KAS Docs. If you have any questions or comments, please leave them in the Klaytn Developers Forum. alias When a method of the KIP-17 API requires a contract address, you can use the contract alias. You can give the contract an alias when deploying, and use it in place of the complicated address. # Fee Payer Options KAS KIP-17 supports four ways to pay the transaction fees.
1. Only using KAS Global FeePayer Account
Sends all transactions using KAS Global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer Account
Sends all transactions using User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account
Sends transactions using User FeePayer Account by default, and switches to the KAS Global FeePayer Account when balances are insufficient. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account
Sends transactions the default way, paying the transaction fee from the user's account. { \"options\": { \"enableGlobalFeePayer\": false } }
# Error Code This section contains the errors that might occur when using the KIP-17 API. KAS uses HTTP status codes. More details can be found in this link.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-17 API

Introduction The KIP-17 API helps BApp (Blockchain Application) developers to manage contracts and tokens created in accordance with the KIP-17 standard, which is Klaytn's technical speficication for Non-Fungible Tokens. The functionality of the multiple endpoints enables you to do the following actions: - deploy smart contracts - manage the entire life cycle of an NFT from minting, to sending and burning - get contract or token data - authorize a third party to execute token transfers - view token ownership history For more details on KAS, please refer to KAS Docs. If you have any questions or comments, please leave them in the Klaytn Developers Forum. alias When a method of the KIP-17 API requires a contract address, you can use the contract alias. You can give the contract an alias when deploying, and use it in place of the complicated address. # Fee Payer Options KAS KIP-17 supports four ways to pay the transaction fees.
1. Only using KAS Global FeePayer Account
Sends all transactions using KAS Global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer Account
Sends all transactions using User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account
Sends transactions using User FeePayer Account by default, and switches to the KAS Global FeePayer Account when balances are insufficient. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account
Sends transactions the default way, paying the transaction fee from the user's account. { \"options\": { \"enableGlobalFeePayer\": false } }
# Error Code This section contains the errors that might occur when using the KIP-17 API. KAS uses HTTP status codes. More details can be found in this link.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-17 API

Introduction The KIP-17 API helps BApp (Blockchain Application) developers to manage contracts and tokens created in accordance with the KIP-17 standard, which is Klaytn's technical speficication for Non-Fungible Tokens. The functionality of the multiple endpoints enables you to do the following actions: - deploy smart contracts - manage the entire life cycle of an NFT from minting, to sending and burning - get contract or token data - authorize a third party to execute token transfers - view token ownership history For more details on KAS, please refer to KAS Docs. If you have any questions or comments, please leave them in the Klaytn Developers Forum. alias When a method of the KIP-17 API requires a contract address, you can use the contract alias. You can give the contract an alias when deploying, and use it in place of the complicated address. # Fee Payer Options KAS KIP-17 supports four ways to pay the transaction fees.
1. Only using KAS Global FeePayer Account
Sends all transactions using KAS Global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer Account
Sends all transactions using User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account
Sends transactions using User FeePayer Account by default, and switches to the KAS Global FeePayer Account when balances are insufficient. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account
Sends transactions the default way, paying the transaction fee from the user's account. { \"options\": { \"enableGlobalFeePayer\": false } }
# Error Code This section contains the errors that might occur when using the KIP-17 API. KAS uses HTTP status codes. More details can be found in this link.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-37 API

Introduction The KIP-37 API helps Blockchain app (BApp) developers to easily deploy smart contracts and send tokens of the KIP-37 Multi Token Standard. You can use the default contract managing account (deployer) and alias. You can also manage the contracts and tokens created on the klaytn network using the caver SDK, using contract address and the Wallet API account. ## Fee Payer Options KAS KIP-37 supports four scenarios for paying transactin fees: 1. Using only KAS Global FeePayer Account Sends all transactions using the KAS global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer account Sends all transactions using the KAS User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account Uses User FeePayer Account as default. When the balance runs out, KAS Global FeePayer Account will be used. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account Sends a transaction via normal means where the sender pays the transaction fee. { \"options\": { \"enableGlobalFeePayer\": false } }

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-37 API

Introduction The KIP-37 API helps Blockchain app (BApp) developers to easily deploy smart contracts and send tokens of the KIP-37 Multi Token Standard. You can use the default contract managing account (deployer) and alias. You can also manage the contracts and tokens created on the klaytn network using the caver SDK, using contract address and the Wallet API account. ## Fee Payer Options KAS KIP-37 supports four scenarios for paying transactin fees: 1. Using only KAS Global FeePayer Account Sends all transactions using the KAS global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer account Sends all transactions using the KAS User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account Uses User FeePayer Account as default. When the balance runs out, KAS Global FeePayer Account will be used. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account Sends a transaction via normal means where the sender pays the transaction fee. { \"options\": { \"enableGlobalFeePayer\": false } }

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-37 API

Introduction The KIP-37 API helps Blockchain app (BApp) developers to easily deploy smart contracts and send tokens of the KIP-37 Multi Token Standard. You can use the default contract managing account (deployer) and alias. You can also manage the contracts and tokens created on the klaytn network using the caver SDK, using contract address and the Wallet API account. ## Fee Payer Options KAS KIP-37 supports four scenarios for paying transactin fees: 1. Using only KAS Global FeePayer Account Sends all transactions using the KAS global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer account Sends all transactions using the KAS User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account Uses User FeePayer Account as default. When the balance runs out, KAS Global FeePayer Account will be used. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account Sends a transaction via normal means where the sender pays the transaction fee. { \"options\": { \"enableGlobalFeePayer\": false } }

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-37 API

Introduction The KIP-37 API helps Blockchain app (BApp) developers to easily deploy smart contracts and send tokens of the KIP-37 Multi Token Standard. You can use the default contract managing account (deployer) and alias. You can also manage the contracts and tokens created on the klaytn network using the caver SDK, using contract address and the Wallet API account. ## Fee Payer Options KAS KIP-37 supports four scenarios for paying transactin fees: 1. Using only KAS Global FeePayer Account Sends all transactions using the KAS global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer account Sends all transactions using the KAS User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account Uses User FeePayer Account as default. When the balance runs out, KAS Global FeePayer Account will be used. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account Sends a transaction via normal means where the sender pays the transaction fee. { \"options\": { \"enableGlobalFeePayer\": false } }

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-37 API

Introduction The KIP-37 API helps Blockchain app (BApp) developers to easily deploy smart contracts and send tokens of the KIP-37 Multi Token Standard. You can use the default contract managing account (deployer) and alias. You can also manage the contracts and tokens created on the klaytn network using the caver SDK, using contract address and the Wallet API account. ## Fee Payer Options KAS KIP-37 supports four scenarios for paying transactin fees: 1. Using only KAS Global FeePayer Account Sends all transactions using the KAS global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer account Sends all transactions using the KAS User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account Uses User FeePayer Account as default. When the balance runs out, KAS Global FeePayer Account will be used. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account Sends a transaction via normal means where the sender pays the transaction fee. { \"options\": { \"enableGlobalFeePayer\": false } }

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-37 API

Introduction The KIP-37 API helps Blockchain app (BApp) developers to easily deploy smart contracts and send tokens of the KIP-37 Multi Token Standard. You can use the default contract managing account (deployer) and alias. You can also manage the contracts and tokens created on the klaytn network using the caver SDK, using contract address and the Wallet API account. ## Fee Payer Options KAS KIP-37 supports four scenarios for paying transactin fees: 1. Using only KAS Global FeePayer Account Sends all transactions using the KAS global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer account Sends all transactions using the KAS User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account Uses User FeePayer Account as default. When the balance runs out, KAS Global FeePayer Account will be used. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account Sends a transaction via normal means where the sender pays the transaction fee. { \"options\": { \"enableGlobalFeePayer\": false } }

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-37 API

Introduction The KIP-37 API helps Blockchain app (BApp) developers to easily deploy smart contracts and send tokens of the KIP-37 Multi Token Standard. You can use the default contract managing account (deployer) and alias. You can also manage the contracts and tokens created on the klaytn network using the caver SDK, using contract address and the Wallet API account. ## Fee Payer Options KAS KIP-37 supports four scenarios for paying transactin fees: 1. Using only KAS Global FeePayer Account Sends all transactions using the KAS global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer account Sends all transactions using the KAS User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account Uses User FeePayer Account as default. When the balance runs out, KAS Global FeePayer Account will be used. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account Sends a transaction via normal means where the sender pays the transaction fee. { \"options\": { \"enableGlobalFeePayer\": false } }

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-37 API

Introduction The KIP-37 API helps Blockchain app (BApp) developers to easily deploy smart contracts and send tokens of the KIP-37 Multi Token Standard. You can use the default contract managing account (deployer) and alias. You can also manage the contracts and tokens created on the klaytn network using the caver SDK, using contract address and the Wallet API account. ## Fee Payer Options KAS KIP-37 supports four scenarios for paying transactin fees: 1. Using only KAS Global FeePayer Account Sends all transactions using the KAS global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer account Sends all transactions using the KAS User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account Uses User FeePayer Account as default. When the balance runs out, KAS Global FeePayer Account will be used. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account Sends a transaction via normal means where the sender pays the transaction fee. { \"options\": { \"enableGlobalFeePayer\": false } }

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-37 API

Introduction The KIP-37 API helps Blockchain app (BApp) developers to easily deploy smart contracts and send tokens of the KIP-37 Multi Token Standard. You can use the default contract managing account (deployer) and alias. You can also manage the contracts and tokens created on the klaytn network using the caver SDK, using contract address and the Wallet API account. ## Fee Payer Options KAS KIP-37 supports four scenarios for paying transactin fees: 1. Using only KAS Global FeePayer Account Sends all transactions using the KAS global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer account Sends all transactions using the KAS User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account Uses User FeePayer Account as default. When the balance runs out, KAS Global FeePayer Account will be used. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account Sends a transaction via normal means where the sender pays the transaction fee. { \"options\": { \"enableGlobalFeePayer\": false } }

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-37 API

Introduction The KIP-37 API helps Blockchain app (BApp) developers to easily deploy smart contracts and send tokens of the KIP-37 Multi Token Standard. You can use the default contract managing account (deployer) and alias. You can also manage the contracts and tokens created on the klaytn network using the caver SDK, using contract address and the Wallet API account. ## Fee Payer Options KAS KIP-37 supports four scenarios for paying transactin fees: 1. Using only KAS Global FeePayer Account Sends all transactions using the KAS global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer account Sends all transactions using the KAS User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account Uses User FeePayer Account as default. When the balance runs out, KAS Global FeePayer Account will be used. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account Sends a transaction via normal means where the sender pays the transaction fee. { \"options\": { \"enableGlobalFeePayer\": false } }

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-37 API

Introduction The KIP-37 API helps Blockchain app (BApp) developers to easily deploy smart contracts and send tokens of the KIP-37 Multi Token Standard. You can use the default contract managing account (deployer) and alias. You can also manage the contracts and tokens created on the klaytn network using the caver SDK, using contract address and the Wallet API account. ## Fee Payer Options KAS KIP-37 supports four scenarios for paying transactin fees: 1. Using only KAS Global FeePayer Account Sends all transactions using the KAS global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer account Sends all transactions using the KAS User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account Uses User FeePayer Account as default. When the balance runs out, KAS Global FeePayer Account will be used. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account Sends a transaction via normal means where the sender pays the transaction fee. { \"options\": { \"enableGlobalFeePayer\": false } }

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-37 API

Introduction The KIP-37 API helps Blockchain app (BApp) developers to easily deploy smart contracts and send tokens of the KIP-37 Multi Token Standard. You can use the default contract managing account (deployer) and alias. You can also manage the contracts and tokens created on the klaytn network using the caver SDK, using contract address and the Wallet API account. ## Fee Payer Options KAS KIP-37 supports four scenarios for paying transactin fees: 1. Using only KAS Global FeePayer Account Sends all transactions using the KAS global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer account Sends all transactions using the KAS User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account Uses User FeePayer Account as default. When the balance runs out, KAS Global FeePayer Account will be used. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account Sends a transaction via normal means where the sender pays the transaction fee. { \"options\": { \"enableGlobalFeePayer\": false } }

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-37 API

Introduction The KIP-37 API helps Blockchain app (BApp) developers to easily deploy smart contracts and send tokens of the KIP-37 Multi Token Standard. You can use the default contract managing account (deployer) and alias. You can also manage the contracts and tokens created on the klaytn network using the caver SDK, using contract address and the Wallet API account. ## Fee Payer Options KAS KIP-37 supports four scenarios for paying transactin fees: 1. Using only KAS Global FeePayer Account Sends all transactions using the KAS global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer account Sends all transactions using the KAS User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account Uses User FeePayer Account as default. When the balance runs out, KAS Global FeePayer Account will be used. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account Sends a transaction via normal means where the sender pays the transaction fee. { \"options\": { \"enableGlobalFeePayer\": false } }

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-37 API

Introduction The KIP-37 API helps Blockchain app (BApp) developers to easily deploy smart contracts and send tokens of the KIP-37 Multi Token Standard. You can use the default contract managing account (deployer) and alias. You can also manage the contracts and tokens created on the klaytn network using the caver SDK, using contract address and the Wallet API account. ## Fee Payer Options KAS KIP-37 supports four scenarios for paying transactin fees: 1. Using only KAS Global FeePayer Account Sends all transactions using the KAS global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer account Sends all transactions using the KAS User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account Uses User FeePayer Account as default. When the balance runs out, KAS Global FeePayer Account will be used. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account Sends a transaction via normal means where the sender pays the transaction fee. { \"options\": { \"enableGlobalFeePayer\": false } }

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-37 API

Introduction The KIP-37 API helps Blockchain app (BApp) developers to easily deploy smart contracts and send tokens of the KIP-37 Multi Token Standard. You can use the default contract managing account (deployer) and alias. You can also manage the contracts and tokens created on the klaytn network using the caver SDK, using contract address and the Wallet API account. ## Fee Payer Options KAS KIP-37 supports four scenarios for paying transactin fees: 1. Using only KAS Global FeePayer Account Sends all transactions using the KAS global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer account Sends all transactions using the KAS User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account Uses User FeePayer Account as default. When the balance runs out, KAS Global FeePayer Account will be used. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account Sends a transaction via normal means where the sender pays the transaction fee. { \"options\": { \"enableGlobalFeePayer\": false } }

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-37 API

Introduction The KIP-37 API helps Blockchain app (BApp) developers to easily deploy smart contracts and send tokens of the KIP-37 Multi Token Standard. You can use the default contract managing account (deployer) and alias. You can also manage the contracts and tokens created on the klaytn network using the caver SDK, using contract address and the Wallet API account. ## Fee Payer Options KAS KIP-37 supports four scenarios for paying transactin fees: 1. Using only KAS Global FeePayer Account Sends all transactions using the KAS global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer account Sends all transactions using the KAS User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account Uses User FeePayer Account as default. When the balance runs out, KAS Global FeePayer Account will be used. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account Sends a transaction via normal means where the sender pays the transaction fee. { \"options\": { \"enableGlobalFeePayer\": false } }

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-37 API

Introduction The KIP-37 API helps Blockchain app (BApp) developers to easily deploy smart contracts and send tokens of the KIP-37 Multi Token Standard. You can use the default contract managing account (deployer) and alias. You can also manage the contracts and tokens created on the klaytn network using the caver SDK, using contract address and the Wallet API account. ## Fee Payer Options KAS KIP-37 supports four scenarios for paying transactin fees: 1. Using only KAS Global FeePayer Account Sends all transactions using the KAS global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer account Sends all transactions using the KAS User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account Uses User FeePayer Account as default. When the balance runs out, KAS Global FeePayer Account will be used. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account Sends a transaction via normal means where the sender pays the transaction fee. { \"options\": { \"enableGlobalFeePayer\": false } }

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-37 API

Introduction The KIP-37 API helps Blockchain app (BApp) developers to easily deploy smart contracts and send tokens of the KIP-37 Multi Token Standard. You can use the default contract managing account (deployer) and alias. You can also manage the contracts and tokens created on the klaytn network using the caver SDK, using contract address and the Wallet API account. ## Fee Payer Options KAS KIP-37 supports four scenarios for paying transactin fees: 1. Using only KAS Global FeePayer Account Sends all transactions using the KAS global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer account Sends all transactions using the KAS User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account Uses User FeePayer Account as default. When the balance runs out, KAS Global FeePayer Account will be used. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account Sends a transaction via normal means where the sender pays the transaction fee. { \"options\": { \"enableGlobalFeePayer\": false } }

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-37 API

Introduction The KIP-37 API helps Blockchain app (BApp) developers to easily deploy smart contracts and send tokens of the KIP-37 Multi Token Standard. You can use the default contract managing account (deployer) and alias. You can also manage the contracts and tokens created on the klaytn network using the caver SDK, using contract address and the Wallet API account. ## Fee Payer Options KAS KIP-37 supports four scenarios for paying transactin fees: 1. Using only KAS Global FeePayer Account Sends all transactions using the KAS global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer account Sends all transactions using the KAS User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account Uses User FeePayer Account as default. When the balance runs out, KAS Global FeePayer Account will be used. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account Sends a transaction via normal means where the sender pays the transaction fee. { \"options\": { \"enableGlobalFeePayer\": false } }

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-37 API

Introduction The KIP-37 API helps Blockchain app (BApp) developers to easily deploy smart contracts and send tokens of the KIP-37 Multi Token Standard. You can use the default contract managing account (deployer) and alias. You can also manage the contracts and tokens created on the klaytn network using the caver SDK, using contract address and the Wallet API account. ## Fee Payer Options KAS KIP-37 supports four scenarios for paying transactin fees: 1. Using only KAS Global FeePayer Account Sends all transactions using the KAS global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer account Sends all transactions using the KAS User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account Uses User FeePayer Account as default. When the balance runs out, KAS Global FeePayer Account will be used. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account Sends a transaction via normal means where the sender pays the transaction fee. { \"options\": { \"enableGlobalFeePayer\": false } }

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-37 API

Introduction The KIP-37 API helps Blockchain app (BApp) developers to easily deploy smart contracts and send tokens of the KIP-37 Multi Token Standard. You can use the default contract managing account (deployer) and alias. You can also manage the contracts and tokens created on the klaytn network using the caver SDK, using contract address and the Wallet API account. ## Fee Payer Options KAS KIP-37 supports four scenarios for paying transactin fees: 1. Using only KAS Global FeePayer Account Sends all transactions using the KAS global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer account Sends all transactions using the KAS User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account Uses User FeePayer Account as default. When the balance runs out, KAS Global FeePayer Account will be used. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account Sends a transaction via normal means where the sender pays the transaction fee. { \"options\": { \"enableGlobalFeePayer\": false } }

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-37 API

Introduction The KIP-37 API helps Blockchain app (BApp) developers to easily deploy smart contracts and send tokens of the KIP-37 Multi Token Standard. You can use the default contract managing account (deployer) and alias. You can also manage the contracts and tokens created on the klaytn network using the caver SDK, using contract address and the Wallet API account. ## Fee Payer Options KAS KIP-37 supports four scenarios for paying transactin fees: 1. Using only KAS Global FeePayer Account Sends all transactions using the KAS global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer account Sends all transactions using the KAS User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account Uses User FeePayer Account as default. When the balance runs out, KAS Global FeePayer Account will be used. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account Sends a transaction via normal means where the sender pays the transaction fee. { \"options\": { \"enableGlobalFeePayer\": false } }

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-37 API

Introduction The KIP-37 API helps Blockchain app (BApp) developers to easily deploy smart contracts and send tokens of the KIP-37 Multi Token Standard. You can use the default contract managing account (deployer) and alias. You can also manage the contracts and tokens created on the klaytn network using the caver SDK, using contract address and the Wallet API account. ## Fee Payer Options KAS KIP-37 supports four scenarios for paying transactin fees: 1. Using only KAS Global FeePayer Account Sends all transactions using the KAS global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer account Sends all transactions using the KAS User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account Uses User FeePayer Account as default. When the balance runs out, KAS Global FeePayer Account will be used. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account Sends a transaction via normal means where the sender pays the transaction fee. { \"options\": { \"enableGlobalFeePayer\": false } }

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-37 API

Introduction The KIP-37 API helps Blockchain app (BApp) developers to easily deploy smart contracts and send tokens of the KIP-37 Multi Token Standard. You can use the default contract managing account (deployer) and alias. You can also manage the contracts and tokens created on the klaytn network using the caver SDK, using contract address and the Wallet API account. ## Fee Payer Options KAS KIP-37 supports four scenarios for paying transactin fees: 1. Using only KAS Global FeePayer Account Sends all transactions using the KAS global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer account Sends all transactions using the KAS User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account Uses User FeePayer Account as default. When the balance runs out, KAS Global FeePayer Account will be used. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account Sends a transaction via normal means where the sender pays the transaction fee. { \"options\": { \"enableGlobalFeePayer\": false } }

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-37 API

Introduction The KIP-37 API helps Blockchain app (BApp) developers to easily deploy smart contracts and send tokens of the KIP-37 Multi Token Standard. You can use the default contract managing account (deployer) and alias. You can also manage the contracts and tokens created on the klaytn network using the caver SDK, using contract address and the Wallet API account. ## Fee Payer Options KAS KIP-37 supports four scenarios for paying transactin fees: 1. Using only KAS Global FeePayer Account Sends all transactions using the KAS global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer account Sends all transactions using the KAS User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account Uses User FeePayer Account as default. When the balance runs out, KAS Global FeePayer Account will be used. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account Sends a transaction via normal means where the sender pays the transaction fee. { \"options\": { \"enableGlobalFeePayer\": false } }

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-37 API

Introduction The KIP-37 API helps Blockchain app (BApp) developers to easily deploy smart contracts and send tokens of the KIP-37 Multi Token Standard. You can use the default contract managing account (deployer) and alias. You can also manage the contracts and tokens created on the klaytn network using the caver SDK, using contract address and the Wallet API account. ## Fee Payer Options KAS KIP-37 supports four scenarios for paying transactin fees: 1. Using only KAS Global FeePayer Account Sends all transactions using the KAS global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer account Sends all transactions using the KAS User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account Uses User FeePayer Account as default. When the balance runs out, KAS Global FeePayer Account will be used. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account Sends a transaction via normal means where the sender pays the transaction fee. { \"options\": { \"enableGlobalFeePayer\": false } }

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-7 API

Introduction The KIP-17 API helps BApp (Blockchain Application) developers to manage contracts and tokens created in accordance with the KIP-7 standard, which is Klaytn's technical speficication for Fungible Tokens. The functionality of the multiple endpoints enables you to do the following actions: - deploy smart contracts - manage the entire life cycle of an FT from minting, to sending and burning - get contract or token data - authorize a third party to execute token transfers - send tokens on behalf of the owner For more details on KAS, please refer to KAS Docs. If you have any questions or comments, please leave them in the Klaytn Developers Forum. alias When a method of the KIP-17 API requires a contract address, you can use the contract alias. You can give the contract an alias when deploying, and use it in place of the complicated address. deployer When you create a contract, you will be assigned one deployer address per Credential, which is the account address used for managing contracts. In KIP-7 API, this address is used in many different token-related operations. You can find the deployer address with KIP7Deployer. Even with contracts created using SDKs like "caver", you can still use the contract address and Wallet API account to manage your contracts and tokens. # Fee Payer Options KAS KIP-17 supports four ways to pay the transaction fees.
1. Only using KAS Global FeePayer Account
Sends all transactions using KAS Global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer Account
Sends all transactions using User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account
Sends transactions using User FeePayer Account by default, and switches to the KAS Global FeePayer Account when balances are insufficient. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account
Sends transactions the default way, paying the transaction fee from the user's account. { \"options\": { \"enableGlobalFeePayer\": false } } # Error Code This section contains the errors that might occur when using the KIP-17 API. KAS uses HTTP status codes. More details can be found in this link.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-7 API

Introduction The KIP-17 API helps BApp (Blockchain Application) developers to manage contracts and tokens created in accordance with the KIP-7 standard, which is Klaytn's technical speficication for Fungible Tokens. The functionality of the multiple endpoints enables you to do the following actions: - deploy smart contracts - manage the entire life cycle of an FT from minting, to sending and burning - get contract or token data - authorize a third party to execute token transfers - send tokens on behalf of the owner For more details on KAS, please refer to KAS Docs. If you have any questions or comments, please leave them in the Klaytn Developers Forum. alias When a method of the KIP-17 API requires a contract address, you can use the contract alias. You can give the contract an alias when deploying, and use it in place of the complicated address. deployer When you create a contract, you will be assigned one deployer address per Credential, which is the account address used for managing contracts. In KIP-7 API, this address is used in many different token-related operations. You can find the deployer address with KIP7Deployer. Even with contracts created using SDKs like "caver", you can still use the contract address and Wallet API account to manage your contracts and tokens. # Fee Payer Options KAS KIP-17 supports four ways to pay the transaction fees.
1. Only using KAS Global FeePayer Account
Sends all transactions using KAS Global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer Account
Sends all transactions using User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account
Sends transactions using User FeePayer Account by default, and switches to the KAS Global FeePayer Account when balances are insufficient. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account
Sends transactions the default way, paying the transaction fee from the user's account. { \"options\": { \"enableGlobalFeePayer\": false } } # Error Code This section contains the errors that might occur when using the KIP-17 API. KAS uses HTTP status codes. More details can be found in this link.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-7 API

Introduction The KIP-17 API helps BApp (Blockchain Application) developers to manage contracts and tokens created in accordance with the KIP-7 standard, which is Klaytn's technical speficication for Fungible Tokens. The functionality of the multiple endpoints enables you to do the following actions: - deploy smart contracts - manage the entire life cycle of an FT from minting, to sending and burning - get contract or token data - authorize a third party to execute token transfers - send tokens on behalf of the owner For more details on KAS, please refer to KAS Docs. If you have any questions or comments, please leave them in the Klaytn Developers Forum. alias When a method of the KIP-17 API requires a contract address, you can use the contract alias. You can give the contract an alias when deploying, and use it in place of the complicated address. deployer When you create a contract, you will be assigned one deployer address per Credential, which is the account address used for managing contracts. In KIP-7 API, this address is used in many different token-related operations. You can find the deployer address with KIP7Deployer. Even with contracts created using SDKs like "caver", you can still use the contract address and Wallet API account to manage your contracts and tokens. # Fee Payer Options KAS KIP-17 supports four ways to pay the transaction fees.
1. Only using KAS Global FeePayer Account
Sends all transactions using KAS Global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer Account
Sends all transactions using User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account
Sends transactions using User FeePayer Account by default, and switches to the KAS Global FeePayer Account when balances are insufficient. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account
Sends transactions the default way, paying the transaction fee from the user's account. { \"options\": { \"enableGlobalFeePayer\": false } } # Error Code This section contains the errors that might occur when using the KIP-17 API. KAS uses HTTP status codes. More details can be found in this link.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-7 API

Introduction The KIP-17 API helps BApp (Blockchain Application) developers to manage contracts and tokens created in accordance with the KIP-7 standard, which is Klaytn's technical speficication for Fungible Tokens. The functionality of the multiple endpoints enables you to do the following actions: - deploy smart contracts - manage the entire life cycle of an FT from minting, to sending and burning - get contract or token data - authorize a third party to execute token transfers - send tokens on behalf of the owner For more details on KAS, please refer to KAS Docs. If you have any questions or comments, please leave them in the Klaytn Developers Forum. alias When a method of the KIP-17 API requires a contract address, you can use the contract alias. You can give the contract an alias when deploying, and use it in place of the complicated address. deployer When you create a contract, you will be assigned one deployer address per Credential, which is the account address used for managing contracts. In KIP-7 API, this address is used in many different token-related operations. You can find the deployer address with KIP7Deployer. Even with contracts created using SDKs like "caver", you can still use the contract address and Wallet API account to manage your contracts and tokens. # Fee Payer Options KAS KIP-17 supports four ways to pay the transaction fees.
1. Only using KAS Global FeePayer Account
Sends all transactions using KAS Global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer Account
Sends all transactions using User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account
Sends transactions using User FeePayer Account by default, and switches to the KAS Global FeePayer Account when balances are insufficient. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account
Sends transactions the default way, paying the transaction fee from the user's account. { \"options\": { \"enableGlobalFeePayer\": false } } # Error Code This section contains the errors that might occur when using the KIP-17 API. KAS uses HTTP status codes. More details can be found in this link.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-7 API

Introduction The KIP-17 API helps BApp (Blockchain Application) developers to manage contracts and tokens created in accordance with the KIP-7 standard, which is Klaytn's technical speficication for Fungible Tokens. The functionality of the multiple endpoints enables you to do the following actions: - deploy smart contracts - manage the entire life cycle of an FT from minting, to sending and burning - get contract or token data - authorize a third party to execute token transfers - send tokens on behalf of the owner For more details on KAS, please refer to KAS Docs. If you have any questions or comments, please leave them in the Klaytn Developers Forum. alias When a method of the KIP-17 API requires a contract address, you can use the contract alias. You can give the contract an alias when deploying, and use it in place of the complicated address. deployer When you create a contract, you will be assigned one deployer address per Credential, which is the account address used for managing contracts. In KIP-7 API, this address is used in many different token-related operations. You can find the deployer address with KIP7Deployer. Even with contracts created using SDKs like "caver", you can still use the contract address and Wallet API account to manage your contracts and tokens. # Fee Payer Options KAS KIP-17 supports four ways to pay the transaction fees.
1. Only using KAS Global FeePayer Account
Sends all transactions using KAS Global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer Account
Sends all transactions using User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account
Sends transactions using User FeePayer Account by default, and switches to the KAS Global FeePayer Account when balances are insufficient. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account
Sends transactions the default way, paying the transaction fee from the user's account. { \"options\": { \"enableGlobalFeePayer\": false } } # Error Code This section contains the errors that might occur when using the KIP-17 API. KAS uses HTTP status codes. More details can be found in this link.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-7 API

Introduction The KIP-17 API helps BApp (Blockchain Application) developers to manage contracts and tokens created in accordance with the KIP-7 standard, which is Klaytn's technical speficication for Fungible Tokens. The functionality of the multiple endpoints enables you to do the following actions: - deploy smart contracts - manage the entire life cycle of an FT from minting, to sending and burning - get contract or token data - authorize a third party to execute token transfers - send tokens on behalf of the owner For more details on KAS, please refer to KAS Docs. If you have any questions or comments, please leave them in the Klaytn Developers Forum. alias When a method of the KIP-17 API requires a contract address, you can use the contract alias. You can give the contract an alias when deploying, and use it in place of the complicated address. deployer When you create a contract, you will be assigned one deployer address per Credential, which is the account address used for managing contracts. In KIP-7 API, this address is used in many different token-related operations. You can find the deployer address with KIP7Deployer. Even with contracts created using SDKs like "caver", you can still use the contract address and Wallet API account to manage your contracts and tokens. # Fee Payer Options KAS KIP-17 supports four ways to pay the transaction fees.
1. Only using KAS Global FeePayer Account
Sends all transactions using KAS Global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer Account
Sends all transactions using User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account
Sends transactions using User FeePayer Account by default, and switches to the KAS Global FeePayer Account when balances are insufficient. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account
Sends transactions the default way, paying the transaction fee from the user's account. { \"options\": { \"enableGlobalFeePayer\": false } } # Error Code This section contains the errors that might occur when using the KIP-17 API. KAS uses HTTP status codes. More details can be found in this link.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-7 API

Introduction The KIP-17 API helps BApp (Blockchain Application) developers to manage contracts and tokens created in accordance with the KIP-7 standard, which is Klaytn's technical speficication for Fungible Tokens. The functionality of the multiple endpoints enables you to do the following actions: - deploy smart contracts - manage the entire life cycle of an FT from minting, to sending and burning - get contract or token data - authorize a third party to execute token transfers - send tokens on behalf of the owner For more details on KAS, please refer to KAS Docs. If you have any questions or comments, please leave them in the Klaytn Developers Forum. alias When a method of the KIP-17 API requires a contract address, you can use the contract alias. You can give the contract an alias when deploying, and use it in place of the complicated address. deployer When you create a contract, you will be assigned one deployer address per Credential, which is the account address used for managing contracts. In KIP-7 API, this address is used in many different token-related operations. You can find the deployer address with KIP7Deployer. Even with contracts created using SDKs like "caver", you can still use the contract address and Wallet API account to manage your contracts and tokens. # Fee Payer Options KAS KIP-17 supports four ways to pay the transaction fees.
1. Only using KAS Global FeePayer Account
Sends all transactions using KAS Global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer Account
Sends all transactions using User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account
Sends transactions using User FeePayer Account by default, and switches to the KAS Global FeePayer Account when balances are insufficient. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account
Sends transactions the default way, paying the transaction fee from the user's account. { \"options\": { \"enableGlobalFeePayer\": false } } # Error Code This section contains the errors that might occur when using the KIP-17 API. KAS uses HTTP status codes. More details can be found in this link.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-7 API

Introduction The KIP-17 API helps BApp (Blockchain Application) developers to manage contracts and tokens created in accordance with the KIP-7 standard, which is Klaytn's technical speficication for Fungible Tokens. The functionality of the multiple endpoints enables you to do the following actions: - deploy smart contracts - manage the entire life cycle of an FT from minting, to sending and burning - get contract or token data - authorize a third party to execute token transfers - send tokens on behalf of the owner For more details on KAS, please refer to KAS Docs. If you have any questions or comments, please leave them in the Klaytn Developers Forum. alias When a method of the KIP-17 API requires a contract address, you can use the contract alias. You can give the contract an alias when deploying, and use it in place of the complicated address. deployer When you create a contract, you will be assigned one deployer address per Credential, which is the account address used for managing contracts. In KIP-7 API, this address is used in many different token-related operations. You can find the deployer address with KIP7Deployer. Even with contracts created using SDKs like "caver", you can still use the contract address and Wallet API account to manage your contracts and tokens. # Fee Payer Options KAS KIP-17 supports four ways to pay the transaction fees.
1. Only using KAS Global FeePayer Account
Sends all transactions using KAS Global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer Account
Sends all transactions using User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account
Sends transactions using User FeePayer Account by default, and switches to the KAS Global FeePayer Account when balances are insufficient. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account
Sends transactions the default way, paying the transaction fee from the user's account. { \"options\": { \"enableGlobalFeePayer\": false } } # Error Code This section contains the errors that might occur when using the KIP-17 API. KAS uses HTTP status codes. More details can be found in this link.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-7 API

Introduction The KIP-17 API helps BApp (Blockchain Application) developers to manage contracts and tokens created in accordance with the KIP-7 standard, which is Klaytn's technical speficication for Fungible Tokens. The functionality of the multiple endpoints enables you to do the following actions: - deploy smart contracts - manage the entire life cycle of an FT from minting, to sending and burning - get contract or token data - authorize a third party to execute token transfers - send tokens on behalf of the owner For more details on KAS, please refer to KAS Docs. If you have any questions or comments, please leave them in the Klaytn Developers Forum. alias When a method of the KIP-17 API requires a contract address, you can use the contract alias. You can give the contract an alias when deploying, and use it in place of the complicated address. deployer When you create a contract, you will be assigned one deployer address per Credential, which is the account address used for managing contracts. In KIP-7 API, this address is used in many different token-related operations. You can find the deployer address with KIP7Deployer. Even with contracts created using SDKs like "caver", you can still use the contract address and Wallet API account to manage your contracts and tokens. # Fee Payer Options KAS KIP-17 supports four ways to pay the transaction fees.
1. Only using KAS Global FeePayer Account
Sends all transactions using KAS Global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer Account
Sends all transactions using User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account
Sends transactions using User FeePayer Account by default, and switches to the KAS Global FeePayer Account when balances are insufficient. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account
Sends transactions the default way, paying the transaction fee from the user's account. { \"options\": { \"enableGlobalFeePayer\": false } } # Error Code This section contains the errors that might occur when using the KIP-17 API. KAS uses HTTP status codes. More details can be found in this link.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-7 API

Introduction The KIP-17 API helps BApp (Blockchain Application) developers to manage contracts and tokens created in accordance with the KIP-7 standard, which is Klaytn's technical speficication for Fungible Tokens. The functionality of the multiple endpoints enables you to do the following actions: - deploy smart contracts - manage the entire life cycle of an FT from minting, to sending and burning - get contract or token data - authorize a third party to execute token transfers - send tokens on behalf of the owner For more details on KAS, please refer to KAS Docs. If you have any questions or comments, please leave them in the Klaytn Developers Forum. alias When a method of the KIP-17 API requires a contract address, you can use the contract alias. You can give the contract an alias when deploying, and use it in place of the complicated address. deployer When you create a contract, you will be assigned one deployer address per Credential, which is the account address used for managing contracts. In KIP-7 API, this address is used in many different token-related operations. You can find the deployer address with KIP7Deployer. Even with contracts created using SDKs like "caver", you can still use the contract address and Wallet API account to manage your contracts and tokens. # Fee Payer Options KAS KIP-17 supports four ways to pay the transaction fees.
1. Only using KAS Global FeePayer Account
Sends all transactions using KAS Global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer Account
Sends all transactions using User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account
Sends transactions using User FeePayer Account by default, and switches to the KAS Global FeePayer Account when balances are insufficient. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account
Sends transactions the default way, paying the transaction fee from the user's account. { \"options\": { \"enableGlobalFeePayer\": false } } # Error Code This section contains the errors that might occur when using the KIP-17 API. KAS uses HTTP status codes. More details can be found in this link.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-7 API

Introduction The KIP-17 API helps BApp (Blockchain Application) developers to manage contracts and tokens created in accordance with the KIP-7 standard, which is Klaytn's technical speficication for Fungible Tokens. The functionality of the multiple endpoints enables you to do the following actions: - deploy smart contracts - manage the entire life cycle of an FT from minting, to sending and burning - get contract or token data - authorize a third party to execute token transfers - send tokens on behalf of the owner For more details on KAS, please refer to KAS Docs. If you have any questions or comments, please leave them in the Klaytn Developers Forum. alias When a method of the KIP-17 API requires a contract address, you can use the contract alias. You can give the contract an alias when deploying, and use it in place of the complicated address. deployer When you create a contract, you will be assigned one deployer address per Credential, which is the account address used for managing contracts. In KIP-7 API, this address is used in many different token-related operations. You can find the deployer address with KIP7Deployer. Even with contracts created using SDKs like "caver", you can still use the contract address and Wallet API account to manage your contracts and tokens. # Fee Payer Options KAS KIP-17 supports four ways to pay the transaction fees.
1. Only using KAS Global FeePayer Account
Sends all transactions using KAS Global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer Account
Sends all transactions using User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account
Sends transactions using User FeePayer Account by default, and switches to the KAS Global FeePayer Account when balances are insufficient. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account
Sends transactions the default way, paying the transaction fee from the user's account. { \"options\": { \"enableGlobalFeePayer\": false } } # Error Code This section contains the errors that might occur when using the KIP-17 API. KAS uses HTTP status codes. More details can be found in this link.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-7 API

Introduction The KIP-17 API helps BApp (Blockchain Application) developers to manage contracts and tokens created in accordance with the KIP-7 standard, which is Klaytn's technical speficication for Fungible Tokens. The functionality of the multiple endpoints enables you to do the following actions: - deploy smart contracts - manage the entire life cycle of an FT from minting, to sending and burning - get contract or token data - authorize a third party to execute token transfers - send tokens on behalf of the owner For more details on KAS, please refer to KAS Docs. If you have any questions or comments, please leave them in the Klaytn Developers Forum. alias When a method of the KIP-17 API requires a contract address, you can use the contract alias. You can give the contract an alias when deploying, and use it in place of the complicated address. deployer When you create a contract, you will be assigned one deployer address per Credential, which is the account address used for managing contracts. In KIP-7 API, this address is used in many different token-related operations. You can find the deployer address with KIP7Deployer. Even with contracts created using SDKs like "caver", you can still use the contract address and Wallet API account to manage your contracts and tokens. # Fee Payer Options KAS KIP-17 supports four ways to pay the transaction fees.
1. Only using KAS Global FeePayer Account
Sends all transactions using KAS Global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer Account
Sends all transactions using User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account
Sends transactions using User FeePayer Account by default, and switches to the KAS Global FeePayer Account when balances are insufficient. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account
Sends transactions the default way, paying the transaction fee from the user's account. { \"options\": { \"enableGlobalFeePayer\": false } } # Error Code This section contains the errors that might occur when using the KIP-17 API. KAS uses HTTP status codes. More details can be found in this link.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-7 API

Introduction The KIP-17 API helps BApp (Blockchain Application) developers to manage contracts and tokens created in accordance with the KIP-7 standard, which is Klaytn's technical speficication for Fungible Tokens. The functionality of the multiple endpoints enables you to do the following actions: - deploy smart contracts - manage the entire life cycle of an FT from minting, to sending and burning - get contract or token data - authorize a third party to execute token transfers - send tokens on behalf of the owner For more details on KAS, please refer to KAS Docs. If you have any questions or comments, please leave them in the Klaytn Developers Forum. alias When a method of the KIP-17 API requires a contract address, you can use the contract alias. You can give the contract an alias when deploying, and use it in place of the complicated address. deployer When you create a contract, you will be assigned one deployer address per Credential, which is the account address used for managing contracts. In KIP-7 API, this address is used in many different token-related operations. You can find the deployer address with KIP7Deployer. Even with contracts created using SDKs like "caver", you can still use the contract address and Wallet API account to manage your contracts and tokens. # Fee Payer Options KAS KIP-17 supports four ways to pay the transaction fees.
1. Only using KAS Global FeePayer Account
Sends all transactions using KAS Global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer Account
Sends all transactions using User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account
Sends transactions using User FeePayer Account by default, and switches to the KAS Global FeePayer Account when balances are insufficient. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account
Sends transactions the default way, paying the transaction fee from the user's account. { \"options\": { \"enableGlobalFeePayer\": false } } # Error Code This section contains the errors that might occur when using the KIP-17 API. KAS uses HTTP status codes. More details can be found in this link.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-7 API

Introduction The KIP-17 API helps BApp (Blockchain Application) developers to manage contracts and tokens created in accordance with the KIP-7 standard, which is Klaytn's technical speficication for Fungible Tokens. The functionality of the multiple endpoints enables you to do the following actions: - deploy smart contracts - manage the entire life cycle of an FT from minting, to sending and burning - get contract or token data - authorize a third party to execute token transfers - send tokens on behalf of the owner For more details on KAS, please refer to KAS Docs. If you have any questions or comments, please leave them in the Klaytn Developers Forum. alias When a method of the KIP-17 API requires a contract address, you can use the contract alias. You can give the contract an alias when deploying, and use it in place of the complicated address. deployer When you create a contract, you will be assigned one deployer address per Credential, which is the account address used for managing contracts. In KIP-7 API, this address is used in many different token-related operations. You can find the deployer address with KIP7Deployer. Even with contracts created using SDKs like "caver", you can still use the contract address and Wallet API account to manage your contracts and tokens. # Fee Payer Options KAS KIP-17 supports four ways to pay the transaction fees.
1. Only using KAS Global FeePayer Account
Sends all transactions using KAS Global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer Account
Sends all transactions using User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account
Sends transactions using User FeePayer Account by default, and switches to the KAS Global FeePayer Account when balances are insufficient. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account
Sends transactions the default way, paying the transaction fee from the user's account. { \"options\": { \"enableGlobalFeePayer\": false } } # Error Code This section contains the errors that might occur when using the KIP-17 API. KAS uses HTTP status codes. More details can be found in this link.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-7 API

Introduction The KIP-17 API helps BApp (Blockchain Application) developers to manage contracts and tokens created in accordance with the KIP-7 standard, which is Klaytn's technical speficication for Fungible Tokens. The functionality of the multiple endpoints enables you to do the following actions: - deploy smart contracts - manage the entire life cycle of an FT from minting, to sending and burning - get contract or token data - authorize a third party to execute token transfers - send tokens on behalf of the owner For more details on KAS, please refer to KAS Docs. If you have any questions or comments, please leave them in the Klaytn Developers Forum. alias When a method of the KIP-17 API requires a contract address, you can use the contract alias. You can give the contract an alias when deploying, and use it in place of the complicated address. deployer When you create a contract, you will be assigned one deployer address per Credential, which is the account address used for managing contracts. In KIP-7 API, this address is used in many different token-related operations. You can find the deployer address with KIP7Deployer. Even with contracts created using SDKs like "caver", you can still use the contract address and Wallet API account to manage your contracts and tokens. # Fee Payer Options KAS KIP-17 supports four ways to pay the transaction fees.
1. Only using KAS Global FeePayer Account
Sends all transactions using KAS Global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer Account
Sends all transactions using User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account
Sends transactions using User FeePayer Account by default, and switches to the KAS Global FeePayer Account when balances are insufficient. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account
Sends transactions the default way, paying the transaction fee from the user's account. { \"options\": { \"enableGlobalFeePayer\": false } } # Error Code This section contains the errors that might occur when using the KIP-17 API. KAS uses HTTP status codes. More details can be found in this link.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-7 API

Introduction The KIP-17 API helps BApp (Blockchain Application) developers to manage contracts and tokens created in accordance with the KIP-7 standard, which is Klaytn's technical speficication for Fungible Tokens. The functionality of the multiple endpoints enables you to do the following actions: - deploy smart contracts - manage the entire life cycle of an FT from minting, to sending and burning - get contract or token data - authorize a third party to execute token transfers - send tokens on behalf of the owner For more details on KAS, please refer to KAS Docs. If you have any questions or comments, please leave them in the Klaytn Developers Forum. alias When a method of the KIP-17 API requires a contract address, you can use the contract alias. You can give the contract an alias when deploying, and use it in place of the complicated address. deployer When you create a contract, you will be assigned one deployer address per Credential, which is the account address used for managing contracts. In KIP-7 API, this address is used in many different token-related operations. You can find the deployer address with KIP7Deployer. Even with contracts created using SDKs like "caver", you can still use the contract address and Wallet API account to manage your contracts and tokens. # Fee Payer Options KAS KIP-17 supports four ways to pay the transaction fees.
1. Only using KAS Global FeePayer Account
Sends all transactions using KAS Global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer Account
Sends all transactions using User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account
Sends transactions using User FeePayer Account by default, and switches to the KAS Global FeePayer Account when balances are insufficient. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account
Sends transactions the default way, paying the transaction fee from the user's account. { \"options\": { \"enableGlobalFeePayer\": false } } # Error Code This section contains the errors that might occur when using the KIP-17 API. KAS uses HTTP status codes. More details can be found in this link.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-7 API

Introduction The KIP-17 API helps BApp (Blockchain Application) developers to manage contracts and tokens created in accordance with the KIP-7 standard, which is Klaytn's technical speficication for Fungible Tokens. The functionality of the multiple endpoints enables you to do the following actions: - deploy smart contracts - manage the entire life cycle of an FT from minting, to sending and burning - get contract or token data - authorize a third party to execute token transfers - send tokens on behalf of the owner For more details on KAS, please refer to KAS Docs. If you have any questions or comments, please leave them in the Klaytn Developers Forum. alias When a method of the KIP-17 API requires a contract address, you can use the contract alias. You can give the contract an alias when deploying, and use it in place of the complicated address. deployer When you create a contract, you will be assigned one deployer address per Credential, which is the account address used for managing contracts. In KIP-7 API, this address is used in many different token-related operations. You can find the deployer address with KIP7Deployer. Even with contracts created using SDKs like "caver", you can still use the contract address and Wallet API account to manage your contracts and tokens. # Fee Payer Options KAS KIP-17 supports four ways to pay the transaction fees.
1. Only using KAS Global FeePayer Account
Sends all transactions using KAS Global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer Account
Sends all transactions using User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account
Sends transactions using User FeePayer Account by default, and switches to the KAS Global FeePayer Account when balances are insufficient. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account
Sends transactions the default way, paying the transaction fee from the user's account. { \"options\": { \"enableGlobalFeePayer\": false } } # Error Code This section contains the errors that might occur when using the KIP-17 API. KAS uses HTTP status codes. More details can be found in this link.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-7 API

Introduction The KIP-17 API helps BApp (Blockchain Application) developers to manage contracts and tokens created in accordance with the KIP-7 standard, which is Klaytn's technical speficication for Fungible Tokens. The functionality of the multiple endpoints enables you to do the following actions: - deploy smart contracts - manage the entire life cycle of an FT from minting, to sending and burning - get contract or token data - authorize a third party to execute token transfers - send tokens on behalf of the owner For more details on KAS, please refer to KAS Docs. If you have any questions or comments, please leave them in the Klaytn Developers Forum. alias When a method of the KIP-17 API requires a contract address, you can use the contract alias. You can give the contract an alias when deploying, and use it in place of the complicated address. deployer When you create a contract, you will be assigned one deployer address per Credential, which is the account address used for managing contracts. In KIP-7 API, this address is used in many different token-related operations. You can find the deployer address with KIP7Deployer. Even with contracts created using SDKs like "caver", you can still use the contract address and Wallet API account to manage your contracts and tokens. # Fee Payer Options KAS KIP-17 supports four ways to pay the transaction fees.
1. Only using KAS Global FeePayer Account
Sends all transactions using KAS Global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer Account
Sends all transactions using User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account
Sends transactions using User FeePayer Account by default, and switches to the KAS Global FeePayer Account when balances are insufficient. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account
Sends transactions the default way, paying the transaction fee from the user's account. { \"options\": { \"enableGlobalFeePayer\": false } } # Error Code This section contains the errors that might occur when using the KIP-17 API. KAS uses HTTP status codes. More details can be found in this link.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-7 API

Introduction The KIP-17 API helps BApp (Blockchain Application) developers to manage contracts and tokens created in accordance with the KIP-7 standard, which is Klaytn's technical speficication for Fungible Tokens. The functionality of the multiple endpoints enables you to do the following actions: - deploy smart contracts - manage the entire life cycle of an FT from minting, to sending and burning - get contract or token data - authorize a third party to execute token transfers - send tokens on behalf of the owner For more details on KAS, please refer to KAS Docs. If you have any questions or comments, please leave them in the Klaytn Developers Forum. alias When a method of the KIP-17 API requires a contract address, you can use the contract alias. You can give the contract an alias when deploying, and use it in place of the complicated address. deployer When you create a contract, you will be assigned one deployer address per Credential, which is the account address used for managing contracts. In KIP-7 API, this address is used in many different token-related operations. You can find the deployer address with KIP7Deployer. Even with contracts created using SDKs like "caver", you can still use the contract address and Wallet API account to manage your contracts and tokens. # Fee Payer Options KAS KIP-17 supports four ways to pay the transaction fees.
1. Only using KAS Global FeePayer Account
Sends all transactions using KAS Global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer Account
Sends all transactions using User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account
Sends transactions using User FeePayer Account by default, and switches to the KAS Global FeePayer Account when balances are insufficient. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account
Sends transactions the default way, paying the transaction fee from the user's account. { \"options\": { \"enableGlobalFeePayer\": false } } # Error Code This section contains the errors that might occur when using the KIP-17 API. KAS uses HTTP status codes. More details can be found in this link.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-7 API

Introduction The KIP-17 API helps BApp (Blockchain Application) developers to manage contracts and tokens created in accordance with the KIP-7 standard, which is Klaytn's technical speficication for Fungible Tokens. The functionality of the multiple endpoints enables you to do the following actions: - deploy smart contracts - manage the entire life cycle of an FT from minting, to sending and burning - get contract or token data - authorize a third party to execute token transfers - send tokens on behalf of the owner For more details on KAS, please refer to KAS Docs. If you have any questions or comments, please leave them in the Klaytn Developers Forum. alias When a method of the KIP-17 API requires a contract address, you can use the contract alias. You can give the contract an alias when deploying, and use it in place of the complicated address. deployer When you create a contract, you will be assigned one deployer address per Credential, which is the account address used for managing contracts. In KIP-7 API, this address is used in many different token-related operations. You can find the deployer address with KIP7Deployer. Even with contracts created using SDKs like "caver", you can still use the contract address and Wallet API account to manage your contracts and tokens. # Fee Payer Options KAS KIP-17 supports four ways to pay the transaction fees.
1. Only using KAS Global FeePayer Account
Sends all transactions using KAS Global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer Account
Sends all transactions using User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account
Sends transactions using User FeePayer Account by default, and switches to the KAS Global FeePayer Account when balances are insufficient. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account
Sends transactions the default way, paying the transaction fee from the user's account. { \"options\": { \"enableGlobalFeePayer\": false } } # Error Code This section contains the errors that might occur when using the KIP-17 API. KAS uses HTTP status codes. More details can be found in this link.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-7 API

Introduction The KIP-17 API helps BApp (Blockchain Application) developers to manage contracts and tokens created in accordance with the KIP-7 standard, which is Klaytn's technical speficication for Fungible Tokens. The functionality of the multiple endpoints enables you to do the following actions: - deploy smart contracts - manage the entire life cycle of an FT from minting, to sending and burning - get contract or token data - authorize a third party to execute token transfers - send tokens on behalf of the owner For more details on KAS, please refer to KAS Docs. If you have any questions or comments, please leave them in the Klaytn Developers Forum. alias When a method of the KIP-17 API requires a contract address, you can use the contract alias. You can give the contract an alias when deploying, and use it in place of the complicated address. deployer When you create a contract, you will be assigned one deployer address per Credential, which is the account address used for managing contracts. In KIP-7 API, this address is used in many different token-related operations. You can find the deployer address with KIP7Deployer. Even with contracts created using SDKs like "caver", you can still use the contract address and Wallet API account to manage your contracts and tokens. # Fee Payer Options KAS KIP-17 supports four ways to pay the transaction fees.
1. Only using KAS Global FeePayer Account
Sends all transactions using KAS Global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer Account
Sends all transactions using User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account
Sends transactions using User FeePayer Account by default, and switches to the KAS Global FeePayer Account when balances are insufficient. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account
Sends transactions the default way, paying the transaction fee from the user's account. { \"options\": { \"enableGlobalFeePayer\": false } } # Error Code This section contains the errors that might occur when using the KIP-17 API. KAS uses HTTP status codes. More details can be found in this link.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-7 API

Introduction The KIP-17 API helps BApp (Blockchain Application) developers to manage contracts and tokens created in accordance with the KIP-7 standard, which is Klaytn's technical speficication for Fungible Tokens. The functionality of the multiple endpoints enables you to do the following actions: - deploy smart contracts - manage the entire life cycle of an FT from minting, to sending and burning - get contract or token data - authorize a third party to execute token transfers - send tokens on behalf of the owner For more details on KAS, please refer to KAS Docs. If you have any questions or comments, please leave them in the Klaytn Developers Forum. alias When a method of the KIP-17 API requires a contract address, you can use the contract alias. You can give the contract an alias when deploying, and use it in place of the complicated address. deployer When you create a contract, you will be assigned one deployer address per Credential, which is the account address used for managing contracts. In KIP-7 API, this address is used in many different token-related operations. You can find the deployer address with KIP7Deployer. Even with contracts created using SDKs like "caver", you can still use the contract address and Wallet API account to manage your contracts and tokens. # Fee Payer Options KAS KIP-17 supports four ways to pay the transaction fees.
1. Only using KAS Global FeePayer Account
Sends all transactions using KAS Global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer Account
Sends all transactions using User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account
Sends transactions using User FeePayer Account by default, and switches to the KAS Global FeePayer Account when balances are insufficient. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account
Sends transactions the default way, paying the transaction fee from the user's account. { \"options\": { \"enableGlobalFeePayer\": false } } # Error Code This section contains the errors that might occur when using the KIP-17 API. KAS uses HTTP status codes. More details can be found in this link.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-7 API

Introduction The KIP-17 API helps BApp (Blockchain Application) developers to manage contracts and tokens created in accordance with the KIP-7 standard, which is Klaytn's technical speficication for Fungible Tokens. The functionality of the multiple endpoints enables you to do the following actions: - deploy smart contracts - manage the entire life cycle of an FT from minting, to sending and burning - get contract or token data - authorize a third party to execute token transfers - send tokens on behalf of the owner For more details on KAS, please refer to KAS Docs. If you have any questions or comments, please leave them in the Klaytn Developers Forum. alias When a method of the KIP-17 API requires a contract address, you can use the contract alias. You can give the contract an alias when deploying, and use it in place of the complicated address. deployer When you create a contract, you will be assigned one deployer address per Credential, which is the account address used for managing contracts. In KIP-7 API, this address is used in many different token-related operations. You can find the deployer address with KIP7Deployer. Even with contracts created using SDKs like "caver", you can still use the contract address and Wallet API account to manage your contracts and tokens. # Fee Payer Options KAS KIP-17 supports four ways to pay the transaction fees.
1. Only using KAS Global FeePayer Account
Sends all transactions using KAS Global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer Account
Sends all transactions using User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account
Sends transactions using User FeePayer Account by default, and switches to the KAS Global FeePayer Account when balances are insufficient. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account
Sends transactions the default way, paying the transaction fee from the user's account. { \"options\": { \"enableGlobalFeePayer\": false } } # Error Code This section contains the errors that might occur when using the KIP-17 API. KAS uses HTTP status codes. More details can be found in this link.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-7 API

Introduction The KIP-17 API helps BApp (Blockchain Application) developers to manage contracts and tokens created in accordance with the KIP-7 standard, which is Klaytn's technical speficication for Fungible Tokens. The functionality of the multiple endpoints enables you to do the following actions: - deploy smart contracts - manage the entire life cycle of an FT from minting, to sending and burning - get contract or token data - authorize a third party to execute token transfers - send tokens on behalf of the owner For more details on KAS, please refer to KAS Docs. If you have any questions or comments, please leave them in the Klaytn Developers Forum. alias When a method of the KIP-17 API requires a contract address, you can use the contract alias. You can give the contract an alias when deploying, and use it in place of the complicated address. deployer When you create a contract, you will be assigned one deployer address per Credential, which is the account address used for managing contracts. In KIP-7 API, this address is used in many different token-related operations. You can find the deployer address with KIP7Deployer. Even with contracts created using SDKs like "caver", you can still use the contract address and Wallet API account to manage your contracts and tokens. # Fee Payer Options KAS KIP-17 supports four ways to pay the transaction fees.
1. Only using KAS Global FeePayer Account
Sends all transactions using KAS Global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer Account
Sends all transactions using User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account
Sends transactions using User FeePayer Account by default, and switches to the KAS Global FeePayer Account when balances are insufficient. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account
Sends transactions the default way, paying the transaction fee from the user's account. { \"options\": { \"enableGlobalFeePayer\": false } } # Error Code This section contains the errors that might occur when using the KIP-17 API. KAS uses HTTP status codes. More details can be found in this link.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-7 API

Introduction The KIP-17 API helps BApp (Blockchain Application) developers to manage contracts and tokens created in accordance with the KIP-7 standard, which is Klaytn's technical speficication for Fungible Tokens. The functionality of the multiple endpoints enables you to do the following actions: - deploy smart contracts - manage the entire life cycle of an FT from minting, to sending and burning - get contract or token data - authorize a third party to execute token transfers - send tokens on behalf of the owner For more details on KAS, please refer to KAS Docs. If you have any questions or comments, please leave them in the Klaytn Developers Forum. alias When a method of the KIP-17 API requires a contract address, you can use the contract alias. You can give the contract an alias when deploying, and use it in place of the complicated address. deployer When you create a contract, you will be assigned one deployer address per Credential, which is the account address used for managing contracts. In KIP-7 API, this address is used in many different token-related operations. You can find the deployer address with KIP7Deployer. Even with contracts created using SDKs like "caver", you can still use the contract address and Wallet API account to manage your contracts and tokens. # Fee Payer Options KAS KIP-17 supports four ways to pay the transaction fees.
1. Only using KAS Global FeePayer Account
Sends all transactions using KAS Global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer Account
Sends all transactions using User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account
Sends transactions using User FeePayer Account by default, and switches to the KAS Global FeePayer Account when balances are insufficient. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account
Sends transactions the default way, paying the transaction fee from the user's account. { \"options\": { \"enableGlobalFeePayer\": false } } # Error Code This section contains the errors that might occur when using the KIP-17 API. KAS uses HTTP status codes. More details can be found in this link.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

KIP-7 API

Introduction The KIP-17 API helps BApp (Blockchain Application) developers to manage contracts and tokens created in accordance with the KIP-7 standard, which is Klaytn's technical speficication for Fungible Tokens. The functionality of the multiple endpoints enables you to do the following actions: - deploy smart contracts - manage the entire life cycle of an FT from minting, to sending and burning - get contract or token data - authorize a third party to execute token transfers - send tokens on behalf of the owner For more details on KAS, please refer to KAS Docs. If you have any questions or comments, please leave them in the Klaytn Developers Forum. alias When a method of the KIP-17 API requires a contract address, you can use the contract alias. You can give the contract an alias when deploying, and use it in place of the complicated address. deployer When you create a contract, you will be assigned one deployer address per Credential, which is the account address used for managing contracts. In KIP-7 API, this address is used in many different token-related operations. You can find the deployer address with KIP7Deployer. Even with contracts created using SDKs like "caver", you can still use the contract address and Wallet API account to manage your contracts and tokens. # Fee Payer Options KAS KIP-17 supports four ways to pay the transaction fees.
1. Only using KAS Global FeePayer Account
Sends all transactions using KAS Global FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": true } }
2. Using User FeePayer Account
Sends all transactions using User FeePayer Account. { \"options\": { \"enableGlobalFeePayer\": false, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
3. Using both KAS Global FeePayer Account + User FeePayer Account
Sends transactions using User FeePayer Account by default, and switches to the KAS Global FeePayer Account when balances are insufficient. { \"options\": { \"enableGlobalFeePayer\": true, \"userFeePayer\": { \"krn\": \"krn:1001:wallet:20bab367-141b-439a-8b4c-ae8788b86316:feepayer-pool:default\", \"address\": \"0xd6905b98E4Ba43a24E842d2b66c1410173791cab\" } } }
4. Not using FeePayer Account
Sends transactions the default way, paying the transaction fee from the user's account. { \"options\": { \"enableGlobalFeePayer\": false } } # Error Code This section contains the errors that might occur when using the KIP-17 API. KAS uses HTTP status codes. More details can be found in this link.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Token History API

Introduction Token History API allows you to query the transaction history of KLAY, FTs (KIP-7 and Labelled ERC-20), NFTs (KIP-17 and Labelled ERC-721), and MTs (KIP-37 and Labelled ERC-1155). You can track KLAY's transaction history or retrieve NFT-related data of a certain EOA. For more details on using Token History API, please refer to the Tutorial. For any inquiries on this document or KAS in general, please visit Developer Forum.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Token History API

Introduction Token History API allows you to query the transaction history of KLAY, FTs (KIP-7 and Labelled ERC-20), NFTs (KIP-17 and Labelled ERC-721), and MTs (KIP-37 and Labelled ERC-1155). You can track KLAY's transaction history or retrieve NFT-related data of a certain EOA. For more details on using Token History API, please refer to the Tutorial. For any inquiries on this document or KAS in general, please visit Developer Forum.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Token History API

Introduction Token History API allows you to query the transaction history of KLAY, FTs (KIP-7 and Labelled ERC-20), NFTs (KIP-17 and Labelled ERC-721), and MTs (KIP-37 and Labelled ERC-1155). You can track KLAY's transaction history or retrieve NFT-related data of a certain EOA. For more details on using Token History API, please refer to the Tutorial. For any inquiries on this document or KAS in general, please visit Developer Forum.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Token History API

Introduction Token History API allows you to query the transaction history of KLAY, FTs (KIP-7 and Labelled ERC-20), NFTs (KIP-17 and Labelled ERC-721), and MTs (KIP-37 and Labelled ERC-1155). You can track KLAY's transaction history or retrieve NFT-related data of a certain EOA. For more details on using Token History API, please refer to the Tutorial. For any inquiries on this document or KAS in general, please visit Developer Forum.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Token History API

Introduction Token History API allows you to query the transaction history of KLAY, FTs (KIP-7 and Labelled ERC-20), NFTs (KIP-17 and Labelled ERC-721), and MTs (KIP-37 and Labelled ERC-1155). You can track KLAY's transaction history or retrieve NFT-related data of a certain EOA. For more details on using Token History API, please refer to the Tutorial. For any inquiries on this document or KAS in general, please visit Developer Forum.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Token History API

Introduction Token History API allows you to query the transaction history of KLAY, FTs (KIP-7 and Labelled ERC-20), NFTs (KIP-17 and Labelled ERC-721), and MTs (KIP-37 and Labelled ERC-1155). You can track KLAY's transaction history or retrieve NFT-related data of a certain EOA. For more details on using Token History API, please refer to the Tutorial. For any inquiries on this document or KAS in general, please visit Developer Forum.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Token History API

Introduction Token History API allows you to query the transaction history of KLAY, FTs (KIP-7 and Labelled ERC-20), NFTs (KIP-17 and Labelled ERC-721), and MTs (KIP-37 and Labelled ERC-1155). You can track KLAY's transaction history or retrieve NFT-related data of a certain EOA. For more details on using Token History API, please refer to the Tutorial. For any inquiries on this document or KAS in general, please visit Developer Forum.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Token History API

Introduction Token History API allows you to query the transaction history of KLAY, FTs (KIP-7 and Labelled ERC-20), NFTs (KIP-17 and Labelled ERC-721), and MTs (KIP-37 and Labelled ERC-1155). You can track KLAY's transaction history or retrieve NFT-related data of a certain EOA. For more details on using Token History API, please refer to the Tutorial. For any inquiries on this document or KAS in general, please visit Developer Forum.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Token History API

Introduction Token History API allows you to query the transaction history of KLAY, FTs (KIP-7 and Labelled ERC-20), NFTs (KIP-17 and Labelled ERC-721), and MTs (KIP-37 and Labelled ERC-1155). You can track KLAY's transaction history or retrieve NFT-related data of a certain EOA. For more details on using Token History API, please refer to the Tutorial. For any inquiries on this document or KAS in general, please visit Developer Forum.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Token History API

Introduction Token History API allows you to query the transaction history of KLAY, FTs (KIP-7 and Labelled ERC-20), NFTs (KIP-17 and Labelled ERC-721), and MTs (KIP-37 and Labelled ERC-1155). You can track KLAY's transaction history or retrieve NFT-related data of a certain EOA. For more details on using Token History API, please refer to the Tutorial. For any inquiries on this document or KAS in general, please visit Developer Forum.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Token History API

Introduction Token History API allows you to query the transaction history of KLAY, FTs (KIP-7 and Labelled ERC-20), NFTs (KIP-17 and Labelled ERC-721), and MTs (KIP-37 and Labelled ERC-1155). You can track KLAY's transaction history or retrieve NFT-related data of a certain EOA. For more details on using Token History API, please refer to the Tutorial. For any inquiries on this document or KAS in general, please visit Developer Forum.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Token History API

Introduction Token History API allows you to query the transaction history of KLAY, FTs (KIP-7 and Labelled ERC-20), NFTs (KIP-17 and Labelled ERC-721), and MTs (KIP-37 and Labelled ERC-1155). You can track KLAY's transaction history or retrieve NFT-related data of a certain EOA. For more details on using Token History API, please refer to the Tutorial. For any inquiries on this document or KAS in general, please visit Developer Forum.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Token History API

Introduction Token History API allows you to query the transaction history of KLAY, FTs (KIP-7 and Labelled ERC-20), NFTs (KIP-17 and Labelled ERC-721), and MTs (KIP-37 and Labelled ERC-1155). You can track KLAY's transaction history or retrieve NFT-related data of a certain EOA. For more details on using Token History API, please refer to the Tutorial. For any inquiries on this document or KAS in general, please visit Developer Forum.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Token History API

Introduction Token History API allows you to query the transaction history of KLAY, FTs (KIP-7 and Labelled ERC-20), NFTs (KIP-17 and Labelled ERC-721), and MTs (KIP-37 and Labelled ERC-1155). You can track KLAY's transaction history or retrieve NFT-related data of a certain EOA. For more details on using Token History API, please refer to the Tutorial. For any inquiries on this document or KAS in general, please visit Developer Forum.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Token History API

Introduction Token History API allows you to query the transaction history of KLAY, FTs (KIP-7 and Labelled ERC-20), NFTs (KIP-17 and Labelled ERC-721), and MTs (KIP-37 and Labelled ERC-1155). You can track KLAY's transaction history or retrieve NFT-related data of a certain EOA. For more details on using Token History API, please refer to the Tutorial. For any inquiries on this document or KAS in general, please visit Developer Forum.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Token History API

Introduction Token History API allows you to query the transaction history of KLAY, FTs (KIP-7 and Labelled ERC-20), NFTs (KIP-17 and Labelled ERC-721), and MTs (KIP-37 and Labelled ERC-1155). You can track KLAY's transaction history or retrieve NFT-related data of a certain EOA. For more details on using Token History API, please refer to the Tutorial. For any inquiries on this document or KAS in general, please visit Developer Forum.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Token History API

Introduction Token History API allows you to query the transaction history of KLAY, FTs (KIP-7 and Labelled ERC-20), NFTs (KIP-17 and Labelled ERC-721), and MTs (KIP-37 and Labelled ERC-1155). You can track KLAY's transaction history or retrieve NFT-related data of a certain EOA. For more details on using Token History API, please refer to the Tutorial. For any inquiries on this document or KAS in general, please visit Developer Forum.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Token History API

Introduction Token History API allows you to query the transaction history of KLAY, FTs (KIP-7 and Labelled ERC-20), NFTs (KIP-17 and Labelled ERC-721), and MTs (KIP-37 and Labelled ERC-1155). You can track KLAY's transaction history or retrieve NFT-related data of a certain EOA. For more details on using Token History API, please refer to the Tutorial. For any inquiries on this document or KAS in general, please visit Developer Forum.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Token History API

Introduction Token History API allows you to query the transaction history of KLAY, FTs (KIP-7 and Labelled ERC-20), NFTs (KIP-17 and Labelled ERC-721), and MTs (KIP-37 and Labelled ERC-1155). You can track KLAY's transaction history or retrieve NFT-related data of a certain EOA. For more details on using Token History API, please refer to the Tutorial. For any inquiries on this document or KAS in general, please visit Developer Forum.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Token History API

Introduction Token History API allows you to query the transaction history of KLAY, FTs (KIP-7 and Labelled ERC-20), NFTs (KIP-17 and Labelled ERC-721), and MTs (KIP-37 and Labelled ERC-1155). You can track KLAY's transaction history or retrieve NFT-related data of a certain EOA. For more details on using Token History API, please refer to the Tutorial. For any inquiries on this document or KAS in general, please visit Developer Forum.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Token History API

Introduction Token History API allows you to query the transaction history of KLAY, FTs (KIP-7 and Labelled ERC-20), NFTs (KIP-17 and Labelled ERC-721), and MTs (KIP-37 and Labelled ERC-1155). You can track KLAY's transaction history or retrieve NFT-related data of a certain EOA. For more details on using Token History API, please refer to the Tutorial. For any inquiries on this document or KAS in general, please visit Developer Forum.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Token History API

Introduction Token History API allows you to query the transaction history of KLAY, FTs (KIP-7 and Labelled ERC-20), NFTs (KIP-17 and Labelled ERC-721), and MTs (KIP-37 and Labelled ERC-1155). You can track KLAY's transaction history or retrieve NFT-related data of a certain EOA. For more details on using Token History API, please refer to the Tutorial. For any inquiries on this document or KAS in general, please visit Developer Forum.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Token History API

Introduction Token History API allows you to query the transaction history of KLAY, FTs (KIP-7 and Labelled ERC-20), NFTs (KIP-17 and Labelled ERC-721), and MTs (KIP-37 and Labelled ERC-1155). You can track KLAY's transaction history or retrieve NFT-related data of a certain EOA. For more details on using Token History API, please refer to the Tutorial. For any inquiries on this document or KAS in general, please visit Developer Forum.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Token History API

Introduction Token History API allows you to query the transaction history of KLAY, FTs (KIP-7 and Labelled ERC-20), NFTs (KIP-17 and Labelled ERC-721), and MTs (KIP-37 and Labelled ERC-1155). You can track KLAY's transaction history or retrieve NFT-related data of a certain EOA. For more details on using Token History API, please refer to the Tutorial. For any inquiries on this document or KAS in general, please visit Developer Forum.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Token History API

Introduction Token History API allows you to query the transaction history of KLAY, FTs (KIP-7 and Labelled ERC-20), NFTs (KIP-17 and Labelled ERC-721), and MTs (KIP-37 and Labelled ERC-1155). You can track KLAY's transaction history or retrieve NFT-related data of a certain EOA. For more details on using Token History API, please refer to the Tutorial. For any inquiries on this document or KAS in general, please visit Developer Forum.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Token History API

Introduction Token History API allows you to query the transaction history of KLAY, FTs (KIP-7 and Labelled ERC-20), NFTs (KIP-17 and Labelled ERC-721), and MTs (KIP-37 and Labelled ERC-1155). You can track KLAY's transaction history or retrieve NFT-related data of a certain EOA. For more details on using Token History API, please refer to the Tutorial. For any inquiries on this document or KAS in general, please visit Developer Forum.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Token History API

Introduction Token History API allows you to query the transaction history of KLAY, FTs (KIP-7 and Labelled ERC-20), NFTs (KIP-17 and Labelled ERC-721), and MTs (KIP-37 and Labelled ERC-1155). You can track KLAY's transaction history or retrieve NFT-related data of a certain EOA. For more details on using Token History API, please refer to the Tutorial. For any inquiries on this document or KAS in general, please visit Developer Forum.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Token History API

Introduction Token History API allows you to query the transaction history of KLAY, FTs (KIP-7 and Labelled ERC-20), NFTs (KIP-17 and Labelled ERC-721), and MTs (KIP-37 and Labelled ERC-1155). You can track KLAY's transaction history or retrieve NFT-related data of a certain EOA. For more details on using Token History API, please refer to the Tutorial. For any inquiries on this document or KAS in general, please visit Developer Forum.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Token History API

Introduction Token History API allows you to query the transaction history of KLAY, FTs (KIP-7 and Labelled ERC-20), NFTs (KIP-17 and Labelled ERC-721), and MTs (KIP-37 and Labelled ERC-1155). You can track KLAY's transaction history or retrieve NFT-related data of a certain EOA. For more details on using Token History API, please refer to the Tutorial. For any inquiries on this document or KAS in general, please visit Developer Forum.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Token History API

Introduction Token History API allows you to query the transaction history of KLAY, FTs (KIP-7 and Labelled ERC-20), NFTs (KIP-17 and Labelled ERC-721), and MTs (KIP-37 and Labelled ERC-1155). You can track KLAY's transaction history or retrieve NFT-related data of a certain EOA. For more details on using Token History API, please refer to the Tutorial. For any inquiries on this document or KAS in general, please visit Developer Forum.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Token History API

Introduction Token History API allows you to query the transaction history of KLAY, FTs (KIP-7 and Labelled ERC-20), NFTs (KIP-17 and Labelled ERC-721), and MTs (KIP-37 and Labelled ERC-1155). You can track KLAY's transaction history or retrieve NFT-related data of a certain EOA. For more details on using Token History API, please refer to the Tutorial. For any inquiries on this document or KAS in general, please visit Developer Forum.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Token History API

Introduction Token History API allows you to query the transaction history of KLAY, FTs (KIP-7 and Labelled ERC-20), NFTs (KIP-17 and Labelled ERC-721), and MTs (KIP-37 and Labelled ERC-1155). You can track KLAY's transaction history or retrieve NFT-related data of a certain EOA. For more details on using Token History API, please refer to the Tutorial. For any inquiries on this document or KAS in general, please visit Developer Forum.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Token History API

Introduction Token History API allows you to query the transaction history of KLAY, FTs (KIP-7 and Labelled ERC-20), NFTs (KIP-17 and Labelled ERC-721), and MTs (KIP-37 and Labelled ERC-1155). You can track KLAY's transaction history or retrieve NFT-related data of a certain EOA. For more details on using Token History API, please refer to the Tutorial. For any inquiries on this document or KAS in general, please visit Developer Forum.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Token History API

Introduction Token History API allows you to query the transaction history of KLAY, FTs (KIP-7 and Labelled ERC-20), NFTs (KIP-17 and Labelled ERC-721), and MTs (KIP-37 and Labelled ERC-1155). You can track KLAY's transaction history or retrieve NFT-related data of a certain EOA. For more details on using Token History API, please refer to the Tutorial. For any inquiries on this document or KAS in general, please visit Developer Forum.

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

Wallet API

Introduction Wallet API is an API for creating and managing Klaytn accounts as well as sending transactions. If you create your Klaytn account using Wallet API, you don't have to manage your private key yourself. Wallet API provides a wallet for safe storage of your Klaytn account private keys that you would need to use BApps. For more details on how to use Wallet API, please refer to this tutorial. Wallet API can be divided into the Account part, which creates and manages Klaytn accounts, and the Transaction part, which sends different kinds of transactions. Wallet API creates, deletes and monitors Klaytn accounts and updates the accounts to multisig, and manages all private keys for all accounts registered on KAS. Wallet API can also create transaction to send it to Klaytn. These include transactions sent from multisig accounts. In case of muiltisig accounts, a transaction will automatically be sent to Klaytn once \(Threshold\) is met. For more detail, please refer to this tutorial. There are mainly two types of transactions: basic transactions and fee delegation transactions. Fee delegation transactions include Global Fee Delegation transaction and user fee deletation transaction. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users when a transaction. The functionalities and limits of Wallet API are shown below: | Version | Item | Description | | :--- | :--- | :--- | | 2.0 | Limits | Supports Cypress(Mainnet), Baobab(Testnet) \ Doesn't support (Service Chain \) | | | | Doesn't support account management for external custodial keys | | | | Doesn't support multisig for RLP encoded transactions | | | Account management | Create, retrieve and delete account | | | | Multisig account update | | | Managing transaction | Basic creating and sending transaction | | | | FeeDelegatedWithRatio creating and sending transaction | | | | RLP encoded transaction\(Legacy, Basic, FeeDelegatedWithRatio\) creating and sending | | | | Managing and sending multisig transactions | | | Administrator | Manage resource pool\(create, query pool, delete, retrieve account \) |

OpenAPI spec version: 1.0

NOTE: This class is auto generated by the swagger code generator program. https://github.com/swagger-api/swagger-codegen.git Do not edit the class manually.

SinglePrivateKey presents a single private key such as account types of a legacy key or public key.

MutisigPrivateKeys presents a set of private keys of weighted multisig key account type.

RoleBasedPrivateKeys presents a set of private keys of role based account type. Additionally, each private key can contains multiple private keys for multisig account type.

MigrationAccount presents an account to be migrated. Each account can have one of three types of keys.

RegisterAccount presents an account to be registered in KAS Wallet API.