Bookmap forum

Hi,

Just wanted to let you know that we haven't forgotten to respond to you. We are still considering which approach to recommend.

Hi,

We stopped supporting the Trading Technologies adapter because too few users were using it, so the price of support was deemed too high.

Could you please clarify what do you mean by "Can the adapter be re worked through the API connection service?"

Hi,

Sorry for the delayed response. We are aware of the issues with Multibook and just recently introduced some improvements to our servers.

Please check if any issues are still present for Multibook on your side.

Hi,

We have updated the integration to support the case when secret key has "\n" as two separate symbols. It should now be possible to copy and paste the key from browser or text editor without the issue.

Yes, please reach out to support regarding this at [email protected]. We will need to see log files to investigate the issue, support is going to be able to assist you on where to find them. Feel free to attach this forum thread as a point of reference.

The new line symbols "\n" should be copied as is. There is a possibility that file interpreter that you are using is copying those as separate symbols "\" and "n". If that is the case, you can create a text file, manually replace "\n" symbols with new lines and then copy-paste the result. Also, we w...

Hi, Yes, you should copy/paste the whole "name" as API key and whole "privateKey" as API secret. These fields are present in the "coinbase_cloud_api_key.json" file that Coinbase downloads automatically when you create a new API key. Also, if you have provided a real Private key in the example, pleas...

Hi,

The integration has been fixed. It should now work with both old and new API keys.

Hi,

Thank you for the report.

I checked the connectivity with new API Key and it doesn't work, so we indeed need to update our Coinbase integration in order to be compatible with new API Keys.

We will update our integration and post a reply here when it's done.