WAX Kit Smart Contract icon

WAX Kit Smart Contract

Execute actions on WAX smart contracts

Actions2

Execute Action

AI-generated

Summary

Signs and broadcasts a single smart contract action transaction on the WAX blockchain using the private key from the waxKitPrivateKeyApi credential, and returns the transaction id and processed result.

Inputs

  • Contract Name (required) — Account name of the contract that owns the action (e.g. eosio.token, atomicassets).
  • Action Name (required) — Name of the contract action to execute.
  • Action Data (required) — JSON object with the action's arguments. A string is parsed as JSON; invalid JSON raises an error for that item.
  • Authorization — Multiple entries of actor plus permission (Active, Owner, or Custom with a custom permission name). If none are given, the credential's account is used as actor with 'active' permission.
  • API Endpoint (required) — WAX RPC endpoint URL used to build and push the transaction. Defaults to https://wax.greymass.com.
  • Memo (Optional) — Optional text echoed back in the node output only. It is not added to the action data or the transaction, so put an on-chain memo in Action Data.

Output shape

One output item per input item. It contains success: true, operation, contract, action, actionData, authorization (the list actually used), memo, and a transaction object with transaction_id and processed.

The transaction is signed with the credential's private key, uses blocksBehind 3 and expires after 30 seconds. If the library returns an unrecognized result shape, transaction contains the raw result plus a note instead. With Continue On Fail enabled, a failed item returns success: false, error, and details. Otherwise the node throws. A license check runs before execution.

Examples

Example 1: Transfer WAX tokens to another account

Contract Name: eosio.token; Action Name: transfer; Action Data: {"from":"myaccount","to":"friend","quantity":"1.00000000 WAX","memo":"hi"}; leave Authorization empty to use the credential account with active permission.

Example 2: Run an action with a custom permission

Contract Name: mycontract; Action Name: doit; Action Data: {"id":5}; Authorization: actor myaccount, permission Custom, custom permission 'bot'.

Links

Discussion