Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Exchange Token Endpoint is Broken #9

Open
MakerScott opened this issue Mar 26, 2017 · 6 comments
Open

Exchange Token Endpoint is Broken #9

MakerScott opened this issue Mar 26, 2017 · 6 comments

Comments

@MakerScott
Copy link

The exchangeToken endpoint should point to: "item/public_token/exchange" not "exchange_token". I assume the API changed at some point.

@travoltron
Copy link
Owner

Which branch did you install from? 2.0 is under some heavy modification all over the place, so it may be a little wonky.

In the meantime, I'll take a look at that endpoint and see if I can patch that for you.

@MakerScott
Copy link
Author

Master branch. It looks like all the endpoints need to change. I would take a look at that. It's my first time working with Plaid, so I'm not sure if they pushed breaking changes. I also didn't need to call the tartan URI in config, and I changed that to sandbox. The sample JS they provide on their site to launch Link uses the sandbox environment. The token can only be exchanged using the sandbox URI on the server side, and using my own client_id and secret vars.

@travoltron
Copy link
Owner

Yeah, looks like I'm operating on a legacy branch. This all is a wholesale change, with each product now being a distinct ITEM , and having its own access_token. Hrmmm. It might be a minute while I redo this. Thanks for the heads up.

@travoltron
Copy link
Owner

FWIW, I didn't get any notice from Plaid and I use their API in two different projects, and my existing connection works without trouble. But these all represent breaking changes.

However, they've been nothing short of amazing to work with thus far.

@MakerScott
Copy link
Author

Interesting. I definitely got it working by adjusting these settings. It's possible they may have a legacy API that still works for older customers.

@travoltron
Copy link
Owner

travoltron commented Mar 26, 2017 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants