Building a QuickBooks Online integration usually means the same routine: read the entity docs, work out which calls to make, guess at the order, and hope the books come out right. We wanted to shorten that path — a lot.

That’s why we built the Solution Center, a new experience in the Intuit Developer Portal designed to help you set up and build a working integration with guidance.

Here’s how it works:

1. Start from a workflow, not an endpoint.

Open an accelerator — Accounts Receivable, Accounts Payable, Sales Tax — and you get the whole arc: create the customer, create the invoice, record the payment, check the balance. All the core calls for the workflow, in order, with the dependencies made explicit.

2. Set your language and your sandbox company once.

Each accelerator has a language selector: Node.js, Python, Java, .NET, or PHP. Every code sample on the page rewrites itself. Pick your sandbox company there too, and the samples fill in with your own values instead of placeholders.

3. Run each step as you read it.

You don’t have to leave the page to see whether a call works. Send the request, read the response, and move to the next step with a real object ID rather than a guess.

4. Read the accounting, not only the API.

Each accelerator shows the journal entries your calls produce. Recording the payment typically debits cash and credits accounts receivable. Two lines, and now you know why the balance moves the way it does — and what your integration looks like to the accountant or bookkeeper who reviews it.

5. Keep building.

From there, start with Quickstart if you’re new to the platform, browse the rest of the catalog, or head straight to your dashboard. Quickstart is open to every tier. All other accelerators are only available with a paid tier.

Building with an AI coding tool?

Every accelerator includes a Copy for AI option that puts the whole page on your clipboard as structured markdown. Paste it into the tool of your choice and and gives it grounding instead of a guess..General-purpose AI coding assistants are trained on broad web data, which can lag behind recent API changes.

Our markdown carries the current endpoint paths with the correct implementation steps. Whether you click through it yourself or prompt your way there, the Solution Center is here to guide you through it all.

Whether it’s your first QuickBooks Online integration or your fifth, the Solution Center answers one question fast: what does each use case actually do to your books? Now you can find out before you build the integration.

Introducing the Solution Center: Build a Complete QuickBooks Workflow, Not Just One API Call was originally published in Intuit Developer on Medium, where people are continuing the conversation by highlighting and responding to this story.

Introducing Intuit Developer Plugin for Claude

If you’ve integrated a new API before, you know the drill: research the API, set up an app in the portal, sort out credentials and OAuth, pick the right scopes, and track down the right endpoint.

An hour later, you finally get a 200 back from a sandbox company, and you haven’t written a line of your actual product yet.

As a developer, I’ve been through this loop with many APIs, including our own. Your AI assistant can already write the integration code in seconds. What slows you down is everything before that code can run.

So we built an Intuit Developer Plugin to let your assistant handle that part too.

What we’re releasing

Intuit Developer Plugin, powered by the Intuit Developer MCP server, connects Claude directly to the Intuit Developer platform. Instead of Claude guessing your setup from docs, it works with your actual developer account: your workspaces, your apps, your sandbox companies, and the live QuickBooks Online API catalog.

You describe what you’re building. Claude handles the setup and gives you a working request to drop into your code. For example:

I want to pull customer invoices from QuickBooks into my app.
Set me up so I can make that call in the sandbox.

From that single prompt, Claude finds your workspace, creates or reuses an app, recommends the scopes you need, guides you through OAuth, creates a sandbox company with sample data, and builds the request. It confirms with you before making any changes.

Install it

What you need: an Intuit Developer account. If you don’t have one, sign up at developer.intuit.com. A workspace is created for you by default.

1. Add the plugin in Claude

You can add the plugin directly from the Claude Plugin Directory and follow OAuth setup when prompted.

For detailed technical instructions and integration guides, check out our Intuit Developer Plugin Documentation.

2. Sign in

Once you have added the plugin and installed the server, Claude prompts you to sign in with your Intuit Developer account. Authentication is handled by the plugin, so you never paste a client secret or token into the chat.

3. Check the connection

Am I connected to Intuit Developer?

Once Claude confirms your account is connected, you’re ready to start building.

How it fast-tracks your build

Choose the right scopes the first time

Scope names are technical, and mapping “I want invoices” to the right one usually means another trip to the docs. Instead, ask Claude:

Which scopes do I need to read invoices and customers?

Claude recommends the least-privilege set, explains what each one grants in plain language, and applies it to your app once you approve.

Complete OAuth setup with guidance

OAuth is where many first integrations stall. Redirect URIs, authorization codes, access and refresh tokens all need to line up, and a 401 error rarely tells you which one is wrong.

Help me get an access token for my sandbox app.

Claude registers your redirect URI, gives you the correct authorize and token endpoints for your environment, and walks you through exchanging the code for tokens and refreshing them. When you need your client secret, Claude gives you a direct link to it in the Developer Portal, so you can copy it yourself and it never passes through the chat. If you receive a 401 later, ask Claude to investigate. It reviews your scopes and token state and explains how to resolve the issue.

Set up a sandbox in one step

Create a sandbox company for testing.

You get a sandbox with sample data, ready for test calls. You can also list, reset, or delete sandboxes from the same conversation whenever you need a clean test environment.

Find the right API by describing what you want

I need to find all open invoices for a customer. Which endpoint should I use?

Claude searches the QuickBooks Online API catalog by intent and pulls the full schema for the endpoint: parameters, required scopes, and an example cURL. You no longer need to cross-reference the API reference against the scopes documentation.

From first call to your codebase

Once your app, scopes, and sandbox are ready, choose how far you want to go. Ask for a quick cURL to test the call:

Give me a cURL request to list invoices from my sandbox company.

Or have Claude wire the entire flow, including OAuth, directly into your app:

Integrate the QuickBooks OAuth flow and an invoice list call into my Node.js app.

