Getting Started with Reckon API

Hello and welcome to the Reckon API developer help site. The information on this site will help you navigate through our API technical documentation, as well as provide information on the various integration offerings. Happy coding.

 

Which Product?

The very first thing you will need to do is decide which Reckon Product you want to integrate with. Reckon currently has three public APIs/SDKs for our business range. In most cases your choice will be dictated by your target market, however we can give you guidance if you are unsure which of our applications is most suitable.   

Product

Summary

Integration Method

Reckon One

3-tier architecture browser application; available in AU, NZ and UK

RESTful API (see docs for latest version) / JSON

Reckon Accounts Desktop

Reckon Accounts (formerly known as QuickBooks® in AU and NZ). API supported for Premier and Enterprise versions. See HERE for more information on the Reckon / QuickBooks ®

Intuit QuickBooks® Desktop SDK v6.1 /qbXML / Intuit QuickBooks®  web connector v2.1.0.30

Reckon Accounts Hosted

Reckon Accounts [Enterprise] desktop hosted at AWS. Browser deployment (no virtual app installed)

Intuit QuickBooks® Desktop SDK v6.1 / qbXML / Intuit QuickBooks®  web connector v2.1.0.30 plus RESTful API v2.1

Reckon One Payroll

3-tier architecture browser application; available in AU only.

RESTFUL API (see docs for latest version) / JSON

 

RECKON ACCOUNTS HOSTED
For Accounts Hosted we always encourage developers to integrate with Accounts desktop first. This is because both use the same SDK at a database level, therefore to ensure integrity, your calls should be robustly tested on desktop before introducing the RESTful API component. More information on the differences (and similarities) between the two products can be found on the Hosted API documentation pages.

Accessing the Documentation

All content that is accessible to the public is available on this help site, however the process of gaining access to specific developer documentation is a little different depending on the application.

As Reckon Accounts is based on the Intuit QuickBooks (TM) source code we are required to have you agree to certain T&Cs prior to accessing the SDK. The Accounts Hosted API was developed by Reckon, and therefore access to documentation is less restricted. Reckon One was built from the ground up by Reckon, therefore we expose the full API documentation to the public. 

Available Resources

  • Azure API Portal (Public)
  • Azure API Portal Keys (approved developer partners only)
  • Reckon One Endpoints
  • Reckon Accounts SDK (approved developer partners only)

Reckon API Sample App

Accelerate your integration development by checking out our Sample App. Click here to learn more.

Becoming a Reckon Developer Partner

So you have decided which application, or indeed applications, you want to develop to, so what next? The first step is to become a Reckon Developer Partner. It is a completely FREE program and provides access to the following:

 

  • Reckon add-on marketplace listing
  • Marketing campaigns to our 600,000+ user base
  • Reckon product partners (over 6,000) and partner events
  • Documentation (public as well as restricted)
  • Azure API portal (Reckon One and Accounts Hosted)
  • Free Support
  • Application licenses for testing as required
    • Reckon One
    • Reckon Accounts Desktop Enterprise
    • Reckon Accounts Hosted

You will find more details and the application form  here

 

Requirements

 

Online APIs

For us to provide you with your Oauth key, sub-key, client ID and secret ID you will need to provide us with your callback URL (aka redirect URI). You can supply one or multiple callbacks, and these can be changed at any time, for example, before your application connection is live, however we do need this to provide access to the Azure API portal 

Example callbacks are:

  • localhost
  • 127.0.0.1
  • myapp.com/reckon-api
Without your keys and IDs you will not be able to test your integration with our online products.

 

Do not use a generic email such as gmail or hotmail on the application - your application will be rejected. If you are a developer working on behalf of a company, they must provide the application and verify you are who you say you are. 

 


How did we do?


Powered by HelpDocs