Hey Jedox friends! 👋 If you have ever wanted to bring your QuickBooks Online numbers into Jedox without manually exporting files, this guide is for you. We will go step by step through the setup: first in Intuit Developer, then in Postman, and finally in Jedox Integrator. It may sound a bit technical at first, but once you break it into smaller pieces, it becomes much easier to follow.
Why connect QuickBooks Online with Jedox?
QuickBooks Online is where many companies keep their accounting data. Jedox, on the other hand, is where you can turn that data into planning, reporting, and analysis. A simple example: instead of downloading a Profit and Loss report from QuickBooks every month, you can pull it directly into Jedox and use it in a dashboard, a planning model, or a scheduled report.
What we will build
In the end, we want one thing: a working REST connection from Jedox Integrator to the QuickBooks Online API. To get there, we need three building blocks: an app in Intuit Developer, a refresh token from Postman, and an OAuth plus REST setup in Jedox Integrator. Think of it like getting a key, testing the key, and then using that key inside Jedox.
Step 1: Create your app in Intuit Developer
Start by opening the Intuit Developer portal and signing in. If you do not have an account yet, create one first. Then create a new app for QuickBooks Online. This app is basically the bridge between QuickBooks and external tools like Jedox. It will give you the Client ID and Client Secret, which we will need later for authentication.
Step 2: Copy your keys and credentials
Inside your Intuit app, go to the keys and credentials area. Copy the Client ID and Client Secret and keep them somewhere safe while you work through the setup. You will use them first in Postman and then again in Jedox Integrator. Small tip: this is one of those places where copy-paste mistakes can cost you a lot of debugging time.
Step 3: Add the redirect URI
For the Postman authorization flow, add the Intuit OAuth playground redirect URL as the callback URL. This tells Intuit where to send the authorization response. In simple words: after you approve access, Intuit needs to know where to send Postman back.
Step 4: Prepare Postman
Now open Postman and create a new collection. Postman is useful here because it helps us go through the OAuth flow and get the refresh token. We only need to do this setup part once, but it is an important step before moving into Jedox.
Step 5: Configure OAuth 2.0 in Postman
In Postman, open the Authorization settings and choose OAuth 2.0. Then enter the values from your Intuit setup. The key fields are the callback URL, authorization URL, access token URL, scope, Client ID, and Client Secret. Once these are in place, Postman can request access from QuickBooks.
Postman values to use
Use these values in Postman:
- Callback URL: https://developer.intuit.com/v2/OAuth2Playground/RedirectUrl.
- Authorization URL: https://appcenter.intuit.com/connect/oauth2.
- Access Token URL: https://oauth.platform.intuit.com/oauth2/v1/tokens/bearer.
- Scope: com.intuit.quickbooks.accounting. State: any value you like.
- Client ID and Client Secret: copy them from Intuit Developer.
Step 6: Get the refresh token
After you complete the authorization flow in Postman, you should receive an access token and a refresh token. The refresh token is the one we really care about for Jedox. Why? Because Jedox can use it to request fresh access tokens automatically, instead of you manually updating the connection every time the token expires.
Step 7: Build the QuickBooks API URL
The QuickBooks API URL has three parts: the base URL, your company ID, and the report endpoint. For example, a Profit and Loss request can look like this: https://quickbooks.api.intuit.com/v3/company/{company ID}/reports/ProfitAndLoss?minorversion=65. In your own setup, replace the company ID with the one from your Intuit account. Later, you can also change the report endpoint if you want to load a different QuickBooks report.
Step 8: Create the OAuth token connection in Jedox
Now comes the Jedox part. In Jedox Integrator, create a new OAuth token connection. This connection takes care of the token refresh process in the background. That means your REST connection can stay authenticated without you copying a new access token every time. Nice, right?
Jedox OAuth token settings
Use the token endpoint https://oauth.platform.intuit.com/oauth2/v1/tokens/bearer. Set the authentication method to oauth2RefreshToken, use your Client ID and Client Secret, set the scope to com.intuit.quickbooks.accounting, use basicAuthHeader as the client authentication type, and set refresh token mode to automatic refresh. Also add an additional request parameter called State with any string value.
Step 9: Create the REST connection
Next, create the REST connection in Jedox Integrator. Use the QuickBooks API URL you built earlier and connect it with the OAuth token connection. This REST connection is the part that actually calls QuickBooks and brings back the report data. If everything is configured correctly, this is where the setup starts to feel real.
Step 11: Create a JSON extract
Once the REST connection works, create a JSON extract on top of it. The QuickBooks response comes back as JSON, so the extract helps Jedox read the response in a structured way. From there, you can transform the data, clean it up, and load it into your Jedox model.
Beginner tip: test each part separately
If something does not work immediately, do not panic. API setups often fail because of one tiny missing value or a copied character too much. Test the setup in small steps: first the token in Postman, then the QuickBooks URL, then the OAuth token connection in Jedox, and finally the REST connection and JSON extract. This way, you know exactly where the issue is.
Common things to check
Before you start rebuilding everything, check the basics: Is the Client ID correct? Is the Client Secret copied fully? Is the refresh token stored in the right setting? Is the scope set to com.intuit.quickbooks.accounting? Is the company ID correct? And is the report endpoint written exactly as expected? Most of the time, the problem is hiding in one of these simple details.
What can you do next?
Once the connection is working, you can make it more powerful. For example, you can call other QuickBooks reports, parameterize the URL with variables, schedule the load in Jedox Integrator, or transform the result into a clean reporting cube. This first setup is just the starting point.
Final thoughts
And that’s it! 🎉 You now have the basic structure for connecting QuickBooks Online with Jedox. The setup looks technical because OAuth is involved, but the idea is simple: create the Intuit app, get the token in Postman, configure OAuth in Jedox, build the REST connection, and read the result with a JSON extract. Once this works, you can reuse the same pattern for many other API-based integrations.
If this saved you some time, consider supporting with a coffee ☕ — always appreciated! https://buymeacoffee.com/stefanvelickovic33. It helps us to run and host the website. Thanks <3