You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 13, 2023. It is now read-only.
I'm trying to generate deposit address for each account of my exchange website users by using COINEX API I've faced a real problem imagine there is 2 users in my website and USER1 wants to deposit BTC so when he clicks on generate deposit address code runs : PUT /balance/deposit/address/BTC and address displays to him. but he hasn't used this address yet suddenly USER2 wants to deposit BTC too and then code runs again: PUT /balance/deposit/address/BTC but it says { code: 318, data: { }, message: "Deposit address not used." } should USER2 wait untill USER1 completes his deposit?! it can't be like that.. any idea for solving this? how everyone make an exchange with coinex api, it doesn't make a trouble for them?
The text was updated successfully, but these errors were encountered:
Each user should have his own connection by calling const coinex = new Coinex(API_KEY, SECRET);. I'm not sure how you are dealing with multiple users but only one API_KEY and SECRET pair.
`
I'm trying to generate deposit address for each account of my exchange website users by using COINEX API I've faced a real problem imagine there is 2 users in my website and USER1 wants to deposit BTC so when he clicks on generate deposit address code runs : PUT /balance/deposit/address/BTC and address displays to him. but he hasn't used this address yet suddenly USER2 wants to deposit BTC too and then code runs again: PUT /balance/deposit/address/BTC but it says { code: 318, data: { }, message: "Deposit address not used." } should USER2 wait untill USER1 completes his deposit?! it can't be like that.. any idea for solving this? how everyone make an exchange with coinex api, it doesn't make a trouble for them?
The text was updated successfully, but these errors were encountered: