FTX API not working for Quicken
steven.kerns
Member ✭✭
This is the same issue as the "Coinbase API not working for Quicken" post except for FTX.
https://community.quicken.com/discussion/7911926/coinbase-api-not-working-for-quicken
The FTX API Key is 40 characters, but Quicken only allows 32 characters. FTX says 40 characters is the API code standard, but Quicken support refuses to admit that they might have implemented it wrong and won't raise it as an internal issue.
Quicken
1. Add new Account
2. Search for FTX
3. Finds FTX for ftx.us
4. Create API keys in FTX > Settings> API > Create Read-Only API key
5. Enter API key and API secret key into Quicken
6. Unable to enter API secret key because Quicken only allows 32 characters. Both API Key and API Secret are 40 characters.
Quicken doesn't correctly support the key length. I brought this to Quicken Support twice, but they refused to even acknowledge it as an issue. The best response was from "Kimberly" who said FTX was responsible for telling Quicken about their connection parameters, the maximum password length is 16 characters, and it is not within the realm of possibility that Quicken could be implementing a bank's connection instructions incorrectly.
Kimberly refused to create an internal ticket for the issue and told me to go talk to FTX. Which I did. FTX says 40 characters is the API code standard, so it seems that Quicken is obviously in the wrong but refuses to address it.
Is there no way to escalate an issue when Quicken Support is worse than useless?
https://community.quicken.com/discussion/7911926/coinbase-api-not-working-for-quicken
The FTX API Key is 40 characters, but Quicken only allows 32 characters. FTX says 40 characters is the API code standard, but Quicken support refuses to admit that they might have implemented it wrong and won't raise it as an internal issue.
Quicken
1. Add new Account
2. Search for FTX
3. Finds FTX for ftx.us
4. Create API keys in FTX > Settings> API > Create Read-Only API key
5. Enter API key and API secret key into Quicken
6. Unable to enter API secret key because Quicken only allows 32 characters. Both API Key and API Secret are 40 characters.
Quicken doesn't correctly support the key length. I brought this to Quicken Support twice, but they refused to even acknowledge it as an issue. The best response was from "Kimberly" who said FTX was responsible for telling Quicken about their connection parameters, the maximum password length is 16 characters, and it is not within the realm of possibility that Quicken could be implementing a bank's connection instructions incorrectly.
Kimberly refused to create an internal ticket for the issue and told me to go talk to FTX. Which I did. FTX says 40 characters is the API code standard, so it seems that Quicken is obviously in the wrong but refuses to address it.
Is there no way to escalate an issue when Quicken Support is worse than useless?
0
Comments
-
Sounds like you have hit a conflict in protocols. In general, Quicken is programmed to the OFX standard. That is why certain fields are of a certain max size. 32 characters is the max OFX password size.Signature:
This is my website: http://www.quicknperlwiz.com/0 -
*I* didn't hit a conflict in protocols. It would be Quicken who implemented the API Keys incorrectly. I'm not just trying to paste API Keys into a normal user/password. Quicken has a special security page for this (see pic). They just implemented it wrong.0
-
Let me state that a different way. Quicken was programmed around the OFX protocol, and so they programmed its restrictions all through Quicken. Now clearly, if they are going to support this interface, they should have worked through the flow that that uses it and removed those restrictions, but just as clearly, they have not.
They need to fix this.Signature:
This is my website: http://www.quicknperlwiz.com/1
This discussion has been closed.