是否有相当于 Facebook Access Token linter/debugger 的 API?
是否有与我可以通过编程方式调用的 Facebook 访问令牌 linter/debugger 等效的图形 API?
短绒很好。它告诉您有关您拥有的令牌的各种酷炫信息,例如授予的权限(我可以通过 me/permissions
获得)、颁发日期和到期日期、应用程序 ID、应用程序名称、配置文件Id、用户 ID、用户名(如果有效)(如果我尝试调用 /me
并观察返回的异常,则可用)以及来源。
App ID: APP ID : APP NAME
Profile ID: PAGE NAME
User ID: ID : NAME
Issued: 1328916821 : 3:33 pm Feb 10 2012
Expires: 1334100821 : 4:33 pm Apr 10 2012
Valid: True
Origin: Web
那么怎么样呢?是否有一种编程方式来获取此信息,而不必诉诸屏幕抓取 linter 工具?
Is there a graph API equivalent of the Facebook Access Token linter/debugger that I can call programmatically?
The linter is nice. It tells you all sorts of cool information about the token you have, such as the permissions granted (available to me via me/permissions
), the issue and expiration dates, the App ID, App name, profile Id, User Id, User Name, if it is valid (available to me if I try to call /me
and watch for the exception returned), and the origin.
App ID: APP ID : APP NAME
Profile ID: PAGE NAME
User ID: ID : NAME
Issued: 1328916821 : 3:33 pm Feb 10 2012
Expires: 1334100821 : 4:33 pm Apr 10 2012
Valid: True
Origin: Web
So how about it? Is there a programmatic way to get this info without having to resort to screenscraping the linter tool?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(4)
现在可以通过
debug_token
端点https:// /developers.facebook.com/docs/authentication/access-token-debug/
This is now possible with the
debug_token
endpointhttps://developers.facebook.com/docs/authentication/access-token-debug/
这是有可能的。现在您可以检查哪些信息与您拥有的访问令牌相关联。
只需触发此 URL:
来源 https://developers.facebook.com/docs/ facebook-登录/访问令牌/
It's possible. Now you can check what information is associated with the access token you have.
Simply Fire this URL:
Source https://developers.facebook.com/docs/facebook-login/access-tokens/
不,恐怕它不存在。你想要什么?
No, it doesn't exist I'm afraid. What were you wanting it for ooi??
不幸的是,没有。
您可以通过将 &format=json 添加到 URL 来从 URL 调试器获取 JSON 响应,但这目前不适用于 access_token 调试器。
可以为其提交错误!
Unfortunately, no.
You can get a JSON response from the URL debugger by adding &format=json to the URL, but this doesn't work currently for the access_token debugger.
Could file a bug for it!