Conditional Close with different pairs about python3-krakenex HOT 4 CLOSED

Either I didn't sufficiently test the example when putting it in the repo, or the API changed on Kraken's side without a version bump.

I've also noticed (a few months ago) that some close[...] attributes have no effect - close[volume], I think?..

from python3-krakenex.

Do you have a workaround in mind?

from python3-krakenex.

I don't think there can be a workaround, other than running a monitoring bot.

Below somewhat OT.

Kraken's API docs currently lists these as possible:

optional closing order to add to system when order gets filled:
close[ordertype] = order type
close[price] = price
close[price2] = secondary price

The Wayback Machine suggests that it never really did list anything else.

It could be that Kraken decided to limit what fields are acceptable here, and ignore the rest.

Again, I'm not sure if it ever accepted anything else. The fact that examples/conditional-close.py has shown more fields, ever since it was added in commit 15dd9ee tends to suggest that it did, or that I'm delusional.

I do remember testing that example with a live market order, though...

from python3-krakenex.

So, Kraken replied.

Hello there,

I did some more digging and it turns out we do not allow separate pairs beyond the base pairs for conditional close orders. Sorry I don't have better news.

from python3-krakenex.