Claude writes the code with the right endpoints, scopes, and base URL for your environment. Add your client secret from the Developer Portal, run it, and keep building.

Built for development, with the same guardrails

The plugin gets you building faster. It doesn’t change how access works.

• Sandbox only. It’s built for development and testing. It doesn’t make production API calls or generate production keys.
• No extra permissions. Your app’s scopes and OAuth authorization control what it can access, exactly as they do in the Developer Portal.
• You stay in control. Claude explains app and scope changes and asks before applying them.
• Secrets stay out of the chat. Keep client secrets and tokens out of prompts, source code, and logs.

AI-generated output can contain mistakes, so review generated requests and code before you ship them. When you’re ready for production, complete the review and compliance steps in the Intuit Developer Portal. Claude can point you to the next step.

What’s under the hood

The plugin exposes a focused set of connector tools:

Connection

• Intuit_developer_connectivity_status: confirms your identity and connection

Workspaces and apps

• Intuit_developer_workspace_read: reads your workspace details
• Intuit_developer_app_read: gets app details
• Intuit_developer_app_create: creates a new app
• Intuit_developer_app_update: updates redirect URIs, name, or scopes

OAuth

• Intuit_developer_oauth_details: returns the OAuth endpoints for you to configure

Sandbox

• Intuit_developer_sandbox_list: lists your sandbox companies
• Intuit_developer_sandbox_create: creates a sandbox company
• Intuit_developer_sandbox_reset: resets sandbox test data
• Intuit_developer_sandbox_delete: deletes a sandbox company

API discovery

• Intuit_quickbooks_api_search: searches QuickBooks API operations by intent
• Intuit_quickbooks_api_describe: returns the schema, scope, base URL, and example cURL

Try it and tell us what you think

Install the plugin, open Claude, and ask it to set you up for your first QuickBooks API call. Setup that once meant switching between the portal, docs, and your IDE now happens in a single conversation.

We’re starting with Claude and plan to support more AI development environments. If there’s a workflow you want the plugin to handle, we want to hear about it. Submit a ticket or post on our forums.

Claude is a trademark of Anthropic, PBC. This integration is developed by Intuit and is not sponsored, endorsed, or affiliated with Anthropic

Claude is a third-party service provided by Anthropic. Anthropic does not sponsor or endorse this plugin. Features and results may vary. Review and test generated outputs before use.

Build with Intuit Developer AI plugin was originally published in Intuit Developer on Medium, where people are continuing the conversation by highlighting and responding to this story.

We’re excited to announce the launch of the Sales Order API, giving you direct access to create, read, update, and delete sales orders in QuickBooks Online and Intuit Enterprise Suite. This includes:

1. A new GraphQL API to create, retrieve, update, and delete sales orders, including line items, tax details, shipping, and billing information.
2. Support for both US and global (non-US) tax models, so apps built on the API work consistently whether a company uses sales tax groups or VAT-style header/line tax treatment.
3. Interoperability with existing linked transactions, invoices, and purchase orders, so you can build end-to-end order-to-cash and order-to-procurement workflows.

Together, these enhancements enable you to build richer order management and fulfillment experiences directly into your apps. As non-posting transactions, sales orders allow businesses to reserve inventory items without impacting financial records. Once fulfillment begins, these records can be seamlessly converted into invoices or purchase orders to facilitate end-to-end accounting workflows.

What’s included in this release

Create a sales order

Use the salesCreateSalesOrder mutation to create a sales order, setting the customer reference, line items, and optional shipping address and project reference attributes. This resource supports both US tax groups (set at the header, with lines marked taxable/non-taxable) and global VAT-style tax treatment (tax type at the header, tax group per line).

API type: GraphQL

Read a sales order

Use the salesSalesOrder query to retrieve a single sales order by ID, including its line items, tax detail, shipping and billing addresses, and order status.

API type: GraphQL

Update a sales order

Use the salesUpdateSalesOrder mutation to update an existing sales order. The line array uses full-replace behavior — any line present in the stored record but omitted from the update request is deleted, so apps must re-include every line they want to retain, along with the current syncToken.

API type: GraphQL

Delete a sales order

Use the salesDeleteSalesOrder mutation to delete an existing sales order.

API type: GraphQL

Feature support by product

Sales orders and the Sales Order API are supported for QuickBooks Online Plus, QuickBooks Online Advanced, and Intuit Enterprise Suite. Support is also available in QuickBooks Online Simple Start and Essentials with the Inventory Add-on purchase. Sales orders can be converted and linked to invoices and to purchase orders, so integrations can trace an order through fulfillment and billing.

How to get access

The Sales Order API is available to Silver, Gold, and Platinum tier partners within the Intuit App Partner Program. To get access:

1. Sign in to your developer account at developer.intuit.com.
2. Navigate to My Hub and select your app under App Dashboard.
3. Go to the Permissions section in your app settings and enable the sales.sales-order.read and sales.sales-order.write scopes under Restricted scopes.
4. Add the enabled scope to your OAuth authorization requests, alongside the default com.intuit.quickbooks.accounting scope for linked transactions such as invoices and purchase orders. Then make API calls to the GraphQL endpoint.
5. Enable the Sales Orders feature in the QuickBooks company (Settings > Account and Settings > Sales, or the applicable feature toggle for Sales Orders).

Endpoints:

• Production: https://qb.api.intuit.com/graphql
• Sandbox: https://qb-sandbox.api.intuit.com/graphql
• Accounting REST API (for linked transactions): https://quickbooks.api.intuit.com/v3/company/entityname/

Note: If you’re already on a paid tier and still don’t have access, open a support ticket.

What’s next?

Explore the new Sales Order API today using the GraphQL API Explorer and the Get Started and Use Cases documentation.

