#ryanw

1 messages · Page 1 of 1 (latest)

alpine agateBOT
fading palm
royal drum
#

Understood, that is the suggested approach. But still curious, is there a way to get the connected account publishable key via API?

#

Or get connected account publishable key in any other fashion?

fading palm
#

There is, but we very strongly discourage using it.

#

What's your use case?

royal drum
#

Understood, it is discouraged. Our team has been working on an integration for quite some time. We took the approach of the frontend using connected account publishable keys directly (not sure myself on why this is the decision, but that's our setup). We are storing CA publishable keys on our end and sending them to the FE to use. I believe one of our CA publishable keys was incorrectly stored on our part and so the FE is not working correctly with it. All other connected accounts & keys are working just fine. I'm just looking to get the publishable key for the affected account

#

Refactoring to the other approach at this point is not feasible in the short term. A good short term fix for us is just getting the connected account key value one time, so that we can record the correct key and fix our problem

fading palm
#

You get those keys at connection time. You're saying you didn't save them at that time and want to retrieve them for an account that's already connected?

royal drum
#

Yes exactly. I think we did not record the correct key at connection time, so I'd like to retrieve it now

alpine agateBOT
fading palm
royal drum
#

Ah I see. I'm not sure we have the refresh token stored either 😞

#

Is there another avenue if we do not have the refresh token?

fading palm
#

If you don't you would need to disconnect and reconnect the account.

royal drum
#

Got it, how is that done?

fading palm
#

Is it a Standard or Express account?

royal drum
#

Standard

fading palm
royal drum
#

Okay got it. Thank you!

#

Appreciate the assistance and all the docs on this