Creating a Coinbase Account in Quicken for Mac... is this possible?
I have tried adding an account in my quicken for Mac and see the option for Coinbase - Bitcoin Wallet (coinbase.com). It brings up the normal menu but instead of asking for username and password for the account (like all my other accounts), it ask for an API Key and Secret Key.
I created the keys according to the Coinbase process and (Copy Paste) those two keys but keep getting an error.
I am not sure if the length of the key is too long or if Quicken should simply be asking for username and password.
Anyone out there successful with simply adding the Coinbase using these new API Keys?
Comments
-
Flagged for moderator to move to a Mac forum category.
-splasher using Q continuously since 1996
- Subscription Quicken - Win11 and QW2013 - Win11
-Questions? Check out the Quicken Windows FAQ list0 -
I have the same exact issue:
It asks for API Key and API Secret and on Coinbase website, it generates API Key and EC Private Key. I am assuming the Private key is the secret key. I also get error. I dont know which portion of the Private Key is the password.
Quicken Mac Premier Starting 8/2024
Quicken Windows 2000-2024
Successfully moved to Mac with thousands of transactions and stock/option trades. Quicken Mac handles large files a lot faster.
0 -
Hello All,
Thank you for taking the time to report this issue to the Community, although we apologize for any frustration or inconvenience experienced.
This issue has been reported to our Development and Product teams for further investigation and resolution. Though we do not currently have an ETA, you can bookmark this Community Alert to get updates when available and to know when the issue is resolved. If you do not see the bookmark icon at the upper right, please make sure you are logged into the Community.
Thank you!
(Ticket #11458652)
Quicken Kristina
Make sure to sign up for the email digest to see a round up of your top posts.
0 -
I did a search on (Ticket #11458652) and found there was a post that this was RESOLVED. I've installed the 1/15 Quicken update Version 8.0.0 (Build 800.56192.100) and still get the same error when trying to use a newly generated API Key and EC Private Key. Also, could you please show us an example of how the keys should be entered. ex.
api_key = "organizations/{org_id}/apiKeys/{key_id}"
api_secret = "-----BEGIN EC PRIVATE KEY-----\nYOUR PRIVATE KEY\n-----END EC PRIVATE KEY-----\n"0 -
UPDATE 1/17: I've installed the 1/17/25 Quicken for Mac Version 8.0.1 (Build 800.56243.100) on macOS 15.2 and still get the same error. Please provide an example of the required API Keys.
0 -
I don't see this working yet….
0 -
This still does not work, and as snowland requested, provide an example of the string that needs to be entered as the API and Private Key so we can actually access the account through Quicken.
0 -
Hello All,
I can see the original resolution was to use the legacy API.
What happens when you attempt to connect? Are you seeing any error messages/codes?
I look forward to your responses!
Quicken Kristina
Make sure to sign up for the email digest to see a round up of your top posts.
0 -
If you are new to Coinbase, there is no legacy API. Coinbase has eliminated generation of those APIs in favor of new API format. So, that is why we are asking for a specific cut and paste example of what we need to pull from the new format API that we generate to use as the API Key and Secret Key.
2 -
Thank you for your reply,
What happens when you attempt to connect? What error messages/codes are you seeing?
Thank you!
Quicken Kristina
Make sure to sign up for the email digest to see a round up of your top posts.
0 -
There is no error number, just a Quicken dialogue box that says "Did you mistype your sign-in info?" Please re-enter your credentials for Coinbase. If the log in only works with legacy keys that needs to be fixed ASAP, because here is a quote from the Coinbase website
"Legacy keys will be expiring on Feb 5, 2025
On February 5, 2025, we will be expiring all legacy API keys. Create new CDP API keys and update your code to continue using Coinbase App APIs after February 5, 2025."
1 -
I am trying to access the Community Alert to follow it but I get a permissions error and I am signed in. Is there another email/alert that I should be following?
0 -
Thank you for your replies,
The Community Alert was marked resolved and archived after a few days. You are seeing the permissions error because it's archived.
Thank you for providing the additional information and for sending a problem report!
I forwarded this issue to the proper channels to be further investigated. In the meantime, if you haven't already done so, please navigate to Help > Report a problem and submit a problem report with log files attached and (if you are willing) a sanitized copy of your data file in order to contribute to the investigation.
While you will not receive a response through this submission, these reports will help our teams in further investigating the issue. The more problem reports we receive, the better.
We apologize for any inconvenience!
Thank you.
(CBT-564)
Quicken Kristina
Make sure to sign up for the email digest to see a round up of your top posts.
0 -
Did this issue get resolved? Any update or ETA?
0 -
Thank you for your reply,
The issue is still happening and has been re-reported. It is in work. No additional information or ETA is available at this time.
Thank you!
Quicken Kristina
Make sure to sign up for the email digest to see a round up of your top posts.
0 -
I am also having this issue. I had Coinbase connected to my Quicken for Mac, however I was forced to reset my Quicken Cloud and when doing so it knocked out all my connections. They sent out emails to all informing that they would be expiring legacy keys in favor of a Coinbase Developer Platform (CDP) API key on 2/24/25. My legacy key had still worked until this morning, and when trying to connect a newly created API key Quicken is not recognizing them.
It would be great if Quicken could address this.
0 -
@Quicken Kristina Since this is acknowledged by Quicken, is there a Support thread owned by Quicken we should be following?
0 -
Thank you for your reply,
An alert just came out for this issue. Please bookmark the Community Alert linked below:
If you do not see the bookmark icon, please make sure you are logged into the Community.
Thank you!
(Ticket #11592597/CTP-10554)
[Edited - Added link to alert]
Quicken Kristina
Make sure to sign up for the email digest to see a round up of your top posts.
0 -
I did not sign up to be a Beta tester for Quicken. We have been given the support runaround for many months. How is it that a company this size can not support its product? Why can it not give us the required format for entering the api key and api secret? This is technology at its worst!
0 -
I have had this issue for many months, had an escalated support ticket, voice calls, so far no resolve. Will bookmark this thread and wait
1 -
Could someone please explain the difference between Ticket #11458652 and Ticket #11592597/CTP-10554 which shows this issue was RESOLVED. I've installed the 3/12 Quicken update Version 8.1.0 (Build 801.56843.100) on macOS 15.3.1 and still get the same error when trying to use a newly generated API Key and EC Private Key. This has been emphasized many times by me and others to provide a format example of how the keys should be entered. (entire or partial string) example:
api_key = "organizations/{org_id}/apiKeys/{key_id}"
api_secret = "-----BEGIN EC PRIVATE KEY-----\nYOUR PRIVATE KEY\n-----END EC PRIVATE KEY-----\n"Someone at Quicken must have tested this to state the issue was
RESOLVED 3/12/25(Ticket #11592597/CTP-10554). Thanks!0 -
Hello @snowland,
Thanks for following up!
After double-checking the internal escalation ticket, I can confirm that it is still open and actively being worked on. The Community Alert was originally marked as resolved because the internal alert was closed, but since the escalation ticket remains open, I have updated Jasmine's post to reflect that the alert is now marked as Closed rather than Resolved.
Even though the alert is closed, once the escalation ticket is completed and the issue is fully resolved, the alert will still be updated to reflect that resolution.
We apologize for any confusion and appreciate your patience in the meantime! Thank you.
-Quicken Anja
Make sure to sign up for the email digest to see a round up of your top posts.1
