linkedin api更新评论计数为null [英] linkedin api update comment count null

查看:80
本文介绍了linkedin api更新评论计数为null的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我们每天执行一项工作,以从LinkedIn的api提取数据,并注意到今天收到的值发生了变化.它们实际上都是0,但是现在一个返回为null,另一个像以前一样输入为0.

更新:时间戳:2017-03-28T19:31:25.281Z,UpdateKey:UPDATE-xxxxxxxx,UpdateType:CMPY 数值:1, UpdateComments:总计:0

更新:时间戳记:2017-03-27T18:37:12Z,UpdateKey:UPDATE-xxxxy,UpdateType:CMPY NumLikes:0, UpdateComments:空

LinkedIn是否经常更改其数据回报?这是可以预期的吗?今天还有其他人遇到吗?我担心,LinkedIn端可能会发生一些事情,当它返回非0值时,可能会导致我们收到空值.

谢谢!

解决方案

自2017年初以来,Linked In API发生了变化. 请参阅: http://www.oodlestechnologies.com/blogs/Recent- LinkedIn-API中的更改 https://cloud.c2m.net/linkedin/linkedin-api

另一种可能是由于尝试从应用程序或桌面应用程序访问数据而导致的拒绝,在这种情况下,只需添加

?allowUnsupportedBrowser=true

您的POST请求.

We run a daily job to pick up data from LinkedIn's api and noticed a change today in the values we receive back. They are both actually 0 but one comes back as null now and another comes in as 0 as before.

Update: Timestamp: 2017-03-28T19:31:25.281Z, UpdateKey: UPDATE-xxxxxxxx , UpdateType: CMPY NumLikes: 1 , UpdateComments: Total: 0

Update: Timestamp: 2017-03-27T18:37:12Z, UpdateKey: UPDATE-xxxxy , UpdateType: CMPY NumLikes: 0 , UpdateComments: null

Does LinkedIn change their data returns often? Is this something to be expected? Anyone else running into this today? I'm concerned that there may be something happening on LinkedIn's end that may cause us to receive null values when it should return something other than 0.

Thanks!

解决方案

Since the beginning of 2017 there are changes in the Linked In API. See: http://www.oodlestechnologies.com/blogs/Recent-changes-in-LinkedIn-API and https://cloud.c2m.net/linkedin/linkedin-api

Another posibility could be a rejection due to trying to access the data from an App or a desktop application, in such case, just add

?allowUnsupportedBrowser=true

to your POST request.

这篇关于linkedin api更新评论计数为null的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