nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Coinbase API for Online Setup?

joecg

Has anyone successfully configured Coinbase for download within Quicken?

What portions of the ID and Private Key did you input into Quicken?

The Quicken feature either still doesn't work as intended, or more instruction is needed. I've reviewed the Coinbase Product API Docs, https://docs.cdp.coinbase.com/coinbase-app/docs/quickstart . Don't tell me to contact Coinbase; my question is how Quicken has implemented this API and what format values is Quicken expecting? I'm wondering if someone successfully verified this works after the August update, or perhaps the textbox lengths just increased? (see Background below) If it's verified, then what is the format? It doesn't appear to be copy/paste out of Coinbase…

Example ID and Private Key values, as provided by Coinbase:

organizations/12345678-90ab-cdef-1234-567890abcdef/apiKeys/12345678-90ab-cdef-fedc-ba0987654321

-----BEGIN EC PRIVATE KEY-----\nLMnOpQRStUvWxYZ9876543210123abcDEFghiJKLmnoPQRstuVWXyz123456789z\nABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyzAbCdEfGhIjKl\n1234566790123456789012345678901234==\n-----END EC PRIVATE KEY-----\n

I've tried the values as provided by Coinbase in full - e.g. including the key header/footer and newline characters - also in variations stripping these seemingly unnecessary characters out and/or using just the key_id portion of the ID/key_name. I get a CC-503 every time, until I hit CC-929 due to failed attempts.

This is not working/intuitive. If Quicken intends for this to work, then more instruction should please be made available.

Background: I reported the Legacy issue in July —

https://community.quicken.com/discussion/7954513/quicken-does-not-support-coinbase

Quicken updated their product to extend the field length in August —

https://info.quicken.com/win/release-r58-8-august-2024

Find more posts tagged with

Accounts

Crypto Currency

One Step Update

Comments

Quicken Anja

Hello @joecg,

We recently had a Coinbase Alert posted that was marked as resolved last week. However, since you are still experiencing this CC-503 error, could you please navigate to Help > Report a problem within your Quicken program and submit a problem report with log files and screenshots attached in order to contribute so we can escalate this further for you?

It would also aid the investigation to include a sanitized file when submitting the problem report. A sanitized file is a data file that removes personally identifiable information so you can comfortably share this file with the Quicken team.

While you will not receive a response through this submission, these reports will help our teams in further investigating the issue.

We apologize for any inconvenience in the meantime! Thank you.

Patrick T Williams

Even though Quicken has not resolved the zero balance problem for months now, please answer the question above, does Quicken accept the new CDP keys and if so, how do you enter them for login to Coinbase.

joecg

@Quicken Anja — Could you provide a link to the Coinbase alert? I searched but couldn't find it.

EDIT: I found it, but it's stated as still open, and doesn't seem to relate. I'm wondering if that's now an issue for existing connections created using the LEGACY method. For others' reference, here is that article - https://community.quicken.com/discussion/comment/20471586

I'm hunting for any guidance on the proper format here. Maybe I have it and something else is indeed wrong. I have submitted the "Report a problem", but if I'm not going to receive a response and the issue is in my execution then that isn't going to be helpful.

Anyone at all could chime in with a personal confirmation they've made a Coinbase connection using the new CDP API method, and if there was anything more to it than copying the values out of the https://www.coinbase.com/settings/api confirmation modal and pasting them into the respective fields in Quicken "Add Account" dialog for "Coinbase - Bitcoin Wallet". That is, including the "——-BEGIN…" and "END" portions, as well as all the escaped newlines '\n'

All the variations I've attempted fail. I've made keys both specifying no whitelist and with 0.0.0.0/0 CIDR.

Doesn't work.

q_lurker

There was also an Alert initiated 12/20/24 and 'Resolved' 1/15/25. That Alert is archived (not generally available). The text of the original alert was

___________________

Users attempting to connect to Coinbase - Bitcoin Wallet Investor in Quicken Classic for Mac will encounter error FDP-103, while Quicken Classic for Windows users will encounter error CC-503.

This has been escalated internally, though we do not have an ETA at this time.

To be notified of updates as they become available, please click the bookmark ribbon located in the upper right. If you do not see the bookmark ribbon, please make sure that you are signed into the Quicken Community.

(Ticket #11458652)

_______________________Note that is a different ticket number that your find was. Beyond that, I don't see the information particularly illuminating.

joecg

@q_lurker - Ah, thank you for that helpful reply. When searching for that ticket number, I see this thread —

https://community.quicken.com/discussion/comment/20471778#Comment_20471778

It seems that the alert from a couple weeks ago that was mentioned is because the Legacy API method was retired. I suspect that while Quicken increased the field lengths in August due to reports that they were too short for the new CDP API method, they may never have actually implemented/accommodated the new method. That also seems likely since there was only one "Coinbase" entry listed in the Connected Account provider list (aside from the Canada one) and to overload the single type they'd need to condition off the input format. Seems unlikely since guidance on this has been scarce.

I hazard to guess that anyone who has been using Coinbase successfully until recently was using the old (now fully deprecated) method. I suppose that's good news for me and others similarly situated since it is more likely to motivate Quicken/Coinbase to get the new method properly implemented and/or explained.

Quicken Anja

Hello @joecg,

Thank you for contributing to this discussion.

While the previous Alert has been marked as resolved, we do have an internal escalation ticket (CBT-564) that remains open. Please note that this ticket is only accessible internally.

I appreciate you taking the time to submit a problem report with your log files attached. I will retrieve it and get your log files added to the ticket.

Thank you!

Patrick T Williams

I had also submitted a problem report in hopes that if enough people send in reports Quicken will take action. I can also confirm that Coinbase has deprecated the old key method and just to reiterate, the old method allowed login but Quicken only reported zero balances so hopefully they will fully fix this with the new CDP keys sooner than later.

Quicken Kristina

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 #11592597/CTP-10554)

joecg

@Quicken Kristina FYI, the Community Alert was just marked as resolved. However, I just attempted again and it isn't fixed. Still getting CC-503 when trying to Add Account: Coinbase - Bitcoin Wallet

I've confirmed there isn't a client update, "You already have the latest version of Quicken ( Release R61.21 )."

FYI @Quicken Jasmine since it seems the alert may have been marked Resolved prematurely.

I submitted a report using "Report a problem…" again after this new failed attempt ~5 minutes ago.

Quicken Anja

Hello @joecg,

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.