We’ll be sharing sample code and prompts for common sales order workflows shortly to help you get started. In the meantime, you can begin integrating the create, read, update, and delete use cases into your app using the reference queries and mutations in the documentation.

We’d love to see what you build with the Sales Order API.

We’re excited to announce the launch of the Sales Order API, giving you direct access to create… was originally published in Intuit Developer on Medium, where people are continuing the conversation by highlighting and responding to this story.

Intuit Connect, the premier accounting event, is almost here. Starting October 26, 2026, thousands of accounting professionals and Intuit partners will gather at the ARIA Las Vegas and immerse themselves in all things Intuit.

For three days, they’ll:

• Receive exclusive product announcements directly from the team building the Intuit platform.
• Participate in — and earn CPE credits from — their choice of 73 (and counting) interactive sessions.
• Learn from industry and keynote experts whose individualized perspectives open the door to new and exciting insights.
• Discover the latest updates to Intuit’s core releases along with the innovative third-party applications in the Expo Hall.
• Engage directly with peers, industry experts, and Intuit team executives to grow community connections and their businesses.

We’re excited to provide our entire community with world-class knowledge and experiences that drive thriving businesses, but that’s not all we’re excited about. This year, we’re offering our invaluable partners an expanded connected experience, bringing our distributors, resellers, and integrators together in one place and giving them an inside track into Intuit’s vision, roadmap, and new partner program designed to ensure continued partner success.

Intuit Connect 2026 Partner Opportunities

At Intuit, our mission to Power Prosperity Around the World is fundamentally supported by the relationships we’ve built with our partners. Every partner, whether an ISV, Developer, Mid-Market Partner, or VAR, is essential to delivering, scaling and supporting Intuit along with our shared customers. That’s why the theme for our new Connect Partner Track Customers First, Partners Always. Here’s what to expect as part of Partner Track:

Partner Appreciation Reception:

Kicking off Intuit Connect 2026 will be our Partner Appreciation Reception on Sunday, October 25 from 6:00 PM — 8:00 PM. We want to thank our partners for their inexhaustible support and efforts on our behalf while also taking a moment to look back on FY26, ahead to FY27, and at the role our partners play as we move forward. And this year, we’ve added something new: Partner awards for those with outstanding achievements.

Recognizing partners for going above and beyond is just one way to show our appreciation.

Partner 1:1 Meetings:

Another way is by providing Partner 1:1 Meetings with Intuit Leadership during Connect. These 30-minute meetings, which take place on Monday, October 26 and Tuesday, October 27 and are set up in advance through Intuit account managers, enable partners to speak directly with the leaders driving Intuit’s roadmap. During the individual conversations, partners can share details about their business as well as discuss topics such as growth, go-to-market, customer adoption, product, AI, API integration, and so much more.

Partner Track:

Perhaps most exciting for partners who attend Intuit Connect 2026 is our Dedicated Partner Track. From 9:00 AM to 2:00 PM on Wednesday, October 28, this unified Partner Track will dive deep into Intuit’s next steps and provide opportunities for partners to give their opinions on what those steps should be. They’ll learn about our FY27 partner commitments and get hands-on with our MCP tools right alongside the solution engineers.

We’ll also have the featured session: Ahead of the Curve — Reading Where AI Is Taking Accounting and How Partners Stay Essential. Taking place during the Partner Track, this session is led by Roman Villard, CPA and Founder of Full Send who “takes the customer’s seat for an audience-driven Q&A on where AI is heading in accounting, and what scaling businesses will need from partners next.”

Whether they’re a partner who builds, resells, implements, or advises, they should plan to bring their hardest questions. And expect to walk away with insightful, business-growing answers.

Intuit Connect 2026: A truly do-not-miss event

Intuit Connect 2026 is Intuit’s accounting event of the year, and we invite our partners to register today for a full conference pass.

With the pass, they’ll enjoy main-stage keynotes and informative breakout sessions. They’ll also have access to the Expo Hall where they can experience the Mid-Market Growth Hub (a 15-minute consultation with a hand-selected Intuit Enterprise Suite expert) and access to the Partner Program Info Desk to get all their technical and API integration as well as Intuit App Partner Program (and more) questions answered. Most importantly, the full conference pass will open the door to the dedicated Partner Track sessions with two audience-specific breakouts mid-day.

Learning, shaping Intuit’s future, and connecting with the Intuit community is on tap for partners who attend Intuit Connect 2026.

“Connect is like a festival: high energy, amazing people, meaningful conversations, with sessions on point,” says K.C. Eames, Director of Clients Accounting Services Dark Horse CPAS.

We couldn’t have said it better ourselves, and we can’t wait to see you there!

Intuit Connect 2026: Partner Track was originally published in Intuit Developer on Medium, where people are continuing the conversation by highlighting and responding to this story.

Getting paid is always one of the best parts of running a business and QuickBooks Online makes it easy to keep track of those payments. In this tutorial, we will simulate the Receive Payment functionality via the API to help you invoice, charge a card (securely) and record that a customer has made a payment. You will need to have the com.intuit.quickbooks.accounting and com.intuit.quickbooks.payment scopes enabled in order to accurately follow this tutorial.

Step 1: Create an invoice using the Accounting API

To make this request you must:

• Have at least one sales item (item for sale)
  - If Type=Inventory you must include the Quantity (Qty) in order to create an invoice.
  - This article explains more in detail
• Know the CustomerRef (Customer ID)
  - If you do not know the id you can query a customer to find the id
  SELECT * FROM Customer WHERE givenname = ‘REPLACEWITHCUSTOMERFIRSTNAME’
  - Make a note of the Customer.Id value

Request

POST /v3/company/<realmId>/invoice?minorversion=75

