Skip to content

Support of LinkedIn API v2 #167

@anibalsanchez

Description

@anibalsanchez
Q A
Bug? no
New Feature? yes
Are you using composer? yes
Version 1.0.0

Actual Behavior

Support of LinkedIn API v1.

Expected Behavior

Support of LinkedIn API v2.

... To reiterate: all developers need to migrate their apps to our newest APIs and OAuth 2.0 by March 1, 2019. To help navigate the migration process, please see the technical migration guide on the LinkedIn section of the Microsoft Docs website. Developers can expect follow-up communications via email about these changes and other future announcements about the LinkedIn Developers program.

Reference: LinkedIn v1 to v2 API Migration Frequently Asked Questions

Steps to Reproduce

Create a new App and try to use the new API v2 endpoints.

Possible Solutions

Create a new major version 2.0 of the library. It'd be great to use Happyr/LinkedIn-API-client for LinkedIn API v2.0.

Do you plan to support the new API? Or, will Happyr/LinkedIn-API-client be obsolete after March 1, 2019?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions