LLM Notice: This documentation site supports content negotiation for AI agents. Request any page with Accept: text/markdown or Accept: text/plain header to receive Markdown instead of HTML. Alternatively, append ?format=md to any URL. All markdown files are available at /md/ prefix paths. For all content in one file, visit /llms-full.txt
Skip to main content

Send a Transaction

The Flow CLI provides a command to sign and send transactions to any Flow Access API.


_10
flow transactions send <code filename> [<argument> <argument>...] [flags]

Example use​


_22
> flow transactions send ./tx.cdc "Hello"
_22
_22
Status ✅ SEALED
_22
ID b04b6bcc3164f5ee6b77fa502c3a682e0db57fc47e5b8a8ef3b56aae50ad49c8
_22
Payer f8d6e0586b0a20c7
_22
Authorizers [f8d6e0586b0a20c7]
_22
_22
Proposal Key:
_22
Address f8d6e0586b0a20c7
_22
Index 0
_22
Sequence 0
_22
_22
No Payload Signatures
_22
_22
Envelope Signature 0: f8d6e0586b0a20c7
_22
Signatures (minimized, use --include signatures)
_22
_22
Events: None
_22
_22
Code (hidden, use --include code)
_22
_22
Payload (hidden, use --include payload)

Multiple arguments example:


_10
> flow transactions send tx1.cdc Foo 1 2 10.9 0x1 '[123,222]' '["a","b"]'

Transaction code:


_10
transaction(a: String, b: Int, c: UInt16, d: UFix64, e: Address, f: [Int], g: [String]) {
_10
prepare(authorizer: &Account) {}
_10
}

In the above example, the flow.json file would look something like this:


_10
{
_10
"accounts": {
_10
"my-testnet-account": {
_10
"address": "a2c4941b5f3c7151",
_10
"key": "12c5dfde...bb2e542f1af710bd1d40b2"
_10
}
_10
}
_10
}

JSON arguments from a file example:


_10
> flow transactions send tx1.cdc --args-json "$(cat args.json)"

Arguments​

Code filename​

  • Name: code filename
  • Valid inputs: Any filename and path valid on the system.

The first argument is a path to a Cadence file that contains the transaction to be executed.

Arguments​

  • Name: argument
  • Valid inputs: valid cadence values that matches the argument type in transaction code.

Input arguments values that match types which correspond in the source code and passed in the same order. to can pass a nil value to optional arguments, send the transaction like this: flow transactions send tx.cdc nil.

Flags​

Include fields​

  • Flag: --include
  • Valid inputs: code, payload

Specify fields to include in the result output. Applies only to the text output.

Code​

  • Flag: --code

⚠️ No longer supported: use filename argument.

Results​

  • Flag: --results

⚠️ No longer supported: all transactions will provide result.

Exclude fields​

  • Flag: --exclude
  • Valid inputs: events

Specify fields to exclude from the result output. Applies only to the text output.

Signer​

  • Flag: --signer
  • Valid inputs: the name of an account defined in the configuration (flow.json).

Specify the name of the account that will be used to sign the transaction.

Proposer​

  • Flag: --proposer
  • Valid inputs: the name of an account defined in the configuration (flow.json)

Specify the name of the account that will be used as the proposer in the transaction.

Payer​

  • Flag: --payer
  • Valid inputs: the name of an account defined in the configuration (flow.json)

Specify the name of the account that will be used as the payer in the transaction.

Authorizer​

  • Flag: --authorizer
  • Valid inputs: the name of a single or multiple comma-separated accounts defined in the configuration (flow.json)

Specify the name of the account(s) that will be used as authorizer(s) in the transaction. If you want to provide multiple authorizers, separate them with commas (for example, alice,bob)

Arguments JSON​

  • Flag: --args-json
  • Valid inputs: arguments in JSON-Cadence form.
  • Example: flow transactions send ./tx.cdc '[{"type": "String", "value": "Hello World"}]'

Arguments passed to the Cadence transaction in Cadence JSON format. The Cadence JSON format contains type and value keys and is documented here.

Compute Limit​

  • Flag: --compute-limit
  • Valid inputs: an integer greater than zero.
  • Default: 1000

Specify the compute unit (gas) limit for this transaction.

Host​

  • Flag: --host
  • Valid inputs: an IP address or hostname.
  • Default: 127.0.0.1:3569 (Flow Emulator)

Specify the hostname of the Access API that will be used to execute the command. This flag overrides any host defined by the --network flag.

Network key​

  • Flag: --network-key
  • Valid inputs: A valid network public key of the host in hex string format

Specify the network public key of the Access API that will be used to create a secure GRPC client when you execute the command.

Network​

  • Flag: --network
  • Short Flag: -n
  • Valid inputs: the name of a network defined in the configuration (flow.json)
  • Default: emulator

Specify which network you want the command to use for execution.

Filter​

  • Flag: --filter
  • Short Flag: -x
  • Valid inputs: a case-sensitive name of the result property.

Specify any property name from the result you want to return as the only value.

Output​

  • Flag: --output
  • Short Flag: -o
  • Valid inputs: json, inline

Specify the format of the command results.

Save​

  • Flag: --save
  • Short Flag: -s
  • Valid inputs: a path in the current filesystem.

Specify the filename where you want to save the result.

Log​

  • Flag: --log
  • Short Flag: -l
  • Valid inputs: none, error, debug
  • Default: info

Specify the log level. Control how much output you want to see during command execution.

Configuration​

  • Flag: --config-path
  • Short Flag: -f
  • Valid inputs: a path in the current filesystem.
  • Default: flow.json

Specify the path to the flow.json configuration file. You can use the -f flag multiple times to merge several configuration files.

Version check​

  • Flag: --skip-version-check
  • Default: false

Skip version check during start up to speed up process for slow connections.

Rate this page