Issue in export to Json

[ayazali23]

https://www.linkedin.com/in/noamgraetz/
please check I Cannot export to Json like these types of profiles?

[joshuatz]

Hmm. I think there is actually a site-wide issue with the tool at the moment; not just that profile, but every profile (or at least ones that require an API endpoint). At a quick glance, this looks to be an issue with the LinkedIn Voyager APIs changing.

I'll try to make time this week to tackle this. Hopefully this will be a quick fix, like just updating an endpoint URL, but I can't tell for sure right now.

[ayazali23]

Thank you so much for your help

…

On Mon, Dec 6, 2021, 14:38 Joshua Tzucker ***@***.***> wrote: Hmm. I think there is actually a site-wide issue with the tool at the moment; not just that profile, but every profile (or at least ones that require an API endpoint). At a quick glance, this looks to be an issue with the LinkedIn Voyager APIs changing. I'll try to make time this week to tackle this. Hopefully this will be a quick fix, like just updating an endpoint URL, but I can't tell for sure right now. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#63 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AWXXZOGFWG5ZQN2S3Q2CWODUPSACPANCNFSM5JG6XH2Q> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[joshuatz]

@ayazali23 I finally had some time to work on this - should now be fixed in the new v3.2.2 release.

(For anyone wondering - yes, the endpoints did change. I also added some code to try and make it easier to "discover" them in the future, as well some documentation notes around some interesting new GraphQL flavored endpoints).