与QuickBooks的在线V3 API交互 [英] Interacting with QuickBooks Online V3 API

问题描述

我正在写一个Web应用程序（也就是不被Intuit公司在其应用中心的事情出版）使用VB.NET和ASP.NET同步的宗旨，与QuickBooks的在线（QBO）进行交互。我有一个很难理解如何准确或从哪里开始这样做。我明白这这算什么：

1. 用户访问您的Web应用程序和连接到QuickBooks的按钮（也忒需要应用内授权）显示。


2. 按钮之前点击你发送一个HTTP请求使用您的消费凭证拿到的OAuth要求凭据。


3. 一旦用户点击他们重定向到QuickBooks的在线（QBO），他们可以登录，然后授权访问某个公司，给你授权的请求凭证的按钮。


4. QBO然后重定向到你的网站表示您授权在你发送一个HTTP请求来获取访问凭据请求凭据。


5. 一旦你的访问凭据你基本上都是免费的与QBO V3 API进行互动。


6. 使用访问凭据，那么你可以构建在体内发送特定的HTTP方法与XML / JSON来执行QBO相应的CRUD操作HTTP请求和QB​​O发送指示是否成功与否的响应。


7. 如果您的应用程序完成与QBO交互您只需确保访问凭据都存储在安全的地方，让用户继续与他们的生活。

（边问：这是正确的还是我错过了什么或者误解的东西吗？）

我的主要问题：你，作为应用开发者，甚至需要构建这些HTTP请求或者你使用他们的SDK或完全不同的东西，我只是没有得到它？

我试图想出解决办法，但它听起来像你应该建造这一切从头开始，但后来我看在他们的SDK和他们有各种不同的实体类型类，但那么他们的串行不序列正确地和他们谈他们的DataService类，以及如何用它来送过来对象，并使用一些JavaScript文件，他们的主机，我只看到引用但没有被他们解释，或者有人真的，我确实发现信息似乎是过时的/德precated雅...

也许这只是我新​​的Web开发而这一切是在我头上的路要走，这很可能是。

（题外话，八九不离十：这是我或者是他们的地盘可笑破这似乎只是有很多无法正常工作或事情是很难浏览和查找...？）

不管怎么说，感谢您的帮助任何人都可以提供。如果我需要提供更多的细节或提出不同的问题或什么，只是让我知道。这个新的，它是比我想象的要问事情更难哈哈。

解决方案

  

我的主要问题：你，作为应用开发者，甚至需要构建
  这些HTTP请求或者你使用他们的SDK或完全的东西
  不同的，我只是没有得到它？

这是完全由你决定，开发商。

如果您的希望的推出自己的，并构建自己的HTTP请求，你当然可以。你几乎肯定会仍希望使用pre封装的OAuth库，OAuth是不平凡的实施。

不过，您也可以肯定使用现有的code库/过的devkit，在这种情况下，图书馆/的devkit将建设HTTP请求你。

该DevKits应该包含例如code向您展示如何真正做到这一点的东西，所以这可能是开始你的最好的地方。

I'm writing a web application (that is not to be published by Intuit on their App Center thing) to interact with QuickBooks Online (QBO) for syncing purposes, using VB.NET and ASP.NET. I'm having a hard time understanding how to do this exactly or where to start. What I understand this this:

1. User accesses your web application and the "Connect to QuickBooks" button (that Intuit requires for In-App authorization) is displayed.
2. Before the button is clicked you send a HTTP request to get OAuth request credentials using your consumer credentials.
3. Once the user clicks the button they get redirected to QuickBooks Online (QBO) where they can sign in and then authorize access to a certain company, giving you authorized request credentials.
4. QBO then redirects back to your site indicating you have authorized request credentials in which you send a HTTP request to get access credentials.
5. Once you have the access credentials you are basically free to interact with the QBO V3 API.
6. Using the access credentials you can then construct HTTP requests that send a particular HTTP method with XML/JSON in the body to perform a corresponding CRUD operation in QBO and QBO sends a response to indicate whether it was successful or not.
7. When your application is done interacting with QBO you simply make sure the access credentials are stored somewhere safe and let the user continue on with their life.

(Side Question: Is this correct or did I miss something or misunderstand something?)

My main question: Do you, as the app developer, even need to construct these HTTP requests or do you use their SDK or something completely different and I'm just not getting it?

I've tried to figure this out but it sounds like you're supposed to construct this all from scratch but then I look in their SDK and they have classes for all the different entity types but then their serializer doesn't serialize correctly and they talk about their DataService class and how you use that to send objects over and using some JavaScript files they host that I have only seen referenced but not explained by them, or anyone really, and information I do find seems to be outdated/deprecated and ya...

Maybe it's just that I'm new to web development and all this is way over my head right now, which very well could be.

(Off-topic-sorta: Is it me or is their site ridiculously broken? It just seems like a lot doesn't work correctly or things are just hard to navigate and find...)

Anyways, thanks for any help anyone can offer. If I need to give more details or ask a different question or something, just let me know. New to this and it's harder than I thought to ask things haha.

解决方案

My main question: Do you, as the app developer, even need to construct these HTTP requests or do you use their SDK or something completely different and I'm just not getting it?

This is entirely up to you, the developer.

If you want to roll your own and construct your own HTTP requests, you certainly can. You almost certainly will still want to use a pre-packaged OAuth library, as OAuth is not trivial to implement.

However, you could also certainly use an existing code library/DevKit too, in which case the library/DevKit will construct the HTTP requests for you.

The DevKits should contain example code to show you how to actually do this stuff, so that might be your best place to start.

这篇关于与QuickBooks的在线V3 API交互的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！