{
  "Line": [
    {
      "DetailType": "SalesItemLineDetail",
      "Amount": 500,
      "SalesItemLineDetail": {
        "ItemRef": {
          "name": "Sprinkler Pipes",
          "value": "17"
        },
        "Qty": 20
      }
    }
  ],
  "CustomerRef": {
    "value": "<insert customer id>"
  }
}

Response

{
  "Invoice": {
    "AllowIPNPayment": false,
    "AllowOnlinePayment": false,
    "AllowOnlineCreditCardPayment": true,
    "AllowOnlineACHPayment": true,
    "domain": "QBO",
    "sparse": false,
    "Id": "***",
    "SyncToken": "0",
    "MetaData": {
      "CreateTime": "2025-10-20T14:34:58-07:00",
      "LastModifiedByRef": {
        "value": "*****************"
      },
      "LastUpdatedTime": "2025-10-20T14:34:58-07:00"
    },
    "CustomField": [],
    "DocNumber": "1074",
    "TxnDate": "2025-10-20",
    "CurrencyRef": {
      "value": "USD",
      "name": "United States Dollar"
    },
    "LinkedTxn": [],
    "Line": [
      {
        "Id": "1",
        "LineNum": 1,
        "Amount": 500,
        "DetailType": "SalesItemLineDetail",
        "SalesItemLineDetail": {
          "ItemRef": {
            "value": "17",
            "name": "Sprinkler Pipes"
          },
          "Qty": 20,
          "ItemAccountRef": {
            "value": "**",
            "name": "Sales of Product Income"
          },
          "TaxCodeRef": {
            "value": "NON"
          }
        },
        "CustomExtensions": []
      },
      {
        "Amount": 500,
        "DetailType": "SubTotalLineDetail",
        "SubTotalLineDetail": {}
      }
    ],
    "TxnTaxDetail": {
      "TotalTax": 0
    },
    "CustomerRef": {
      "value": "58",
      "name": "****** *****"
    },
    "BillAddr": {
      "Id": "96"
    },
    "ShipAddr": {
      "Id": "96"
    },
    "FreeFormAddress": true,
    "ShipFromAddr": {
      "Id": "137",
      "Line1": "Expressway Auto 2628 Mistletoe Dr.  North Pole, AK  9970",
      "Line2": "North Pole, AK  99700"
    },
    "DueDate": "2025-11-19",
    "TotalAmt": 500,
    "ApplyTaxAfterDiscount": false,
    "PrintStatus": "NeedToPrint",
    "EmailStatus": "NotSet",
    "Balance": 500
  },
  "time": "2025-10-20T14:34:57.712-07:00"
}

Step 2: Create a card token using the Payments API

This step will allow you to create a token that will allow you to “mask” the customer’s card details for privacy reasons and is the preferred method to capture this information.

We provide mock credit card info for testing and processing payments purposes.

• If you are using Postman you can create the request-Id parameter by:
  - Passing request-id: {{$randomUUID}} to auto-generate a unique UUID
• Take a note of the response value — that is your token that you will use in the next step

Request

POST /quickbooks/v4/payments/tokens

{
  "card": {
    "name": "emulate=0",
    "number": "4111111111111111",
    "expMonth": "02",
    "address": {
      "postalCode": "94086",
      "country": "US",
      "region": "CA",
      "streetAddress": "1130 Kifer Rd",
      "city": "Sunnyvale"
    },
    "expYear": "2029",
    "cvc": "123"
  }
}

• The “name” parameter reflects the customer name on the card.
• Make sure the expYear parameter is a future year

Response

{
    "value": "********-****-****-****-************"
}

Step 3: Create and capture a charge using the Payments API

Using the response value from Step 2, send a request with the:

• Amount — amount/total of the transaction
• Currency — the currency the charge was made in
• Capture — set to true; default is false
• Token — response value from Step 2
• Context — additional information included in the request
  - Mobile — was this charge made from a mobile device [ keyed, swiped, dipped or tapped on the merchant’s POS device]?
  - isEcommerce — was this transaction made over the internet?

NOTE: Mobile and isEcommerce cannot be the same value

Request

POST /quickbooks/v4/payments/charges

{
  "amount": "500.00",
  "currency": "USD",
  "capture": "true",
  "token": "<token value from previous step",
  "context": {
    "mobile": "true",
    "isEcommerce": "false"
  }
}

Response

{
  "id": "MT11111111111",
  "created": "2025-07-04T18:20:10Z",
  "status": "CAPTURED",
  "amount": "500.00",
  "currency": "USD",
  "token": "10164ea35c491a8478215c1c6a6d54ffe1801",
  "card": {
    "number": "xxxxxxxxxxxx1111",
    "expMonth": "02",
    "expYear": "2029",
    "cvc": "xxx",
    "name": "emulate=10301",
    "address": {
      "streetAddress": "1130 Kifer Rd",
      "city": "Sunnyvale",
      "region": "CA",
      "country": "US",
      "postalCode": "94086"
    },
    "cardType": "Visa"
  },
  "context": {
    "mobile": true,
    "isEcommerce": false,
    "recurring": false,
    "deviceInfo": {},
    "clientTransID": "<clientTransIDvalue>"
  },
  "capture": true,
  "authCode": "tst940",
  "avsStreet": "Pass",
  "avsZip": "Pass",
  "cardSecurityCodeMatch": "NotAvailable"
}

Take note of the clientTransID value as you will need it for Step 4.

Step 4: Link the Payment to the Invoice using the Accounting API

For this final step, you will need to link the payment to the invoice using the SalesReceipt endpoint.

• Line — all details should match the invoice created in Step 1
• Customer Ref — matches the customer of the invoice from Step 1
• CreditCardPayment -
  - Process Payment : set to true
  - CC TransId : matches the clientTransId value from Step 3: Create a Charge
