This is a very good question. I think it may be under `transfers`. I am looking into it now.

I've just re-run the script, and it looks like I missed 1 operation type :
```
=====> set_withdraw_vesting_route
{'auto_vest': False,
 'from_account': 'steemroller',
 'percent': 100,
 'to_account': 'itsascam'}
```

Ok, I tried exchanging $0.26 SBD into steem and back, and this is the only thing I got from the blockchain:

Buying Steem:
```
=====> limit_order_create
{'amount_to_sell': '0.286 SBD',
 'expiration': '1969-12-31T23:59:59',
 'fill_or_kill': False,
 'min_to_receive': '0.100 STEEM',
 'orderid': 1470060094,
 'owner': 'furion'}
```

Selling Steem:
```
=====> limit_order_create
{'amount_to_sell': '0.100 STEEM',
 'expiration': '1969-12-31T23:59:59',
 'fill_or_kill': False,
 'min_to_receive': '0.274 SBD',
 'orderid': 1470060340,
 'owner': 'furion'}
```

So I dug deeper, and I found out, that `steemd` does not handle exchange data.

To get the exchange data, one needs to to interact with `cli_wallet`'s RPC, not the `steemd`. 
If you use [python-steemlib](https://github.com/xeroc/python-steemlib), the trade history can be obtained like so:
```
class Config():
                wallet_host           = "localhost"
                wallet_port           = 8091
                witness_url           = "wss://steemit.com/wstmp2"
                account = "smooth"

wallet_rpc = SteemExchange(Config)
wallet_rpc.returnTradeHistory()
```

there is a fill_order event in the array returned by get_history:     
 sprintf(url,"http://127.0.0.1:8090");
    sprintf(params,"{\"id\":%llu,\"method\":\"get_account_history\",\"params\":[\"%s\", %d, %d]}",

     fill_order ({"current_owner":"enki","current_orderid":3402053187,"current_pays":"19.613 SBD","open_owner":"taker","open_orderid":1469136521,"open_pays":"5.792 STEEM"})
it shows both orderids and how much was filled

Account history for an account has virtual operations for orders filled by that account. Currently the only way to see virtual ops is in account history, but I'm thinking of adding an event interface for them one of these days and writing a plugin to expose them over an API.