Skip to main content

Create, update and look up QuickBooks projects

Intuit's developer API covers customers, invoices and estimates, and has no Projects object at all. Clickr adds three operations over the QuickBooks account you already have, on one path, with a bearer token.

Start free trialThe whole connector

$80/month · 7-day free trial · cancel anytime

POST /v2/integrations/quickbooks/projects

Live

Request body

projectName

"Johnson Residence Phase 2"

customerName

"Johnson Family LLC"

startDate

"09/01/2026"

status

"in-progress"

statusCallbackUrl

"https://your-app.com/hooks/qb"

Response

200 OK

receipt

"68b2f0c4e1d9a70012ab34cd"

The call returns a receipt as soon as the run is queued. Clickr signs in, creates the project, and posts the finished record to your statusCallbackUrl.

What changes

Creating the project stops being a retyping job

In QuickBooks today

Someone opens QuickBooks, finds the customer, retypes the project name and re-enters dates that already exist in the system where the job was won. It takes about 5 minutes, it happens on every job, and the mismatches surface later during reconciliation.

Through the Projects API

Your CRM, intake form, Zap or AI assistant posts the project the moment the job is won. The customer name is passed through rather than retyped, and the callback carries the QuickBooks project id back to the system that made the call.

0

Projects endpoints in Intuit's API

3

Operations on this path

~5 min

Of retyping per project today

The endpoint

Three operations on one path

The base path is https://api.clickr.cloud/v2/integrations/quickbooks/projects, with your API key as a bearer token in the Authorization header. Each call is metered as one run.

POST /projects

Create a project

Creates a project against a customer that already exists in QuickBooks. projectName and customerName are required, and the customer is matched by name exactly as it reads in your account.

Body

projectNamecustomerNamestartDateendDatestatusnotesbillingAddressshippingAddresscustomFields

PUT /projects

Update a project

Updates an existing project, identified by projectId. Accounts on Velocity can identify it by projectNameIdentifier instead, which is what systems that never stored the id use. Send only the fields you are changing.

Body

projectIdprojectNameIdentifierprojectNamecustomerNamestatusstartDateendDatenotescustomFields

GET /projects

Look up a project

Returns a project by projectId or projectName. This one reads QuickBooks rather than your synced copy, so it takes a callbackUrl in the query string and posts the record there when the lookup finishes.

Query

projectIdprojectNamecallbackUrl

Reading project history in bulk is the Projects Dataset's job rather than this endpoint's. The dataset is queryable without spending a run.

Every call

The fields each request carries

Two fields sit outside the project itself and decide how you hear about the result. Both are accepted on create and update, and validated before the run is queued.

Field

Requirement

What it does

Authorization

required

Bearer followed by your API key. Keys are generated in the Clickr dashboard and revoked there.

projectName

required

The project name as it will read in QuickBooks. On an update it renames the project.

customerName

required

An existing QuickBooks customer, matched by name. The project is created underneath it.

startDate / endDate

optional

MM/DD/YYYY. Anything else is rejected before the run starts.

status

optional

One of not-started, in-progress, completed or canceled.

customFields

optional

A list, each entry carrying label, value and a fieldType of text or dropdown.

statusCallbackUrl

optional

Where Clickr posts the finished project and the run status once the run completes.

metaData

optional

A JSON object of your own, returned untouched on the callback. Use it to match a result to the job that triggered it.

8 FIELDS

billingAddress and shippingAddress take country, streetAddress1, city, state and zipCode, and each of those is required once the address is present.

Setting it up

Connect an account, set the second factor, post a project

Setup is self-serve and nothing in it waits on us. We are happy to walk you through it on a call if you would prefer.

01

Connect your QuickBooks account

Add your credentials in the Clickr dashboard. Clickr does not create a user inside your QuickBooks account, and you can revoke its access from your own settings.

about a minute

02

Point multi-factor authentication at Clickr

Intuit requires a second factor. We give you a phone number to set as it, and Clickr answers the sign-in challenge on every run from then on.

one settings change

03

Post your first project

Generate an API key, then call the endpoint from curl, Zapier, n8n, your own code or an AI assistant. The run appears in your history with its status, duration and any error.

same day

Questions about this endpoint

Questions about the connector as a whole, including pricing and what happens when a run fails, are answered on the QuickBooks page.

support@clickr.cloud

Not through Intuit's own. Their accounting API covers customers, invoices, estimates, items and payments, and Projects is not among them. Clickr's endpoint creates the project by driving the same screens your team uses, so the record lands where it would if someone had typed it.

Yes. A project in QuickBooks belongs to a customer, so pass customerName exactly as it reads in your account. If nothing matches, the run fails with that reason in your run history rather than creating a second customer.

No. The endpoint returns a receipt as soon as the run is queued, and Clickr posts the finished record to the statusCallbackUrl you send. The receipt is what matches the callback back to the call that caused it.

Yes, on the Velocity plan. Send projectNameIdentifier instead of projectId and Clickr resolves the project by name. On Standard the projectId is required.

Yes. Pass customFields as a list, each carrying a label, a value and a fieldType of text or dropdown, and Clickr fills the same fields your team fills in on the project form.

Dates are MM/DD/YYYY. Status is one of not-started, in-progress, completed or canceled, and anything else is rejected before the run starts rather than failing halfway through.

Every call that touches QuickBooks: a create, an update or a lookup. Standard covers up to 100 runs a day, Velocity up to 500.

Yes. The QuickBooks Projects Dataset keeps a synced, queryable copy of your project history, resynced every 10 minutes and readable from the dashboard or the REST API.

Yes. It is an ordinary HTTPS request with a bearer token, so any of them can call it as an action step. Claude, ChatGPT and Cursor can reach the same operations over our MCP server.

9 questions · updated as we are asked new ones

More on our QuickBooks connector

The rest of the connector

Projects are one of two actions on the connector. The estimate conversion, the change webhook and the one-time history export each have their own page.

Overview

QuickBooks Connector

Both actions, the Projects Dataset, the ways to reach them, and what it costs.

Action

QuickBooks Estimates API

Convert an estimate into an invoice over HTTP, in full or in part.

Access

QuickBooks Webhook

Clickr posts project changes to any URL you choose. Zapier, Make and n8n can consume it directly.

Access

QuickBooks MCP server

Connect Claude, ChatGPT or Cursor and create projects or convert estimates in plain English.

Service

QuickBooks Data Export

A one-time export of your full accounting history as CSV and Excel.

Create your first project over HTTP

Connect the QuickBooks account you already have, generate an API key, and post a project today. The trial runs for 7 days and you can cancel at any time.

Start free trialTalk to us

or email support@clickr.cloud with a question first