• TxnSource: Intuit Payment ; this signifies originating source of the payment transaction

Request

POST /v3/company/<realm Id>/salesreceipt

{
  "Line": [
    {
      "Id": "1",
      "LineNum": 1,
      "Description": "Sprinkler Pipes",
      "Amount": 500,
      "DetailType": "SalesItemLineDetail",
      "SalesItemLineDetail": {
        "ItemRef": {
          "value": "17",
          "name": "Sprinkler Pipes"
        },
        "UnitPrice": 25,
        "Qty": 20
      }
    }
  ],
  "CustomerRef": {
    "value": "58",
    "name": "Denise Test"
  },
  "CreditCardPayment": {
    "CreditChargeInfo": {
      "ProcessPayment": "true"
    },
    "CreditChargeResponse": {
      "CCTransId": "<clientTransIDvalue from previous step>"
    }
  },
  "TxnSource": "IntuitPayment"
}

Response

{
  "SalesReceipt": {
    "domain": "QBO",
    "sparse": false,
    "Id": "151",
    "SyncToken": "0",
    "MetaData": {
      "CreateTime": "2025-09-04T12:03:03-07:00",
      "LastUpdatedTime": "2025-09-04T12:03:03-07:00"
    },
    "CustomField": [],
    "DocNumber": "1044",
    "TxnDate": "2025-09-04",
    "CurrencyRef": {
      "value": "USD",
      "name": "United States Dollar"
    },
    "Line": [
      {
        "Id": "1",
        "LineNum": 1,
        "Description": "Sprinkler Pipes",
        "Amount": 500,
        "DetailType": "SalesItemLineDetail",
        "SalesItemLineDetail": {
          "ItemRef": {
            "value": "17",
            "name": "Landscaping:Sprinklers:Sprinkler Pipes"
          },
          "Qty": 20,
          "ItemAccountRef": {
            "value": "79",
            "name": "Sales of Product Income"
          },
          "TaxCodeRef": {
            "value": "NON"
          }
        },
        "CustomExtensions": []
      },
      {
        "Amount": 500,
        "DetailType": "SubTotalLineDetail",
        "SubTotalLineDetail": {}
      }
    ],
    "TxnTaxDetail": {
      "TotalTax": 0
    },
    "TxnSource": "IntuitPayment",
    "CustomerRef": {
      "value": "58",
      "name": "Denise Test"
    },
    "BillAddr": {
      "Id": "96"
    },
    "ShipAddr": {
      "Id": "96"
    },
    "FreeFormAddress": true,
    "ShipFromAddr": {
      "Id": "103",
      "Line1": "123 Sierra Way",
      "Line2": "San Pablo, CA  87999"
    },
    "TotalAmt": 500,
    "ApplyTaxAfterDiscount": false,
    "PrintStatus": "NeedToPrint",
    "EmailStatus": "NotSet",
    "Balance": 0,
    "CreditCardPayment": {
      "CreditChargeInfo": {
        "ProcessPayment": true
      },
      "CreditChargeResponse": {
        "CCTransId": "<clientTransIDvalue from previous step>",
        "Status": "Completed",
        "CardSecurityCodeMatch": "NotAvailable",
        "AvsStreet": "Fail",
        "AvsZip": "Fail"
      }
    },
    "DepositToAccountRef": {
      "value": "4",
      "name": "Undeposited Funds"
    }
  },
  "time": "2025-09-04T12:03:02.972-07:00"
}

Troubleshooting

• Invalid Reference Id : An item in this transaction is set up as a category instead of a product or service.
• Token is invalid/not associated with payment data : Tokens are only valid for 15 mins. You may need to generate a new token and update the value to create a charge

Resources

• What is a requestId and how to use it
• Create a dynamic requestId using Postman
• Practice processing payments using mock data
• Process a payment

From invoice to payment: a step-by-step walkthrough was originally published in Intuit Developer on Medium, where people are continuing the conversation by highlighting and responding to this story.

Getting started with a new API often means the same routine: read the docs, spin up a project, wrestle with OAuth, and hope your first request doesn’t 401. We wanted to shorten that path — a lot.

That’s why we built Try It Out, a new guided experience in the Developer Portal that takes you from sign-up to a successful sandbox API call without writing a single line of code. Here’s how it works:

1. Your app is ready — in seconds. The moment you sign up, we provision an app for you: client ID, client secret, and a sandbox environment, all set up and waiting. Nothing to configure.

2. Get an access token, step by step. Try It Out walks you through the OAuth 2.0 authorization code flow right in the browser. Authorize your app, pick a sandbox test company, and exchange your code for a token. At each step, we show you the actual HTTP request and response, so you can see exactly what’s happening under the hood instead of taking it on faith.

3. Make a real API call. Pick a sample call, such as GET Company Info, and run it against your sandbox company. You’ll get a full response with real sandbox data, proof that your credentials, token, and request all work together.

4. Keep building. From there, jump into our Get Started, explore example integrations, or head straight to your dashboard.

Building with an AI coding tool? The new Try It Out flow is built with AI tools in mind and works with popular AI coding tools. Don’t want to use the browser? Hit Copy for AI to bring your app’s credentials and context straight into the tool of your choice and start building in an instant. Whether you prefer to click through it yourself or prompt your way there, Try It Out meets you where you already are.

Whether you’re evaluating our platform for the first time or onboarding a new team member, Try It Out is designed to answer one question fast: does this actually work? Now you can find out before you write a single line of code.

Introducing “Try It Out”: Make your first API call, without writing a line of code was originally published in Intuit Developer on Medium, where people are continuing the conversation by highlighting and responding to this story.

Why this matters

Retries are a useful tool, but they’re also easy to get wrong. If you retry a failing request repeatedly with no backoff or cooldown, you’re not helping your app recover, you’re piling more load onto a service that’s already struggling. That drives error rates up further and can trigger rate limiting that affects other callers as well.

