Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WebSocket v2 - fundChange type always "Deposit" #205

Open
simbesh opened this issue Apr 14, 2023 · 8 comments
Open

WebSocket v2 - fundChange type always "Deposit" #205

simbesh opened this issue Apr 14, 2023 · 8 comments

Comments

@simbesh
Copy link

simbesh commented Apr 14, 2023

While testing the fundChange channel, It seems "Deposit" is always sent.

here are some withdrawals I made:

{
    "fundtransferId": 6502310512,
    "type": "Deposit",
    "status": "Pending Authorization",
    "timestamp": "2023-04-14T00:15:16.645Z",
    "messageType": "fundChange",
    "currency": "LTC",
    "amount": "10",
    "fee": "0"
  },
  {
    "fundtransferId": 6502310496,
    "type": "Deposit",
    "status": "Pending Authorization",
    "timestamp": "2023-04-13T23:52:55.622Z",
    "messageType": "fundChange",
    "currency": "LTC",
    "amount": "63.14840715",
    "fee": "0"
  }

image

As you can see the type looks incorrect.

@martin-nginio
Copy link
Contributor

Hi @simbesh @MediVik333

Thanks for reporting this issue and sorry for not responding earlier.

This is correct and has been added to our roadmap for next update of the WebSocket API.

@martin-nginio
Copy link
Contributor

In the meantime and as a workaround and if you are interested in getting more data (or at least correct transfer type) for the after receiving the WebSocket fundChange event, please call the following Rest API in order to get a list of recent transfers that you can compare with the transferId arrived with the event:
https://docs.btcmarkets.net/#tag/Fund-Management-APIs/paths/~1v3~1transfers/get

Thanks.

@martin-nginio
Copy link
Contributor

Hi @simbesh @MediVik333

This issue has been fixed today.

If you can please take a look and let us know if you are still observing the same issue.

Thanks for your feedback again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants
@simbesh @martin-nginio and others