get_action_traces

Retrieve a stream of actions, filtered by receiver and account

Usage

Example request:

{
  "type": "get_action_traces",
  "listen": true,
  "req_id": "your-request-id",
  "irreversible_only": true,
  "data": {
    "accounts": "eosio.token",
    "action_name": "transfer",
    "with_inline_traces": true,
    "with_dtrxops": true,
    "with_ramops": true
  }
}

Information about receiver, account and action_name

Actions on the EOS blockchain are identified by a triplet receiver/account/action_name * The code on the receiver is called with the method account/action_name * An action is considered a “notification” when the receiver is different from the account field. That receiver may or may not contain instructions to run for that account/action_name pair. Read more details here.

Arguments

accounts
required
String .  Pipe | separated list of accounts to match.
action_names
Optional
String .  Pipe | separated list of actions to match.
receivers
Optional
String .  Defaults to the same value as accounts. Pipe | separated list of receivers to match.
with_ramops
Optional
Boolean .  Stream RAM billing changes and reasons for costs of storage produced by each action (See RAMOp).
with_tableops
Optional
Boolean .  Stream table operations produced by each action (See TableOp).
with_inline_traces
Optional
Boolean .  Stream the inline actions produced by each action.
with_dtrxops
Optional
Boolean .  Stream the modifications to deferred transactions produced by each action (See DTrxOp).

Responses

  • fetch: true is not supported for get_action_traces
  • listen: true requests will stream ActionTrace objects.
  • irreversible_only: true ensure that you only get actions from irreversible blocks. If you call it with start_block: (current head block), you will have to wait until that block becomes irreversible before you see any data streaming back.