Digikey not working with API v4?

[mkne]

Hi there,

I wasn't able to get Digikey information provider running for quite a while. I always thought it might have to do with firewall or proxy issues. But today looking a bit deeper into the logs I found out that I just have to switch to deprecated Digikey API v3 instead of the API v4 I had configured for my production app. So I created a new production app that uses Digikey API v3 and put the new keys in my docker-compose.yaml, restarted my docker container, executed the oauth (which didn't show a digikey login because I was probably already logged in through another browser tab) and finally was able to find parts with the Digikey information provider.

@jbtronics Should we mention that on the documentation or are there plans or work in progress to switch to Digikey API v4?
I could add something to the documentation.

Maybe it's another reason than API v3 vs. v4 and just a sideeffect of switching to other API keys that it works now. So I would be happy to hear of other users which Digikey API they're using.

[jbtronics]

The whole v4 API is significantly different than the v3 (and I am not really sure, if it actually gives the amount of information as the v3), so the info provider doesnt work with v4.
Some hint in the documentation would probably be good, but in the long term it should be switched to the v4 API, as the v3 is probably not staying forever...

[mkne]

I've created a pull-request: #858