The good news is there’s a simple, well-known way to avoid this by knowing when to retry and when not to retry. This post covers when to retry, when not to, and how to do it safely, focusing on the difference between 4XX and 5XX errors.

Not every error is worth retrying

The first question to ask before retrying is simple: can a retry actually change the outcome? The status code usually tells you.

For most 4XX error codes, you do not want to retry. For 5XX error codes, you typically will. This 4XX vs 5XX split is standard HTTP practice, not specific to any company or API. The differences between these two types of errors are described in detail below. Further down, we’ll look at how it plays out in Intuit’s own published QuickBooks Online API limits.

4XX: fix the request, don’t just retry it

A 4XX status code indicates that the problem is with the request itself, typically caused by a bad payload, missing field, expired token, or resource that doesn’t exist. The server looked at what you sent and rejected it.

Sending the same request again won’t help. A problem that causes a 400 error will send a 400 error later, no matter how many times you try. Retrying just adds load to the API for no benefit.

• 400 Bad Request: fix the payload or parameters, then send it again. Don’t resend it as is.
• 401 Unauthorized: refresh the credentials and retry once. Don’t loop on this.
• 403 Forbidden: a permissions issue. Retrying won’t grant access.
• 404 Not Found: the resource isn’t there. Retrying won’t create it.
• 409 Conflict: re-check the current state and fix the request rather than resending it.
• 429 Too Many Requests: this is the one exception. Retry, but only after honoring the Retry-After header or cooldown period the server gives you.

5XX: usually transient, worth retrying with care

A 5XX error code means something went wrong on the server side. Your request may have been fine. These errors are often temporary, caused by a deploy, failover, or brief spike in load, and they tend to clear up on their own within seconds or minutes. That’s why retrying can work here, unlike with most 4XX errors.

• 500 Internal Server Error: generally safe to retry with backoff.
• 502/504 Bad Gateway or Gateway Timeout: usually a transient infrastructure issue. Retry with backoff.
• 503 Service Unavailable: often the service is shedding load or under maintenance. Retry, but don’t hammer it. Back off meaningfully.

How to retry safely

• Only retry what’s actually retryable: 5XX and 429. Ignore other 4XX errors until the request itself is fixed.
• Back off exponentially. Wait longer between each attempt (1s, then 2s, then 4s, and so on) instead of retrying immediately or at a fixed interval.
• Add some jitter, a bit of randomness in the wait time, so a bunch of clients that failed at the same moment don’t all retry in lockstep.
• Cap the retries. Pick a max (3 to 5 is typical), and after that, fail loudly instead of retrying forever.
• Honor Retry-After when it’s present. If the server tells you how long to wait, use that instead of your own timer.
• Consider a circuit breaker for anything that keeps failing. If a dependency is clearly down, stop calling it for a while instead of retrying request after request.
• Use idempotency keys where they’re supported, especially for anything that creates a resource, so a retry can’t accidentally create a duplicate. This is where the RequestId field helps. Send it as a query parameter on your request, and if the same RequestId comes in again, the service returns the original response instead of re-running the operation. This prevents a retry from creating a duplicate.

Before and after

Before: a request fails with a 400, you retry the same broken payload right away, it fails again, and you keep going. Nothing succeeds, and you’ve just added unnecessary load to the API.

After: a request fails with a 400, so you log it, fix the payload, and send a corrected request. A request fails with a 503, so you back off with jitter, retry up to a set limit, respect any Retry-After hint, and if it still fails after that, you stop and raise an alert instead of continuing to hammer the API.

Retrying the Right Way: 4XX vs 5XX was originally published in Intuit Developer on Medium, where people are continuing the conversation by highlighting and responding to this story.

The Invoice API now returns two new boolean fields on the Invoice object:

• AllowOnlineAffirmPayment
• AllowOnlinePayPalPayment

These sit alongside the two existing online-payment fields already on the Invoice object:

• AllowOnlineACHPayment — bank/ACH online payment
• AllowOnlineCreditCardPayment — credit card online payment

All four fields work the same way: each corresponds to a payment-method toggle on the Invoice screen in QuickBooks Online, and each can be set explicitly on create/update or left to default from the company’s payment settings.

What these fields do

Each of these four fields controls whether a specific online payment method is offered on an invoice, matching the corresponding toggle in the QuickBooks Online invoice screen.

The four fields:

• AllowOnlineCreditCardPayment - customer can pay with a credit/debit card
• AllowOnlineACHPayment - customer can pay directly from their bank account
• AllowOnlinePayPalPaymentnew - customer can pay with PayPal or Venmo
• AllowOnlineAffirmPaymentnew - customer can pay using Affirm, splitting the invoice into installments ("buy now, pay later")

Credit Card and ACH have been available for some time; PayPal and Affirm are the two newest additions, following the same pattern.

Setting a field to true doesn't guarantee the method is offered - the company must also be eligible (payments-enabled, onboarded, active subscription). An explicit value always overrides the company's Sales-settings toggle, in either direction, as long as the company remains eligible - the toggle only determines the default, used when the field is omitted.

• true → method enabled (toggle on)
• false → method disabled (toggle off)
• omitted → defaults to the company’s current setting

Worked example: what happens if a company has PayPal or Affirm “disabled”?

• Not subscribed to Affirm/PayPal, field set to true → Result: false — can't override a missing subscription
• Subscribed, but toggle is off, field set to true → Result: true — explicit value wins

This override is symmetric — an explicit false also overrides a toggle that's switched on - and applies to all four fields: AllowOnlineCreditCardPayment, AllowOnlineACHPayment, AllowOnlinePayPalPayment, and AllowOnlineAffirmPayment.

