You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Going forward, data received from the Profile API using the r_fullprofile permission can only be used to complement your company's careers pages, as described further on the Apply with LinkedIn page.
The only workaround is to make sure that the basic information is exported, but the information obtained is so small that this tool is rather worthless.
There is a way to manually export your LinkedIn data using https://www.linkedin.com/settings/data-export-page . I will have a look at it, though from the request until one gets the data it might take up to 72 hours !
The text was updated successfully, but these errors were encountered:
The exported data from LinkedIn can be downloaded as a zip file and it contains all the information from a user's profile, so it should be possible to export it to JSON Resume
The exported data contains enough information to compose a quite complete JSON Resume output. This has just been implemented, so I will close this ticket.
Due to some changes in LinkedIn's API (see https://developer.linkedin.com/blog/posts/2015/developer-program-changes) the exporter doesn't have access to some useful scopes that were granted before:
r_fullprofile and
r_contactinfo`.It is unlikely I will have access to this again, since this project doesn't comply with their new restrictions (see https://developer.linkedin.com/support/developer-program-transition):
The only workaround is to make sure that the basic information is exported, but the information obtained is so small that this tool is rather worthless.
There is a way to manually export your LinkedIn data using https://www.linkedin.com/settings/data-export-page . I will have a look at it, though from the request until one gets the data it might take up to 72 hours !
The text was updated successfully, but these errors were encountered: