From the looks of our code, it’s set to display that error when the Credly API response is a “401” error. I see this comment in the code right above the spot.
// If the response resulted from potentially bad credentials
Have you double checked and also made sure you didn’t have caps lock on at the time?
Otherwise, I believe it’s all the responsibility of the API itself and not something the plugin has control over.
If you want, I can try to help locate the API key directly and you could enter it that way.
Hi Michael – thanks for the reply. I have tried again, and reset the pw.
Still no joy.
If you could point me in the right direction that would be help
Many thanks
Edward
Out of curiosity, have you been to https://developers.credly.com/my-apps to set up anything there? I believe that’s where you need to go, but it’s been awhile since I looked it over, and the Credly integration isn’t a strong point with me like it perhaps should be.
I went the the dev section and got it to generate an api key for me. And it seems to have worked. So off to see how the process goes now. Thanks for the pointer
Awesome, and yeah we need to look into refining this process imho.
Let me know if you run into other issues.
Hi Michael
Thanks for the above
Sadly – have run into an issue. We have four badges – with as far as I can tell identical setup. Only one of them is showing at Credly. Also, if I set up a test user, then none of their achievements are showing up at in their accounts. I notice that the credly badge id is only appearing for one.
I don’t know if this is a badgeos or a credly thing…
Any thoughts?
Hard to say. As long as the plugin here is sending the data to Credly, then that’s all we can ask for. How it’s processed on Credly’s end is out of the plugin’s hands.
May not hurt to contact them and see if they have any insight on how similar situations are handled.