Company UI setting that activates these fields

The underlying eligibility is driven by the company’s Sales/Invoice payment settings, in the same place as the existing ACH and credit card options:

QuickBooks Online → Gear icon → Account and Settings → Sales → Invoice payments

From here, a company that is payments-enabled and onboarded to Affirm and/or PayPal will see those options available to toggle on invoices, same as the existing Credit Card and Bank Transfer (ACH) toggles.

Creating an Invoice with these fields

Both fields are passed the same way as the existing AllowOnlineACHPayment / AllowOnlineCreditCardPayment fields — as top-level boolean properties on the Invoice payload.

REST request

POST https://sandbox-quickbooks.api.intuit.com/v3/company/{realmId}/invoice
Authorization: Bearer {access_token}
Accept: application/json
Content-Type: application/json

{
  "Line": [
    {
      "DetailType": "SalesItemLineDetail",
      "Amount": 100.00,
      "SalesItemLineDetail": {
        "ItemRef": { "value": "1", "name": "Services" }
      }
    }
  ],
  "CustomerRef": { "value": "1" },
  "AllowOnlineAffirmPayment": true,
  "AllowOnlinePayPalPayment": true,
  "AllowOnlineACHPayment": true,
  "AllowOnlineCreditCardPayment": true
}

Node.js

// assumes qbo is an already-authenticated node-quickbooks client:
// const QuickBooks = require('node-quickbooks');
// const qbo = new QuickBooks(consumerKey, consumerSecret, oauth_token, oauth_token_secret, realmId, useSandbox, debug, minorVer, oAuthVer, refresh_token);

const invoice = {
  Line: [
    {
      DetailType: "SalesItemLineDetail",
      Amount: 100.00,
      SalesItemLineDetail: { ItemRef: { value: "1", name: "Services" } }
    }
  ],
  CustomerRef: { value: "1" },
  AllowOnlineAffirmPayment: true,
  AllowOnlinePayPalPayment: true
};

qbo.createInvoice(invoice, (err, createdInvoice) => {
  if (err) {
    console.error(err);
    return;
  }
  console.log(createdInvoice.AllowOnlineAffirmPayment, createdInvoice.AllowOnlinePayPalPayment);
});

Java

// assumes customerRef and lines (a List<Line>) are already built,
// and dataService is an authenticated DataService instance -
// see Intuit's QBOConceptsTutorial-Java for a full working example.
// add() throws FMSException - wrap in try/catch or declare it in production code.

Invoice invoice = new Invoice();
invoice.setCustomerRef(customerRef);
invoice.setLine(lines);
invoice.setAllowOnlineAffirmPayment(true);
invoice.setAllowOnlinePayPalPayment(true);

Invoice createdInvoice = dataService.add(invoice);

Reminder: if you omit these two fields entirely, QuickBooks Online will fall back to the company’s default eligibility (see “What these fields do” above) rather than defaulting to false.

What the response and invoice UI look like

A successful create/read response will include the two new fields alongside the existing ones:

{
  "Id": "129",
  ...
  "AllowOnlineACHPayment": true,
  "AllowOnlineCreditCardPayment": true,
  "AllowOnlineAffirmPayment": true,
  "AllowOnlinePayPalPayment": true
}

On the QuickBooks Online invoice screen, each true field shows up as an enabled toggle in the "Payment options" panel of the invoice - for example, the customer-facing invoice will show an Affirm and/or PayPal option next to the existing Credit Card / Bank Transfer options, letting the customer choose that method when paying online.

Here’s what this looks like in practice, from a real QuickBooks Online company with Affirm and PayPal enabled:

SDK availability

Both fields are included in the latest QuickBooks Online SDKs. Older SDK versions that don’t recognize the new properties can throw deserialization errors when reading an Invoice response — for example, this exact error showed up in the PHP SDK before it was updated:

Property QuickBooksOnline\APIData\IPPinvoice::$AllowOnlineAffirmPayment does not exist. Class QuickBooksOnline\API\Data\IPPinvoice

Please update to the latest SDKs to avoid this error and utilize these fields:

If you use the Java SDK, please upgrade to version 6.5.5
If you use the.NET SDK, please upgrade to version 14.7.1.5
If you use the PHP SDK, please upgrade to version 6.3.1

References

• Review Invoice API reference
• Review General release notes
• Learn more about Affirm payments in QuickBooks Online
• Learn more about PayPal & Venmo payments in QuickBooks Online

Enabling Affirm and PayPal online payments on invoices was originally published in Intuit Developer on Medium, where people are continuing the conversation by highlighting and responding to this story.

There are 47 new reasons to love the QuickBooks App Store! Each new app added to our global marketplace extends the capabilities of QuickBooks for small and mid-market businesses. This quarter’s additions span everything from AI-powered AP/AR automation and construction job costing, to sales tax compliance, POS checkout, and manufacturing inventory.

