Deploy Contract

Deploys a new KIP-17 contract with the given parameters. You can find the tutorial for KIP-17 contract deployment here.

Even if you see Submitted in the response, it doesn't mean that the transaction is Committed. To confirm transaction status, use Get Contract List or Get Transaction Receipt from the Wallet API.

Request
Security:
basic
header Parameters
x-chain-id
required
string

Kaia Network Chain ID (1001 or 8217)

Request Body schema: application/json
alias
required
string

The alias of the contract. When using KIP-17 API, you can use the contract alias in place of the address. The alias must only consist of lowercase letters, numbers and hyphens, and the first letter is restricted to a lowercase letter.

symbol
required
string

The contract symbol. It usually consists of 3-4 uppercase letters.

name
required
string

The contract name. It can contain lowercase and uppercase letters, numbers and hyphens.

owner
string

The address available to own the contract. The account creating this contract can be an owner if empty.

object (Kip17FeePayerOptions)
Responses
200

Your request was successful.

400

Your request is not valid.

401

The credential you entered is invalid.

409

There was a conflict with the current state of the server.

post/v2/contract
Request samples
application/json
{
  • "alias": "test",
  • "symbol": "TEST",
  • "name": "TEST NFT",
  • "options": {
    }
}
Response samples
application/json

Your request was successful.

{
  • "status": "Submitted",
  • "transactionHash": "0x0a4f4f97d8a5904721514d60abd3f9ad7938862e415a6c043553a94ab68a5edb",
  • "owner": "0xa809284C83b901eD106Aba4Ccda14628Af128e14",
  • "options": {
    }
}