本文介绍了LinkedIn新API-无法获得r_network权限的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我继承了一个用旧的LinkedIn API编写的程序,我正尝试将其迁移到新的API.当我尝试获得r_basicprofile权限时,我的oauth令牌有效.但是,当我尝试r_networkrw_nus时,会得到响应

I inherited a program that was written with the old LinkedIn API, and I'm trying to migrate it to the new API. When I try to get the r_basicprofile permission, my oauth token works. However, when I try r_network or rw_nus, I get a response

但是,当我转到www.linkedin.com/developer/apps/xxxx/auth时,选中了r_networkrw_nus的框.

Yet, when I go to www.linkedin.com/developer/apps/xxxx/auth, the boxes for r_network and rw_nus are checked.

即,一个请求

有效,但要求

给出该错误.我究竟做错了什么?

gives that error. What am I doing wrong?

推荐答案

从5月15日

Profile API — /v1/people/~ `
Share API — /v1/people/~/shares
Companies API — /v1/companies/{id}


看起来linkedin不再希望与其API共享任何内容.创建一个新的应用程序表明,唯一可能的选项是r_basicprofiler_emailaddressrw_company_adminw_share:


It looks like linkedin no longer wants to share anything with their API. Creating a new app indicates that the only possible options are r_basicprofile, r_emailaddress, rw_company_admin, and w_share:

TLDR:他们已锁定API,并将使用范围限制在极为有限的一组访问点中.

这篇关于LinkedIn新API-无法获得r_network权限的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

08-01 04:06