1. Accrueasy — Automate accrual journal entries for QuickBooks month-end close with AI-powered categorization, no spreadsheets required.
2. AccuPriceLists.com — Sync 1,200+ common electrical products and custom markups into QuickBooks for consistent, same-day field pricing.
3. Appello — Manage scheduling, time tracking, job costing, and safety compliance for ICI contractors with real-time QuickBooks sync.
4. AR Collector AI — Automatically call, text, and email customers to collect on overdue invoices, syncing status back to QuickBooks.
5. ARiA Digital — Send AI-assisted, automated payment reminders based on live QuickBooks invoice data to get paid faster.
6. Bill360 — Automate accounts receivable and get paid an average of 10 days faster with embedded payments for B2B companies.
7. buildclarity — Track job profitability, cash flow, and markup with a financial command center built for contractors.
8. CastleFX — Send, receive, and convert currencies across 200+ countries with automatic exchange-rate reconciliation to QuickBooks.
9. CentID — Print labels, RFID tags, invoices, and reports from iOS and Android with leading barcode and RFID printers.
10. Check Issuing — Print and mail checks directly from QuickBooks Online bills.
11. ClearBox FPA — Build three-statement forecasts and weekly cash flow plans with agentic AI, synced to your QuickBooks general ledger.
12. efacturapty — Automate electronic invoicing (facturación electrónica) for Panama directly from QuickBooks. (Only available in Panama.)
13. Emerald Solutions — Generate emissions, climate-risk, and regulatory compliance reports straight from your existing QuickBooks data.
14. EMERGE App — Manage orders, purchases, and inventory in real time across multiple sales channels with QuickBooks sync.
15. Fora — Take mobile orders and market your business with a responsive website, synced to QuickBooks Online or Desktop.
16. Foresight — Get an AI CFO powered by your QuickBooks data for real-time P&L insights, 12-month forecasts, and hiring analysis.
17. Fraudblock — Verify vendors and payment details with AI to stop fraud before it happens.
18. Fresho — Automate order entry for food wholesalers with AI, syncing invoices and daily payouts to QuickBooks.
19. Hinges AI — Extract invoice data with 99.8% accuracy and link it to POs for faster, cleaner construction AP.
20. IdealAllocations — Allocate expenses in a few clicks with reusable templates that import journal entries directly into QuickBooks.
21. Jofotara Integration — Submit invoices, sales receipts, and credit memos to Jordan’s JoFotara system for ISTD tax compliance.
22. Kintsugi — Automate sales tax, VAT, and GST compliance with free nexus monitoring and filings in 100+ countries.
23. MelkPM — Manage leases, maintenance, and tenant communications with AI-powered property management synced to QuickBooks.
24. MineralTree TotalAP — Capture bills, route approvals, and pay vendors by ACH, check, or virtual card with two-way QuickBooks sync.
25. Missing Toolkit: Estimates — Create detailed estimates with built-in calculations and sync them to QuickBooks with one click.
26. Missing Toolkit: Templates — Generate custom Word and PDF documents from your QuickBooks invoice and estimate data.
27. Payable by Cephgate — Process vendor invoices with AI directly from Gmail and save them to QuickBooks without switching apps.
28. Payment Links Integration — Add a payment link to every QuickBooks invoice automatically and reconcile payments with no manual matching. (Only available in Mauritius.)
29. Planyfin — Plan, track, and build consolidated P&L presentations automatically from your QuickBooks data.
30. Profit Optimizer Pro — Turn your QuickBooks data into a real-time profit dashboard with break-even targets and margin-leak alerts.
31. Quellba — Bulk edit, import, and export QuickBooks transactions with built-in validation and one-click undo.
32. QuickBooks AI connector for Google Drive — Turn your Google Drive files into QuickBooks-ready draft invoices automatically.
33. register by ability business — Ring up sales with a POS checkout app that syncs every line item to QuickBooks Online in real time.
34. Relanco — Send bilingual (English and French) SMS and email invoice reminders built for Canadian contractors.
35. Runbook — Automate custom reporting and analysis in Google Sheets with AI-generated variance explanations from your QuickBooks data.
36. Sanus Benefits — Quote, enroll, and administer employee benefit plans from hundreds of options.
37. Setell — Turn customer requests into priced quotes in minutes with AI, then auto-invoice in QuickBooks the moment they sign.
38. Skyline Payments — Send PayNow links, accept EMV/ACH/card payments, and reconcile invoices in QuickBooks with one click.
39. Spendifique — Capture and clean expense data for batch review before it reaches QuickBooks.
40. Stocksmith — Track raw materials, batches, and finished goods with accurate inventory values and true COGS synced to QuickBooks.
41. SupportBee — Surface QuickBooks customer balances and profile links directly inside your support tickets.
42. Tabiri AI Accountant — Prepare bill entry, coding, and reconciliation work for your review with an AI accounting assistant.
43. WAAVE Payment Request — Send compliant payment request links from QuickBooks for high-risk merchants, with payments syncing back automatically.
44. WEGOTRADE — Sync invoices in real time between QuickBooks and the WEGOTRADE B2B trading platform.
45. Windingflow — Automate purchase orders, supplier invoices, and payments across your supply chain with QuickBooks sync.
46. WorkflowMAX — Manage jobs from quote to invoice and track time and profitability with two-way QuickBooks sync.
47. x2x Lite Manufacturing — Add lightweight BOMs, production orders, and automated cost postings to QuickBooks Online.

To learn more about listing your app on the QuickBooks App Store, go to List your app on our marketplaces. You can also read more about the publishing process in this article on the Intuit Developer Blog.

See the newest apps in the QuickBooks App Store was originally published in Intuit Developer on Medium, where people are continuing the conversation by highlighting and responding to this story.

Earlier this year, we launched the single-entity sandbox for Intuit Enterprise Suite, followed last month by a suite of Project Management and Custom Dimensions APIs expanding what developers can build for our enterprise customers. Today, we’re taking the next step: the Multi-Entity Sandbox is now available for Intuit Enterprise Suite.

What’s new

You can now connect and test your app integrations in a fully isolated, non-production environment with support for multi-entity use cases built in. No more workarounds, no risk to production data.

Getting started

The walkthrough below shows how to access the Multi-Entity Sandbox directly from your developer account.

What’s next

Join us for a webinar on June 25, 2026 for a deep dive into the new sandbox capabilities, a recap of the recently launched APIs, and a live Q&A with our engineering team.

We can’t wait to see what you build.

Multi-Entity Sandbox Now Available for Intuit Enterprise Suite was originally published in Intuit Developer on Medium, where people are continuing the conversation by highlighting and responding to this story.