如何让其他 API 与您的 API 对话，而您的 API 又与 Twitter 对话？
我能想出的最好的标题，但为了澄清，情况是这样的：
我正在开发一个类似短网址的服务，它允许用户使用他们的 Twitter 帐户“登录”并发布内容。现在该服务可以包含在 Tweetdeck 等应用程序中。
我的问题是..我如何建立这样的联系？让另一个应用程序知道可以与我的 Twitter 应用程序一起使用的某种令牌的流程是什么？
Best title I could come up with, but to clarify, this is the situation:
I am working on a short url-like service which lets users 'log in' with their Twitter account and post stuff. Now this service could be included in applications such as Tweetdeck and the like.
My question is.. how would I make such a connection? What would be the flow to let another app know some sort of token that can be used with my Twitter-app?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
您是否研究过 Twitter 的 OAuth Echo 实现？引用：
此交互涉及四个方：
就您而言，您的服务是委托人。有关文档的更多信息。
Have you looked into Twitter's OAuth Echo implementation? Quoting:
There are four parties involved in this interaction:
In your case, your service is the Delegator. More info on the documentation.
所有不同的系统都使用一组 API 相互通信。理想情况下，会有一种标准的通信形式（REST/SOAP 等），但是每个服务都使用一组不同的技术来实现其公共 API。
例如，twitter 有一个公共 API，您必须学习如何从您的系统与他们的系统进行交互。 tweetdeck 可能也必须与 twitter 交互，并且必须使用 twitter 明确定义的方案来做到这一点。
你的问题有点模糊，但流程很基本。举例来说，有人想与您的系统进行通信。您需要提供一份文件来描述第三方如何这样做，并且您需要强制执行该系统。就像我之前提到的，有 REST——这在今天很流行，或者有 SOAP。然后用户只需向您定义的 url 发出请求即可。示例用户想要在您的服务上创建小部件（REST 示例）：
用户将
HTTP 发布到 http://myapi .com/widgets/以及帖子正文中小部件的属性。用户想要获取所有小部件：
HTTP GET 到 http://myapi.com/widgets将返回小部件列表。这就是基本的想法，你只需要设计一些认证即可。有些只使用基本身份验证，有些则使用誓言。
All the different systems communicate with each other using a set of APIs. Optimally, there would be a standard form of communication (REST/SOAP,etc) however each service my use a different set of technologies to implement their public API.
For example twitter has a public API that you must learn to interact w/ their system from your system. And tweetdeck may have to interact w/ twitter too and must use twitters well defined scheme to do this.
Your question is a little vague, but the flow is basic. Say for example someone wants to communicate w/ your system. You need to provide a document describing how a 3rd party may do so, and you need to impoliment that system. Like I mentioned before, there is REST - this is popular today or there is SOAP. Then the user would simply do a request to a url you define. Example user wants to create a widget on your service (REST Example):
User does
HTTP post to http://myapi.com/widgets/with the attributes for a widget inthe post body.user wants to get all widgets:
HTTP GET to http://myapi.com/widgetswould return a list of widgets.This is the basic idea, you just need to design some authentication. Some just use basic auth and some use oath.