Coinbase no longer connects due to a 103 error (edited)
Comments
-
coach Natalie,
Please note that there is an open ticket ticket T-11004189 and someone is looking at that issue. You may want to follow up on the ticket support activity. That may have some additional information
0 -
@RJM, thanks!
I went ahead and reopened the ticket using your case as an example, so you'll now want to follow the Alert for updates on the known issue:
For anyone else experiencing an FDP-103 error with Coinbase after waiting the required 48 hours, please provide the requested information so we can add you to the ticket:
- If the error is occurring on an existing bank account in Quicken Simplifi, the name of the account as it appears in Quicken Simplifi.
- A screenshot of the FDP-103 error in Quicken Simplifi (please expand the message at the top so you can capture the full message with the error code).
- A screenshot of the API Keys page from Coinbase's website that shows the date and time for when the Key was generated.
- A screenshot of the Accounts Summary page from the bank's website that lists all accounts and balances (please redact any personal info) and has a wide enough scope to show the page URL (this must be taken from a web browser and not a mobile browser).
Please also provide your logs via the 'Send Feedback' option:
- Log into the Quicken Simplifi Web App.
- Select Profile from the left-hand navigation bar.
- With the Profile menu open, hold down the Option key for Mac or the Alt key for Windows, and then click Send Feedback.
- Leave all boxes checked, add a brief description of the issue, and then click Send.
Thanks, everyone!
-Coach Natalie
0 -
coinbase doesn't give us an API secret anymore. It’s now giving us an “API Key” and an “EC Private Key”
are people still able to create api keys with secrets anymore? When I go to that website it’s redirecting me to the coinbase developer platform.1 -
@captainkeithy, thanks for posting!
Another user posted these steps here:
- Go to Coinbase.com
- Sign into your account
- Click on the profile button in the top right hand corner
- Go to "My Preferences"
- Look for the tab for "API"
- Click on "Create & Manage API Keys with Coinbase Developer Platform"
- You are directed to a brand new developer portal.
- Click on API keys.
- Generate a new type of oAuth compatible API key/secret.
Let us know if this works for you!
-Coach Natalie
0 -
right. As noted in that post though, keys created through that process do NOT work. Only the keys generated from the old platform work (for now). Any customers like me who are just now trying to connect a coinbase account will not be able to until this is fixed.
Straight from the developer platform “Keys created on the Coinbase Development Platform (CDP) may not yet be supported by all third-party applications.”
0 -
@captainkeithy, thanks for posting back!
Although we appreciate the information, at this time, we'll need to have users follow the API Key and Secret process and wait the required 48 hours from generating the Key and Secret before connecting in Quicken Simplifi. If doing so doesn't allow you to connect, we would then be able to review your case for escalation. Until we find out otherwise from our service provider, these are the connection steps to follow from our end.
I hope this helps to clarify!
-Coach Natalie
0 -
ok. I will create a new one and wait the 48 hours and report back.
1 -
Coinbase has changed from a key/secret to an elliptic curve private key provided as a JSON structure with the key name and PEM-encoded private key. While the old API still technically works, it is not working with Simplifi. When will Quicken be updating to support the new Coinbase API key format?
My previously working accounts won't even sync anymore. I continue to get errors even after putting in the old API key and secret.
The new format has API key name and API key (it isn't labeled as secret anymore and has the additional info that others have posted above). This is how it looks now. Don't worry, I have deleted this API. This is why telling people to reconnect isn't going to work. I don't know why the old ones don't work as they are still supported in theory.
0 -
@minx, thanks for the info!
At this time, we'd need you to generate the API Key and Secret and then allow 48 hours before connecting in Quicken Simplifi with that Key and Secret. If the FDP-103 error persists after doing so, we'd then be able to escalate your case.
Let us know how it goes!
-Coach Natalie
0 -
mine did not work. As Minx referenced above, there is no way to create a new API Key anymore on their end. It’s an entirely new method. I created one with the new process, waited over 72 hours, Input the “private key” where the old secret would go with no luck (of course).
0 -
There is no way to create an API key like @captainkeithy mentioned. The new structure is a PEM-encoded private key like @minx posted above.
@Coach Natalie, this will probably need work by eng. and product teams to update the Coinbase integration.
0 -
@captainkeithy, it sounds like we need to get you added to the ticket. To do so, please provide the following data:
- If the error is occurring on an existing bank account in Quicken Simplifi, the name of the account as it appears in Quicken Simplifi.
- A screenshot of the FDP-103 error in Quicken Simplifi (please expand the message at the top so you can capture the full message with the error code).
- A screenshot of the API Keys page from Coinbase's website (or whatever page you now access) that shows the date and time for when the Key was generated.
- A screenshot of the Accounts Summary page from the bank's website that lists all accounts and balances (please redact any personal info) and has a wide enough scope to show the page URL (this must be taken from a web browser and not a mobile browser).
- Any other proof you can provide of the new process you're outlining so I can share it with the team.
Please also provide your logs via the 'Send Feedback' option:
- Log into the Quicken Simplifi Web App.
- Select Profile from the left-hand navigation bar.
- With the Profile menu open, hold down the Option key for Mac or the Alt key for Windows, and then click Send Feedback.
- Leave all boxes checked, add a brief description of the issue, and then click Send.
@geekay, feel free to chime in on this too, but we will need you to wait the 48 hours.
Much appreciated!
-Coach Natalie
0 -
Coinbase just sent out this email regarding the API update.
Guidelines:
Learn More:
1 -
I don’t see the point in me sending private information for an issue that clearly has nothing to do with my specifically
0 -
Any update on resolution to this issue?
0 -
@kam516, thanks for posting on this topic!
You can follow our Alert here for updates on the known issue with Coinbase:
We appreciate everyone's continued patience as we work to resolve this matter!
-Coach Natalie
0 -
I have failed to switch to the new CDP API key. I reset the connection to Coinbase and when presented with the API key and Secret questions I notice that the field for the Secret is not as long as my new secret. I have pasted everything starting with "-----BEGIN EC PRIVATE KEY-----" all the way through "-----END EC PRIVATE KEY-----\n" and when I display the pasted information Simplifi shows that it ends with "-----END EC "
Am I supposed to cut out the BEGIN and END DC PRIVATE KEY statements? Is the fields really too short?
Quicken for Windows user since 1994 (After MYM for DOS)
Simplifi by Quicken since 20230 -
You’re not doing anything wrong. They need to update the way the app connects to Coinbase’s new system.0 -
I'm having this same issue with the new type of API that Coinbase generates now. When will Simplifi fix this issue so we can all connect back to Coinbase again?
0 -
@Coach Natalie bumping this conversation.
I have the exact same comment as @RiversideKid. It looks like this issue has been ongoing for about two months, has there been any update?
Like RiversideKid explains, the field (API Secret (generated from Coinbase website)) I attempt to put my API secret into is too short, and it gets cut off at "-----END EC"
0 -
[Removed - Speculation] How is this so challenging to provide any feedback on…
0 -
Hello @AndrewH,
We have not yet received any updates. Please bookmark the alert linked in this earlier post, since any updates, once available, will be posted there:
Thank you!
-Coach Kristina
0 -
Hey everyone! We received an update on the Coinbase issue and they've rolled back their new API so you all should be able to connect again using the old system. If you've already cleared your old information/login credentials, you will want to create a new one using the Legacy API Key option.
Can you all give this a try and let us know how it goes, please? Thanks!
-Coach Natalie
0 -
Seems to work for me! Successfully reconnected and loaded in positions & value.
1 -
I logged into my coinbase. do not see the option to create legacy API key. Can you provide where do you see that option. All i see is advance API which does not work with Quicken
0 -
@RajOnTrack, have you tried contacting Coinbase for help locating the Legacy API Key option? I don't have Coinbase myself, so I wouldn't know how to navigate you on their website.
Let us know what you find out in case it helps other users!
-Coach Natalie
0 -
I found that legacy API keys can no longer be created.
0 -
Coinbase support confirmed to me they do not intend to re-enable creation of Legacy API Keys. So, on my end at least, I still cannot connect Simplifi to Coinbase
0 -
@gmedlin, @bobmablob, and anyone else unable to generate an API Key using the old legacy system, can you please confirm that you are still receiving an FDP-103 error? Please also provide some data:
- The name of the account, as it appears in Quicken Simplifi.
- The name of the account(s), as it appears on the bank's website.
- A screenshot of the page where you generate an API Key showing that the "Legacy" option is no longer available.
- A screenshot of the Accounts Summary page from the bank's website that lists all accounts and balances (feel free to redact any personal info) and has a wide enough scope to show the page URL (this must be taken from a web browser and not a mobile browser).
- A screenshot of the error in Quicken Simplifi.
Please also submit your logs via the 'Send Feedback' option:
- Log into the Quicken Simplifi Web App.
- Select Profile from the left-hand navigation bar.
- With the Profile menu open, hold down the Option key for Mac or the Alt key for Windows, and then click Send Feedback.
- Leave all boxes checked, add a brief description of the issue, and then click Send.
Thank you!
-Coach Natalie
0 -
Hi Coach Natalie,
Yes, I am still receiving an error on attempting to connect to Coinbase using the API Key ID and Private Key generated by Coinbase.
Coinbase lists the accounts under My Crypto as Ethereum, though Simplifi shows the (old zeroed out figures) as BTC and Eth.
I've attached the requested screenshots and will send in logs as well. Coinbase also sent out the below email this morning confirming the transition to their new CDP key and a deadline of June 10th, along with guidance for third-party platforms being firm that this is their new direction. So, it seems, the "Legacy" option is explicitly not a long-term fix.
—
Hello,With an extended timeline, effective June 10, 2024, we will be transitioning our existing retail API authentication to a new and improved key creation process powered by CDP (Coinbase Developer Platform) to allow access to your Coinbase account. You will no longer be able to create or edit keys with the legacy authentication method after this date.
If you have existing API keys and OAuth, they will continue to function normally and no further action is required.You can create a CDP API Key today and onboard in a few steps.
- To create your CDP API key, go to the current API settings page and select “Create and Manage Key using CDP”.
- You will be navigated to Coinbase Developer portal to create the key.
- Note: If you are a developer, you can use CDP keys to integrate with Sign in with Coinbase and Advanced Trade API.
- Exchange keys are not impacted by this change.
If you represent a 3rd party platform, and have not yet migrated to a new key type, follow these guidelines to get started. Please note, CDP keys and existing keys have different formats and you must support both key types to support your users. Learn more.
If you encounter any difficulties during the transition process or have any questions, please don't hesitate to reach out to our help center.
1
