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

CV generation breaks because of latest LinkedIn API update #10

Closed
JMPerez opened this issue Jun 9, 2015 · 2 comments
Closed

CV generation breaks because of latest LinkedIn API update #10

JMPerez opened this issue Jun 9, 2015 · 2 comments

Comments

@JMPerez
Copy link
Owner

JMPerez commented Jun 9, 2015

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 andr_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):

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 !

@JMPerez
Copy link
Owner Author

JMPerez commented Jun 10, 2015

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

@JMPerez
Copy link
Owner Author

JMPerez commented Jun 25, 2015

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.

@JMPerez JMPerez closed this as completed Jun 25, 2015
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

1 participant