[QuickBooks Online] Account List detail — the chart of accounts with type, detail type and balance. Report parameters are the vendor's own name=value pairs, passed through as a JSON object — for example {"start_date":"2026-01-01","end_date":"2026-03-31"}.

[QuickBooks Online] Balance Sheet — assets, liabilities and equity as at a date. Report parameters are the vendor's own name=value pairs, passed through as a JSON object — for example {"start_date":"2026-01-01","end_date":"2026-03-31"}.

[QuickBooks Online] Statement of Cash Flows — operating, investing and financing movement for a period. Report parameters are the vendor's own name=value pairs, passed through as a JSON object — for example {"start_date":"2026-01-01","end_date":"2026-03-31"}.

[QuickBooks Online] General Ledger detail — every posting, account by account. This is the largest report in the set; narrow it with a date window. Report parameters are the vendor's own name=value pairs, passed through as a JSON object — for example {"start_date":"2026-01-01","end_date":"2026-03-31"}.

[QuickBooks Online] Journal report — transactions in journal form with their debit and credit splits. Report parameters are the vendor's own name=value pairs, passed through as a JSON object — for example {"start_date":"2026-01-01","end_date":"2026-03-31"}.

[QuickBooks Online] Profit and Loss summary — income, cost of goods sold, expenses and net income for a period. The vendor's own sample uses start_date, end_date and customer (for example start_date=2026-01-01&end_date=2026-03-31). Report parameters are the vendor's own name=value pairs, passed through as a JSON object — for example {"start_date":"2026-01-01","end_date":"2026-03-31"}.

[QuickBooks Online] Profit and Loss detail — every transaction behind each income and expense line. The vendor's sample names customer and class. Report parameters are the vendor's own name=value pairs, passed through as a JSON object — for example {"start_date":"2026-01-01","end_date":"2026-03-31"}.

[QuickBooks Online] Trial Balance — every account with its debit and credit totals. Report parameters are the vendor's own name=value pairs, passed through as a JSON object — for example {"start_date":"2026-01-01","end_date":"2026-03-31"}.

[QuickBooks Online] A/R Aging detail — the individual open invoices behind each aging bucket. Report parameters are the vendor's own name=value pairs, passed through as a JSON object — for example {"start_date":"2026-01-01","end_date":"2026-03-31"}.

[QuickBooks Online] A/R Aging summary — what each customer owes, bucketed by how overdue it is. The collections report. Report parameters are the vendor's own name=value pairs, passed through as a JSON object — for example {"start_date":"2026-01-01","end_date":"2026-03-31"}.

[QuickBooks Online] Customer Balances — the outstanding balance per customer. The vendor's sample names customer and class. Report parameters are the vendor's own name=value pairs, passed through as a JSON object — for example {"start_date":"2026-01-01","end_date":"2026-03-31"}.

[QuickBooks Online] Customer Balance detail — the open transactions making up each customer's balance. Report parameters are the vendor's own name=value pairs, passed through as a JSON object — for example {"start_date":"2026-01-01","end_date":"2026-03-31"}.

[QuickBooks Online] Income by Customer — revenue and expense per customer, the profitability-by-client read. Report parameters are the vendor's own name=value pairs, passed through as a JSON object — for example {"start_date":"2026-01-01","end_date":"2026-03-31"}.

[QuickBooks Online] A/P Aging detail — the individual open bills behind each aging bucket. Report parameters are the vendor's own name=value pairs, passed through as a JSON object — for example {"start_date":"2026-01-01","end_date":"2026-03-31"}.

[QuickBooks Online] A/P Aging summary — what you owe each vendor, bucketed by how overdue it is. Report parameters are the vendor's own name=value pairs, passed through as a JSON object — for example {"start_date":"2026-01-01","end_date":"2026-03-31"}.

[QuickBooks Online] Vendor Balances — the outstanding balance per vendor. Report parameters are the vendor's own name=value pairs, passed through as a JSON object — for example {"start_date":"2026-01-01","end_date":"2026-03-31"}.

[QuickBooks Online] Vendor Balance detail — the open transactions making up each vendor's balance. The vendor's sample names vendor and class. Report parameters are the vendor's own name=value pairs, passed through as a JSON object — for example {"start_date":"2026-01-01","end_date":"2026-03-31"}.

[QuickBooks Online] Expenses by Vendor — spend per vendor for a period. Report parameters are the vendor's own name=value pairs, passed through as a JSON object — for example {"start_date":"2026-01-01","end_date":"2026-03-31"}.

[QuickBooks Online] Sales by Class summary — revenue per class. Report parameters are the vendor's own name=value pairs, passed through as a JSON object — for example {"start_date":"2026-01-01","end_date":"2026-03-31"}.

[QuickBooks Online] Sales by Customer — revenue per customer for a period. The vendor's sample names customer and class. Report parameters are the vendor's own name=value pairs, passed through as a JSON object — for example {"start_date":"2026-01-01","end_date":"2026-03-31"}.

[QuickBooks Online] Sales by Department — revenue per location or department. Report parameters are the vendor's own name=value pairs, passed through as a JSON object — for example {"start_date":"2026-01-01","end_date":"2026-03-31"}.

[QuickBooks Online] Sales by Product/Service — revenue and quantity per item. Report parameters are the vendor's own name=value pairs, passed through as a JSON object — for example {"start_date":"2026-01-01","end_date":"2026-03-31"}.

[QuickBooks Online] Transaction List — every transaction in a period, across types. Report parameters are the vendor's own name=value pairs, passed through as a JSON object — for example {"start_date":"2026-01-01","end_date":"2026-03-31"}.

[QuickBooks Online] Transaction List by Customer — every transaction grouped by customer. Report parameters are the vendor's own name=value pairs, passed through as a JSON object — for example {"start_date":"2026-01-01","end_date":"2026-03-31"}.

[QuickBooks Online] Transaction List by Vendor — every transaction grouped by vendor. Report parameters are the vendor's own name=value pairs, passed through as a JSON object — for example {"start_date":"2026-01-01","end_date":"2026-03-31"}.

[QuickBooks Online] Transaction List with Splits — transactions with each of their ledger splits. Report parameters are the vendor's own name=value pairs, passed through as a JSON object — for example {"start_date":"2026-01-01","end_date":"2026-03-31"}.

[QuickBooks Online] Inventory Valuation detail — the movements behind each item's valuation. Report parameters are the vendor's own name=value pairs, passed through as a JSON object — for example {"start_date":"2026-01-01","end_date":"2026-03-31"}.

[QuickBooks Online] Inventory Valuation summary — quantity on hand and asset value per inventory item. Report parameters are the vendor's own name=value pairs, passed through as a JSON object — for example {"start_date":"2026-01-01","end_date":"2026-03-31"}.

[QuickBooks Online] Tax Summary. Applicable to NON-US companies only — a US company gets an error rather than an empty report. Report parameters are the vendor's own name=value pairs, passed through as a JSON object — for example {"start_date":"2026-01-01","end_date":"2026-03-31"}.

[QuickBooks Online] Create a customer. A customer is the company or person you invoice. The record carries the billing and shipping addresses, terms, tax code, currency, notes and the running Balance. body is the entity record as a JSON object, the same shape a read returns.

[QuickBooks Online] FULL update of a customer. DATA LOSS WARNING: QuickBooks sets every writable field you omit to NULL, so the body must repeat the whole record exactly as a read returned it. Prefer qbo_update_customer, which changes only what you send. A customer is the company or person you invoice. The record carries the billing and shipping addresses, terms, tax code, currency, notes and the running Balance. body is the entity record as a JSON object, the same shape a read returns. The body must carry the record's Id and SyncToken. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] Read one customer by its QuickBooks Id, including the SyncToken every update must echo back. A customer is the company or person you invoice. The record carries the billing and shipping addresses, terms, tax code, currency, notes and the running Balance.

[QuickBooks Online] Read one customer type by its QuickBooks Id. A customer type categorizes customers the way the business thinks of them - by industry, by region, or by how they found you - for reporting and mailings. READ-ONLY through the API: Intuit publishes no create, update or delete for this resource.

[QuickBooks Online] List customer types with an optional WHERE clause. A customer type categorizes customers the way the business thinks of them - by industry, by region, or by how they found you - for reporting and mailings. READ-ONLY through the API: Intuit publishes no create, update or delete for this resource. The WHERE fragment is QuickBooks query syntax, not SQL: no OR, no JOIN, LIKE with only the % wildcard, Id only with = or IN, and string literals in single quotes. Paging is STARTPOSITION/MAXRESULTS inside the query — there is no cursor and no total, so a page shorter than maxResults is the last one. maxResults is capped at 1000.

[QuickBooks Online] List customers with an optional WHERE clause. A customer is the company or person you invoice. The record carries the billing and shipping addresses, terms, tax code, currency, notes and the running Balance. The WHERE fragment is QuickBooks query syntax, not SQL: no OR, no JOIN, LIKE with only the % wildcard, Id only with = or IN, and string literals in single quotes. Paging is STARTPOSITION/MAXRESULTS inside the query — there is no cursor and no total, so a page shorter than maxResults is the last one. maxResults is capped at 1000.

[QuickBooks Online] SPARSE update of a customer — only the fields you send are changed and every omitted field is left alone. This is the safe update and the one to reach for. A customer is the company or person you invoice. The record carries the billing and shipping addresses, terms, tax code, currency, notes and the running Balance. body is the entity record as a JSON object, the same shape a read returns. The body must carry the record's Id and SyncToken. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] Create an invoice. An invoice is a sale on credit — what a customer owes you and when. Line items reference Items, and the Balance field is what is still outstanding. body is the entity record as a JSON object, the same shape a read returns.

[QuickBooks Online] Delete an invoice. This removes the transaction from the company's books and cannot be undone; where the entity can be VOIDED instead, voiding keeps the audit trail and is usually what an accountant wants. An invoice is a sale on credit — what a customer owes you and when. Line items reference Items, and the Balance field is what is still outstanding. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] FULL update of an invoice. DATA LOSS WARNING: QuickBooks sets every writable field you omit to NULL, so the body must repeat the whole record exactly as a read returned it. Prefer qbo_update_invoice, which changes only what you send. An invoice is a sale on credit — what a customer owes you and when. Line items reference Items, and the Balance field is what is still outstanding. body is the entity record as a JSON object, the same shape a read returns. The body must carry the record's Id and SyncToken. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] Read one invoice by its QuickBooks Id, including the SyncToken every update must echo back. An invoice is a sale on credit — what a customer owes you and when. Line items reference Items, and the Balance field is what is still outstanding.

[QuickBooks Online] Download the rendered PDF of an invoice. A file cannot cross the tool surface, so the answer is a JSON envelope carrying a TEMPORARY download link valid for 15 minutes, the content type, a suggested file name, the exact byte count and the expiry — fetch the link before it expires, because StackJack keeps no other copy. QuickBooks renders the document on demand from the transaction as it stands now and the company's current template, so it is a render rather than a stored copy.

[QuickBooks Online] List invoices with an optional WHERE clause. An invoice is a sale on credit — what a customer owes you and when. Line items reference Items, and the Balance field is what is still outstanding. The WHERE fragment is QuickBooks query syntax, not SQL: no OR, no JOIN, LIKE with only the % wildcard, Id only with = or IN, and string literals in single quotes. Paging is STARTPOSITION/MAXRESULTS inside the query — there is no cursor and no total, so a page shorter than maxResults is the last one. maxResults is capped at 1000.

[QuickBooks Online] EMAIL the invoice to a real person. QuickBooks sends it immediately and there is no recall. Omit sendTo to use the email address stored on the document; supply sendTo to override it. Sending also stamps the document EmailSent.

[QuickBooks Online] SPARSE update of an invoice — only the fields you send are changed and every omitted field is left alone. This is the safe update and the one to reach for. An invoice is a sale on credit — what a customer owes you and when. Line items reference Items, and the Balance field is what is still outstanding. body is the entity record as a JSON object, the same shape a read returns. The body must carry the record's Id and SyncToken. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] Void an invoice. The record stays in the books with zero amounts and a Voided stamp, which preserves the audit trail — but the amounts are gone and it cannot be undone. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] Create an estimate. An estimate is a quote. It does not post to the ledger until it is converted to an invoice. body is the entity record as a JSON object, the same shape a read returns.

[QuickBooks Online] Delete an estimate. This removes the transaction from the company's books and cannot be undone; where the entity can be VOIDED instead, voiding keeps the audit trail and is usually what an accountant wants. An estimate is a quote. It does not post to the ledger until it is converted to an invoice. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] FULL update of an estimate. DATA LOSS WARNING: QuickBooks sets every writable field you omit to NULL, so the body must repeat the whole record exactly as a read returned it. Prefer qbo_update_estimate, which changes only what you send. An estimate is a quote. It does not post to the ledger until it is converted to an invoice. body is the entity record as a JSON object, the same shape a read returns. The body must carry the record's Id and SyncToken. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] Read one estimate by its QuickBooks Id, including the SyncToken every update must echo back. An estimate is a quote. It does not post to the ledger until it is converted to an invoice.

[QuickBooks Online] Download the rendered PDF of an estimate. A file cannot cross the tool surface, so the answer is a JSON envelope carrying a TEMPORARY download link valid for 15 minutes, the content type, a suggested file name, the exact byte count and the expiry — fetch the link before it expires, because StackJack keeps no other copy. QuickBooks renders the document on demand from the transaction as it stands now and the company's current template, so it is a render rather than a stored copy.

[QuickBooks Online] List estimates with an optional WHERE clause. An estimate is a quote. It does not post to the ledger until it is converted to an invoice. The WHERE fragment is QuickBooks query syntax, not SQL: no OR, no JOIN, LIKE with only the % wildcard, Id only with = or IN, and string literals in single quotes. Paging is STARTPOSITION/MAXRESULTS inside the query — there is no cursor and no total, so a page shorter than maxResults is the last one. maxResults is capped at 1000.

[QuickBooks Online] EMAIL the estimate to a real person. QuickBooks sends it immediately and there is no recall. Omit sendTo to use the email address stored on the document; supply sendTo to override it. Sending also stamps the document EmailSent.

[QuickBooks Online] SPARSE update of an estimate — only the fields you send are changed and every omitted field is left alone. This is the safe update and the one to reach for. An estimate is a quote. It does not post to the ledger until it is converted to an invoice. body is the entity record as a JSON object, the same shape a read returns. The body must carry the record's Id and SyncToken. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] Create a sales receipt. A sales receipt is a sale that was paid at the time — no receivable is created. body is the entity record as a JSON object, the same shape a read returns.

[QuickBooks Online] Delete a sales receipt. This removes the transaction from the company's books and cannot be undone; where the entity can be VOIDED instead, voiding keeps the audit trail and is usually what an accountant wants. A sales receipt is a sale that was paid at the time — no receivable is created. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] FULL update of a sales receipt. DATA LOSS WARNING: QuickBooks sets every writable field you omit to NULL, so the body must repeat the whole record exactly as a read returned it. Prefer qbo_update_sales_receipt, which changes only what you send. A sales receipt is a sale that was paid at the time — no receivable is created. body is the entity record as a JSON object, the same shape a read returns. The body must carry the record's Id and SyncToken. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] Read one sales receipt by its QuickBooks Id, including the SyncToken every update must echo back. A sales receipt is a sale that was paid at the time — no receivable is created.

[QuickBooks Online] Download the rendered PDF of a sales receipt. A file cannot cross the tool surface, so the answer is a JSON envelope carrying a TEMPORARY download link valid for 15 minutes, the content type, a suggested file name, the exact byte count and the expiry — fetch the link before it expires, because StackJack keeps no other copy. QuickBooks renders the document on demand from the transaction as it stands now and the company's current template, so it is a render rather than a stored copy.

[QuickBooks Online] List sales receipts with an optional WHERE clause. A sales receipt is a sale that was paid at the time — no receivable is created. The WHERE fragment is QuickBooks query syntax, not SQL: no OR, no JOIN, LIKE with only the % wildcard, Id only with = or IN, and string literals in single quotes. Paging is STARTPOSITION/MAXRESULTS inside the query — there is no cursor and no total, so a page shorter than maxResults is the last one. maxResults is capped at 1000.

[QuickBooks Online] EMAIL the sales receipt to a real person. QuickBooks sends it immediately and there is no recall. Omit sendTo to use the email address stored on the document; supply sendTo to override it. Sending also stamps the document EmailSent.

[QuickBooks Online] SPARSE update of a sales receipt — only the fields you send are changed and every omitted field is left alone. This is the safe update and the one to reach for. A sales receipt is a sale that was paid at the time — no receivable is created. body is the entity record as a JSON object, the same shape a read returns. The body must carry the record's Id and SyncToken. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] Void a sales receipt. The record stays in the books with zero amounts and a Voided stamp, which preserves the audit trail — but the amounts are gone and it cannot be undone. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] Create a payment. A payment records money received from a customer and, through its Line entries, which invoices it settles. body is the entity record as a JSON object, the same shape a read returns.

[QuickBooks Online] Delete a payment. This removes the transaction from the company's books and cannot be undone; where the entity can be VOIDED instead, voiding keeps the audit trail and is usually what an accountant wants. A payment records money received from a customer and, through its Line entries, which invoices it settles. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] FULL update of a payment. DATA LOSS WARNING: QuickBooks sets every writable field you omit to NULL, so the body must repeat the whole record exactly as a read returned it. This entity offers no sparse update, so read the record first and echo every writable field back. A payment records money received from a customer and, through its Line entries, which invoices it settles. body is the entity record as a JSON object, the same shape a read returns. The body must carry the record's Id and SyncToken. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] Read one payment by its QuickBooks Id, including the SyncToken every update must echo back. A payment records money received from a customer and, through its Line entries, which invoices it settles.

[QuickBooks Online] Download the rendered PDF of a payment. A file cannot cross the tool surface, so the answer is a JSON envelope carrying a TEMPORARY download link valid for 15 minutes, the content type, a suggested file name, the exact byte count and the expiry — fetch the link before it expires, because StackJack keeps no other copy. QuickBooks renders the document on demand from the transaction as it stands now and the company's current template, so it is a render rather than a stored copy.

[QuickBooks Online] List payments with an optional WHERE clause. A payment records money received from a customer and, through its Line entries, which invoices it settles. The WHERE fragment is QuickBooks query syntax, not SQL: no OR, no JOIN, LIKE with only the % wildcard, Id only with = or IN, and string literals in single quotes. Paging is STARTPOSITION/MAXRESULTS inside the query — there is no cursor and no total, so a page shorter than maxResults is the last one. maxResults is capped at 1000.

[QuickBooks Online] EMAIL the payment receipt to a real person. QuickBooks sends it immediately and there is no recall. Omit sendTo to use the email address stored on the document; supply sendTo to override it. Sending also stamps the document EmailSent.

[QuickBooks Online] Void a payment. The record stays in the books with zero amounts and a Voided stamp, which preserves the audit trail — but the amounts are gone and it cannot be undone. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] Create a credit memo. A credit memo is a refund or credit of payment, or part of a payment, for goods or services already sold. It reduces what the customer owes. body is the entity record as a JSON object, the same shape a read returns.

[QuickBooks Online] Delete a credit memo. This removes the transaction from the company's books and cannot be undone; where the entity can be VOIDED instead, voiding keeps the audit trail and is usually what an accountant wants. A credit memo is a refund or credit of payment, or part of a payment, for goods or services already sold. It reduces what the customer owes. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] FULL update of a credit memo. DATA LOSS WARNING: QuickBooks sets every writable field you omit to NULL, so the body must repeat the whole record exactly as a read returned it. This entity offers no sparse update, so read the record first and echo every writable field back. A credit memo is a refund or credit of payment, or part of a payment, for goods or services already sold. It reduces what the customer owes. body is the entity record as a JSON object, the same shape a read returns. The body must carry the record's Id and SyncToken. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] Read one credit memo by its QuickBooks Id, including the SyncToken every update must echo back. A credit memo is a refund or credit of payment, or part of a payment, for goods or services already sold. It reduces what the customer owes.

[QuickBooks Online] Download the rendered PDF of a credit memo. A file cannot cross the tool surface, so the answer is a JSON envelope carrying a TEMPORARY download link valid for 15 minutes, the content type, a suggested file name, the exact byte count and the expiry — fetch the link before it expires, because StackJack keeps no other copy. QuickBooks renders the document on demand from the transaction as it stands now and the company's current template, so it is a render rather than a stored copy.

[QuickBooks Online] List credit memos with an optional WHERE clause. A credit memo is a refund or credit of payment, or part of a payment, for goods or services already sold. It reduces what the customer owes. The WHERE fragment is QuickBooks query syntax, not SQL: no OR, no JOIN, LIKE with only the % wildcard, Id only with = or IN, and string literals in single quotes. Paging is STARTPOSITION/MAXRESULTS inside the query — there is no cursor and no total, so a page shorter than maxResults is the last one. maxResults is capped at 1000.

[QuickBooks Online] EMAIL the credit memo to a real person. QuickBooks sends it immediately and there is no recall. Omit sendTo to use the email address stored on the document; supply sendTo to override it. Sending also stamps the document EmailSent.

[QuickBooks Online] Create a refund receipt. A refund receipt records money given back to a customer for a product or service that was provided. body is the entity record as a JSON object, the same shape a read returns.

[QuickBooks Online] Delete a refund receipt. This removes the transaction from the company's books and cannot be undone; where the entity can be VOIDED instead, voiding keeps the audit trail and is usually what an accountant wants. A refund receipt records money given back to a customer for a product or service that was provided. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] FULL update of a refund receipt. DATA LOSS WARNING: QuickBooks sets every writable field you omit to NULL, so the body must repeat the whole record exactly as a read returned it. Prefer qbo_update_refund_receipt, which changes only what you send. A refund receipt records money given back to a customer for a product or service that was provided. body is the entity record as a JSON object, the same shape a read returns. The body must carry the record's Id and SyncToken. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] Read one refund receipt by its QuickBooks Id, including the SyncToken every update must echo back. A refund receipt records money given back to a customer for a product or service that was provided.

[QuickBooks Online] Download the rendered PDF of a refund receipt. A file cannot cross the tool surface, so the answer is a JSON envelope carrying a TEMPORARY download link valid for 15 minutes, the content type, a suggested file name, the exact byte count and the expiry — fetch the link before it expires, because StackJack keeps no other copy. QuickBooks renders the document on demand from the transaction as it stands now and the company's current template, so it is a render rather than a stored copy.

[QuickBooks Online] List refund receipts with an optional WHERE clause. A refund receipt records money given back to a customer for a product or service that was provided. The WHERE fragment is QuickBooks query syntax, not SQL: no OR, no JOIN, LIKE with only the % wildcard, Id only with = or IN, and string literals in single quotes. Paging is STARTPOSITION/MAXRESULTS inside the query — there is no cursor and no total, so a page shorter than maxResults is the last one. maxResults is capped at 1000.

[QuickBooks Online] EMAIL the refund receipt to a real person. QuickBooks sends it immediately and there is no recall. Omit sendTo to use the email address stored on the document; supply sendTo to override it. Sending also stamps the document EmailSent.

[QuickBooks Online] SPARSE update of a refund receipt — only the fields you send are changed and every omitted field is left alone. This is the safe update and the one to reach for. A refund receipt records money given back to a customer for a product or service that was provided. body is the entity record as a JSON object, the same shape a read returns. The body must carry the record's Id and SyncToken. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] Create a change order. A change order is a modification to the scope of work on an existing project estimate - additions or deletions to the contracted work that roll up into the project's total budget alongside the parent estimate. PRODUCT-GATED: US companies on QuickBooks Online Advanced with the Construction Pack, or Intuit Enterprise Suite, with the Projects feature enabled. Other companies get an error rather than an empty result. body is the entity record as a JSON object, the same shape a read returns.

[QuickBooks Online] Delete a change order. This removes the transaction from the company's books and cannot be undone; where the entity can be VOIDED instead, voiding keeps the audit trail and is usually what an accountant wants. A change order is a modification to the scope of work on an existing project estimate - additions or deletions to the contracted work that roll up into the project's total budget alongside the parent estimate. PRODUCT-GATED: US companies on QuickBooks Online Advanced with the Construction Pack, or Intuit Enterprise Suite, with the Projects feature enabled. Other companies get an error rather than an empty result. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] FULL update of a change order. DATA LOSS WARNING: QuickBooks sets every writable field you omit to NULL, so the body must repeat the whole record exactly as a read returned it. This entity offers no sparse update, so read the record first and echo every writable field back. A change order is a modification to the scope of work on an existing project estimate - additions or deletions to the contracted work that roll up into the project's total budget alongside the parent estimate. PRODUCT-GATED: US companies on QuickBooks Online Advanced with the Construction Pack, or Intuit Enterprise Suite, with the Projects feature enabled. Other companies get an error rather than an empty result. body is the entity record as a JSON object, the same shape a read returns. The body must carry the record's Id and SyncToken. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] Read one change order by its QuickBooks Id, including the SyncToken every update must echo back. A change order is a modification to the scope of work on an existing project estimate - additions or deletions to the contracted work that roll up into the project's total budget alongside the parent estimate. PRODUCT-GATED: US companies on QuickBooks Online Advanced with the Construction Pack, or Intuit Enterprise Suite, with the Projects feature enabled. Other companies get an error rather than an empty result.

[QuickBooks Online] Create a payment method. A payment method is how money was received (cash, cheque, a card type). It cannot be deleted: set Active to false in an update to hide it, which leaves references to it intact. body is the entity record as a JSON object, the same shape a read returns.

[QuickBooks Online] Create a term. A term is the sales terms a document is issued under - net 30, or 2%/15 net 60, or an absolute due date - including any early-payment discount. body is the entity record as a JSON object, the same shape a read returns.

[QuickBooks Online] FULL update of a payment method. DATA LOSS WARNING: QuickBooks sets every writable field you omit to NULL, so the body must repeat the whole record exactly as a read returned it. This entity offers no sparse update, so read the record first and echo every writable field back. A payment method is how money was received (cash, cheque, a card type). It cannot be deleted: set Active to false in an update to hide it, which leaves references to it intact. body is the entity record as a JSON object, the same shape a read returns. The body must carry the record's Id and SyncToken. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] FULL update of a term. DATA LOSS WARNING: QuickBooks sets every writable field you omit to NULL, so the body must repeat the whole record exactly as a read returned it. This entity offers no sparse update, so read the record first and echo every writable field back. A term is the sales terms a document is issued under - net 30, or 2%/15 net 60, or an absolute due date - including any early-payment discount. body is the entity record as a JSON object, the same shape a read returns. The body must carry the record's Id and SyncToken. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] Read one payment method by its QuickBooks Id, including the SyncToken every update must echo back. A payment method is how money was received (cash, cheque, a card type). It cannot be deleted: set Active to false in an update to hide it, which leaves references to it intact.

[QuickBooks Online] Read one term by its QuickBooks Id, including the SyncToken every update must echo back. A term is the sales terms a document is issued under - net 30, or 2%/15 net 60, or an absolute due date - including any early-payment discount.

[QuickBooks Online] List payment methods with an optional WHERE clause. A payment method is how money was received (cash, cheque, a card type). It cannot be deleted: set Active to false in an update to hide it, which leaves references to it intact. The WHERE fragment is QuickBooks query syntax, not SQL: no OR, no JOIN, LIKE with only the % wildcard, Id only with = or IN, and string literals in single quotes. Paging is STARTPOSITION/MAXRESULTS inside the query — there is no cursor and no total, so a page shorter than maxResults is the last one. maxResults is capped at 1000.

[QuickBooks Online] List terms with an optional WHERE clause. A term is the sales terms a document is issued under - net 30, or 2%/15 net 60, or an absolute due date - including any early-payment discount. The WHERE fragment is QuickBooks query syntax, not SQL: no OR, no JOIN, LIKE with only the % wildcard, Id only with = or IN, and string literals in single quotes. Paging is STARTPOSITION/MAXRESULTS inside the query — there is no cursor and no total, so a page shorter than maxResults is the last one. maxResults is capped at 1000.

[QuickBooks Online] Read one reimbursable charge by its QuickBooks Id. A reimbursable charge is a billable expense - an expense or bill line marked Billable to a customer, waiting to be invoiced. READ-ONLY through the API.

[QuickBooks Online] List reimburse charges with an optional WHERE clause. A reimbursable charge is a billable expense - an expense or bill line marked Billable to a customer, waiting to be invoiced. READ-ONLY through the API. The WHERE fragment is QuickBooks query syntax, not SQL: no OR, no JOIN, LIKE with only the % wildcard, Id only with = or IN, and string literals in single quotes. Paging is STARTPOSITION/MAXRESULTS inside the query — there is no cursor and no total, so a page shorter than maxResults is the last one. maxResults is capped at 1000.

[QuickBooks Online] Create a vendor. A vendor is someone you buy from. The record carries the remit-to address, terms, tax id and the running Balance. body is the entity record as a JSON object, the same shape a read returns.

[QuickBooks Online] FULL update of a vendor. DATA LOSS WARNING: QuickBooks sets every writable field you omit to NULL, so the body must repeat the whole record exactly as a read returned it. This entity offers no sparse update, so read the record first and echo every writable field back. A vendor is someone you buy from. The record carries the remit-to address, terms, tax id and the running Balance. body is the entity record as a JSON object, the same shape a read returns. The body must carry the record's Id and SyncToken. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] Read one vendor by its QuickBooks Id, including the SyncToken every update must echo back. A vendor is someone you buy from. The record carries the remit-to address, terms, tax id and the running Balance.

[QuickBooks Online] List vendors with an optional WHERE clause. A vendor is someone you buy from. The record carries the remit-to address, terms, tax id and the running Balance. The WHERE fragment is QuickBooks query syntax, not SQL: no OR, no JOIN, LIKE with only the % wildcard, Id only with = or IN, and string literals in single quotes. Paging is STARTPOSITION/MAXRESULTS inside the query — there is no cursor and no total, so a page shorter than maxResults is the last one. maxResults is capped at 1000.

[QuickBooks Online] Create a bill. A bill is a purchase on credit — what you owe a vendor and when. body is the entity record as a JSON object, the same shape a read returns.

[QuickBooks Online] Delete a bill. This removes the transaction from the company's books and cannot be undone; where the entity can be VOIDED instead, voiding keeps the audit trail and is usually what an accountant wants. A bill is a purchase on credit — what you owe a vendor and when. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] FULL update of a bill. DATA LOSS WARNING: QuickBooks sets every writable field you omit to NULL, so the body must repeat the whole record exactly as a read returned it. This entity offers no sparse update, so read the record first and echo every writable field back. A bill is a purchase on credit — what you owe a vendor and when. body is the entity record as a JSON object, the same shape a read returns. The body must carry the record's Id and SyncToken. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] Read one bill by its QuickBooks Id, including the SyncToken every update must echo back. A bill is a purchase on credit — what you owe a vendor and when.

[QuickBooks Online] List bills with an optional WHERE clause. A bill is a purchase on credit — what you owe a vendor and when. The WHERE fragment is QuickBooks query syntax, not SQL: no OR, no JOIN, LIKE with only the % wildcard, Id only with = or IN, and string literals in single quotes. Paging is STARTPOSITION/MAXRESULTS inside the query — there is no cursor and no total, so a page shorter than maxResults is the last one. maxResults is capped at 1000.

[QuickBooks Online] Create a bill payment. A bill payment records money paid to a vendor and, through its Line entries, which bills it settles. body is the entity record as a JSON object, the same shape a read returns.

[QuickBooks Online] Delete a bill payment. This removes the transaction from the company's books and cannot be undone; where the entity can be VOIDED instead, voiding keeps the audit trail and is usually what an accountant wants. A bill payment records money paid to a vendor and, through its Line entries, which bills it settles. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] FULL update of a bill payment. DATA LOSS WARNING: QuickBooks sets every writable field you omit to NULL, so the body must repeat the whole record exactly as a read returned it. This entity offers no sparse update, so read the record first and echo every writable field back. A bill payment records money paid to a vendor and, through its Line entries, which bills it settles. body is the entity record as a JSON object, the same shape a read returns. The body must carry the record's Id and SyncToken. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] Read one bill payment by its QuickBooks Id, including the SyncToken every update must echo back. A bill payment records money paid to a vendor and, through its Line entries, which bills it settles.

[QuickBooks Online] List bill payments with an optional WHERE clause. A bill payment records money paid to a vendor and, through its Line entries, which bills it settles. The WHERE fragment is QuickBooks query syntax, not SQL: no OR, no JOIN, LIKE with only the % wildcard, Id only with = or IN, and string literals in single quotes. Paging is STARTPOSITION/MAXRESULTS inside the query — there is no cursor and no total, so a page shorter than maxResults is the last one. maxResults is capped at 1000.

[QuickBooks Online] Void a bill payment. The record stays in the books with zero amounts and a Voided stamp, which preserves the audit trail — but the amounts are gone and it cannot be undone. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] Create a purchase. A purchase is an expense paid at the time - by cash, cheque or credit card, set by PaymentType. Every purchase must name an AccountRef, and TotalAmt must equal the sum of its line amounts. body is the entity record as a JSON object, the same shape a read returns.

[QuickBooks Online] Delete a purchase. This removes the transaction from the company's books and cannot be undone; where the entity can be VOIDED instead, voiding keeps the audit trail and is usually what an accountant wants. A purchase is an expense paid at the time - by cash, cheque or credit card, set by PaymentType. Every purchase must name an AccountRef, and TotalAmt must equal the sum of its line amounts. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] FULL update of a purchase. DATA LOSS WARNING: QuickBooks sets every writable field you omit to NULL, so the body must repeat the whole record exactly as a read returned it. This entity offers no sparse update, so read the record first and echo every writable field back. A purchase is an expense paid at the time - by cash, cheque or credit card, set by PaymentType. Every purchase must name an AccountRef, and TotalAmt must equal the sum of its line amounts. body is the entity record as a JSON object, the same shape a read returns. The body must carry the record's Id and SyncToken. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] Read one purchase by its QuickBooks Id, including the SyncToken every update must echo back. A purchase is an expense paid at the time - by cash, cheque or credit card, set by PaymentType. Every purchase must name an AccountRef, and TotalAmt must equal the sum of its line amounts.

[QuickBooks Online] List purchases with an optional WHERE clause. A purchase is an expense paid at the time - by cash, cheque or credit card, set by PaymentType. Every purchase must name an AccountRef, and TotalAmt must equal the sum of its line amounts. The WHERE fragment is QuickBooks query syntax, not SQL: no OR, no JOIN, LIKE with only the % wildcard, Id only with = or IN, and string literals in single quotes. Paging is STARTPOSITION/MAXRESULTS inside the query — there is no cursor and no total, so a page shorter than maxResults is the last one. maxResults is capped at 1000.

[QuickBooks Online] Create a purchase order. A purchase order is a NON-POSTING request to buy goods or services from a third party. It changes no balance until it is matched to a bill. body is the entity record as a JSON object, the same shape a read returns.

[QuickBooks Online] Delete a purchase order. This removes the transaction from the company's books and cannot be undone; where the entity can be VOIDED instead, voiding keeps the audit trail and is usually what an accountant wants. A purchase order is a NON-POSTING request to buy goods or services from a third party. It changes no balance until it is matched to a bill. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] FULL update of a purchase order. DATA LOSS WARNING: QuickBooks sets every writable field you omit to NULL, so the body must repeat the whole record exactly as a read returned it. This entity offers no sparse update, so read the record first and echo every writable field back. A purchase order is a NON-POSTING request to buy goods or services from a third party. It changes no balance until it is matched to a bill. body is the entity record as a JSON object, the same shape a read returns. The body must carry the record's Id and SyncToken. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] Read one purchase order by its QuickBooks Id, including the SyncToken every update must echo back. A purchase order is a NON-POSTING request to buy goods or services from a third party. It changes no balance until it is matched to a bill.

[QuickBooks Online] Download the rendered PDF of a purchase order. A file cannot cross the tool surface, so the answer is a JSON envelope carrying a TEMPORARY download link valid for 15 minutes, the content type, a suggested file name, the exact byte count and the expiry — fetch the link before it expires, because StackJack keeps no other copy. QuickBooks renders the document on demand from the transaction as it stands now and the company's current template, so it is a render rather than a stored copy.

[QuickBooks Online] List purchase orders with an optional WHERE clause. A purchase order is a NON-POSTING request to buy goods or services from a third party. It changes no balance until it is matched to a bill. The WHERE fragment is QuickBooks query syntax, not SQL: no OR, no JOIN, LIKE with only the % wildcard, Id only with = or IN, and string literals in single quotes. Paging is STARTPOSITION/MAXRESULTS inside the query — there is no cursor and no total, so a page shorter than maxResults is the last one. maxResults is capped at 1000.

[QuickBooks Online] EMAIL the purchase order to a real person. QuickBooks sends it immediately and there is no recall. Omit sendTo to use the email address stored on the document; supply sendTo to override it. Sending also stamps the document EmailSent. The recipient of this one is your VENDOR, not a customer.

[QuickBooks Online] Create a vendor credit. A vendor credit is an accounts-payable transaction recording a refund or credit a vendor owes you - an overpaid bill, returned merchandise, and so on. body is the entity record as a JSON object, the same shape a read returns.

[QuickBooks Online] Delete a vendor credit. This removes the transaction from the company's books and cannot be undone; where the entity can be VOIDED instead, voiding keeps the audit trail and is usually what an accountant wants. A vendor credit is an accounts-payable transaction recording a refund or credit a vendor owes you - an overpaid bill, returned merchandise, and so on. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] FULL update of a vendor credit. DATA LOSS WARNING: QuickBooks sets every writable field you omit to NULL, so the body must repeat the whole record exactly as a read returned it. This entity offers no sparse update, so read the record first and echo every writable field back. A vendor credit is an accounts-payable transaction recording a refund or credit a vendor owes you - an overpaid bill, returned merchandise, and so on. body is the entity record as a JSON object, the same shape a read returns. The body must carry the record's Id and SyncToken. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] Read one vendor credit by its QuickBooks Id, including the SyncToken every update must echo back. A vendor credit is an accounts-payable transaction recording a refund or credit a vendor owes you - an overpaid bill, returned merchandise, and so on.

[QuickBooks Online] List vendor credits with an optional WHERE clause. A vendor credit is an accounts-payable transaction recording a refund or credit a vendor owes you - an overpaid bill, returned merchandise, and so on. The WHERE fragment is QuickBooks query syntax, not SQL: no OR, no JOIN, LIKE with only the % wildcard, Id only with = or IN, and string literals in single quotes. Paging is STARTPOSITION/MAXRESULTS inside the query — there is no cursor and no total, so a page shorter than maxResults is the last one. maxResults is capped at 1000.

[QuickBooks Online] Create an account. An account is a line in the chart of accounts. Deleting one is NOT possible: set Active to false with an update instead, which hides it without removing its history. body is the entity record as a JSON object, the same shape a read returns.

[QuickBooks Online] FULL update of an account. DATA LOSS WARNING: QuickBooks sets every writable field you omit to NULL, so the body must repeat the whole record exactly as a read returned it. This entity offers no sparse update, so read the record first and echo every writable field back. An account is a line in the chart of accounts. Deleting one is NOT possible: set Active to false with an update instead, which hides it without removing its history. body is the entity record as a JSON object, the same shape a read returns. The body must carry the record's Id and SyncToken. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] Read one account by its QuickBooks Id, including the SyncToken every update must echo back. An account is a line in the chart of accounts. Deleting one is NOT possible: set Active to false with an update instead, which hides it without removing its history.

[QuickBooks Online] List accounts with an optional WHERE clause. An account is a line in the chart of accounts. Deleting one is NOT possible: set Active to false with an update instead, which hides it without removing its history. The WHERE fragment is QuickBooks query syntax, not SQL: no OR, no JOIN, LIKE with only the % wildcard, Id only with = or IN, and string literals in single quotes. Paging is STARTPOSITION/MAXRESULTS inside the query — there is no cursor and no total, so a page shorter than maxResults is the last one. maxResults is capped at 1000.

[QuickBooks Online] Create a journal entry. A journal entry posts debits and credits directly to accounts. Totals must balance or QuickBooks rejects it. body is the entity record as a JSON object, the same shape a read returns.

[QuickBooks Online] Delete a journal entry. This removes the transaction from the company's books and cannot be undone; where the entity can be VOIDED instead, voiding keeps the audit trail and is usually what an accountant wants. A journal entry posts debits and credits directly to accounts. Totals must balance or QuickBooks rejects it. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] FULL update of a journal entry. DATA LOSS WARNING: QuickBooks sets every writable field you omit to NULL, so the body must repeat the whole record exactly as a read returned it. Prefer qbo_update_journal_entry, which changes only what you send. A journal entry posts debits and credits directly to accounts. Totals must balance or QuickBooks rejects it. body is the entity record as a JSON object, the same shape a read returns. The body must carry the record's Id and SyncToken. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] Read one journal entry by its QuickBooks Id, including the SyncToken every update must echo back. A journal entry posts debits and credits directly to accounts. Totals must balance or QuickBooks rejects it.

[QuickBooks Online] List journal entries with an optional WHERE clause. A journal entry posts debits and credits directly to accounts. Totals must balance or QuickBooks rejects it. The WHERE fragment is QuickBooks query syntax, not SQL: no OR, no JOIN, LIKE with only the % wildcard, Id only with = or IN, and string literals in single quotes. Paging is STARTPOSITION/MAXRESULTS inside the query — there is no cursor and no total, so a page shorter than maxResults is the last one. maxResults is capped at 1000.

[QuickBooks Online] SPARSE update of a journal entry — only the fields you send are changed and every omitted field is left alone. This is the safe update and the one to reach for. A journal entry posts debits and credits directly to accounts. Totals must balance or QuickBooks rejects it. body is the entity record as a JSON object, the same shape a read returns. The body must carry the record's Id and SyncToken. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] Create an item. An item is a product or service you sell or buy. Categories and bundles are Items too — they differ only by the Type field on the same endpoint. body is the entity record as a JSON object, the same shape a read returns.

[QuickBooks Online] FULL update of an item. DATA LOSS WARNING: QuickBooks sets every writable field you omit to NULL, so the body must repeat the whole record exactly as a read returned it. This entity offers no sparse update, so read the record first and echo every writable field back. An item is a product or service you sell or buy. Categories and bundles are Items too — they differ only by the Type field on the same endpoint. body is the entity record as a JSON object, the same shape a read returns. The body must carry the record's Id and SyncToken. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] Read one item by its QuickBooks Id, including the SyncToken every update must echo back. An item is a product or service you sell or buy. Categories and bundles are Items too — they differ only by the Type field on the same endpoint.

[QuickBooks Online] List items with an optional WHERE clause. An item is a product or service you sell or buy. Categories and bundles are Items too — they differ only by the Type field on the same endpoint. The WHERE fragment is QuickBooks query syntax, not SQL: no OR, no JOIN, LIKE with only the % wildcard, Id only with = or IN, and string literals in single quotes. Paging is STARTPOSITION/MAXRESULTS inside the query — there is no cursor and no total, so a page shorter than maxResults is the last one. maxResults is capped at 1000.

[QuickBooks Online] Create a class. A class tracks a segment of the business that is not tied to one client or project, so income and expense can be broken down by segment. A class applies to a whole transaction or to individual lines. Requires class tracking to be switched on in the company's preferences. body is the entity record as a JSON object, the same shape a read returns.

[QuickBooks Online] Create a department. A department tracks transactions by physical location - a store, a sales region, a country. It cannot be deleted: set Active to false in an update, which hides it and leaves references intact. body is the entity record as a JSON object, the same shape a read returns.

[QuickBooks Online] FULL update of a class. DATA LOSS WARNING: QuickBooks sets every writable field you omit to NULL, so the body must repeat the whole record exactly as a read returned it. This entity offers no sparse update, so read the record first and echo every writable field back. A class tracks a segment of the business that is not tied to one client or project, so income and expense can be broken down by segment. A class applies to a whole transaction or to individual lines. Requires class tracking to be switched on in the company's preferences. body is the entity record as a JSON object, the same shape a read returns. The body must carry the record's Id and SyncToken. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] FULL update of a department. DATA LOSS WARNING: QuickBooks sets every writable field you omit to NULL, so the body must repeat the whole record exactly as a read returned it. This entity offers no sparse update, so read the record first and echo every writable field back. A department tracks transactions by physical location - a store, a sales region, a country. It cannot be deleted: set Active to false in an update, which hides it and leaves references intact. body is the entity record as a JSON object, the same shape a read returns. The body must carry the record's Id and SyncToken. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] Read one class by its QuickBooks Id, including the SyncToken every update must echo back. A class tracks a segment of the business that is not tied to one client or project, so income and expense can be broken down by segment. A class applies to a whole transaction or to individual lines. Requires class tracking to be switched on in the company's preferences.

[QuickBooks Online] Read one department by its QuickBooks Id, including the SyncToken every update must echo back. A department tracks transactions by physical location - a store, a sales region, a country. It cannot be deleted: set Active to false in an update, which hides it and leaves references intact.

[QuickBooks Online] List classes with an optional WHERE clause. A class tracks a segment of the business that is not tied to one client or project, so income and expense can be broken down by segment. A class applies to a whole transaction or to individual lines. Requires class tracking to be switched on in the company's preferences. The WHERE fragment is QuickBooks query syntax, not SQL: no OR, no JOIN, LIKE with only the % wildcard, Id only with = or IN, and string literals in single quotes. Paging is STARTPOSITION/MAXRESULTS inside the query — there is no cursor and no total, so a page shorter than maxResults is the last one. maxResults is capped at 1000.

[QuickBooks Online] List departments with an optional WHERE clause. A department tracks transactions by physical location - a store, a sales region, a country. It cannot be deleted: set Active to false in an update, which hides it and leaves references intact. The WHERE fragment is QuickBooks query syntax, not SQL: no OR, no JOIN, LIKE with only the % wildcard, Id only with = or IN, and string literals in single quotes. Paging is STARTPOSITION/MAXRESULTS inside the query — there is no cursor and no total, so a page shorter than maxResults is the last one. maxResults is capped at 1000.

[QuickBooks Online] Create a credit card payment. A credit card payment moves money from a bank account to a credit card account to pay down its balance. It is a more limited form of a transfer. body is the entity record as a JSON object, the same shape a read returns.

[QuickBooks Online] Create a deposit. A deposit records money banked: customer payments held in Undeposited Funds moved into an asset account, or direct deposits recorded on their own lines. body is the entity record as a JSON object, the same shape a read returns.

[QuickBooks Online] Create a transfer. A transfer moves funds between two accounts in the company's own chart of accounts. It is not a payment to anyone. body is the entity record as a JSON object, the same shape a read returns.

[QuickBooks Online] Delete a credit card payment. This removes the transaction from the company's books and cannot be undone; where the entity can be VOIDED instead, voiding keeps the audit trail and is usually what an accountant wants. A credit card payment moves money from a bank account to a credit card account to pay down its balance. It is a more limited form of a transfer. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] Delete a deposit. This removes the transaction from the company's books and cannot be undone; where the entity can be VOIDED instead, voiding keeps the audit trail and is usually what an accountant wants. A deposit records money banked: customer payments held in Undeposited Funds moved into an asset account, or direct deposits recorded on their own lines. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] Delete a transfer. This removes the transaction from the company's books and cannot be undone; where the entity can be VOIDED instead, voiding keeps the audit trail and is usually what an accountant wants. A transfer moves funds between two accounts in the company's own chart of accounts. It is not a payment to anyone. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] FULL update of a credit card payment. DATA LOSS WARNING: QuickBooks sets every writable field you omit to NULL, so the body must repeat the whole record exactly as a read returned it. Prefer qbo_update_credit_card_payment, which changes only what you send. A credit card payment moves money from a bank account to a credit card account to pay down its balance. It is a more limited form of a transfer. body is the entity record as a JSON object, the same shape a read returns. The body must carry the record's Id and SyncToken. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] FULL update of a deposit. DATA LOSS WARNING: QuickBooks sets every writable field you omit to NULL, so the body must repeat the whole record exactly as a read returned it. Prefer qbo_update_deposit, which changes only what you send. A deposit records money banked: customer payments held in Undeposited Funds moved into an asset account, or direct deposits recorded on their own lines. body is the entity record as a JSON object, the same shape a read returns. The body must carry the record's Id and SyncToken. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] FULL update of a transfer. DATA LOSS WARNING: QuickBooks sets every writable field you omit to NULL, so the body must repeat the whole record exactly as a read returned it. Prefer qbo_update_transfer, which changes only what you send. A transfer moves funds between two accounts in the company's own chart of accounts. It is not a payment to anyone. body is the entity record as a JSON object, the same shape a read returns. The body must carry the record's Id and SyncToken. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] Read one credit card payment by its QuickBooks Id, including the SyncToken every update must echo back. A credit card payment moves money from a bank account to a credit card account to pay down its balance. It is a more limited form of a transfer.

[QuickBooks Online] Read one deposit by its QuickBooks Id, including the SyncToken every update must echo back. A deposit records money banked: customer payments held in Undeposited Funds moved into an asset account, or direct deposits recorded on their own lines.

[QuickBooks Online] Read one transfer by its QuickBooks Id, including the SyncToken every update must echo back. A transfer moves funds between two accounts in the company's own chart of accounts. It is not a payment to anyone.

[QuickBooks Online] List credit card payments with an optional WHERE clause. A credit card payment moves money from a bank account to a credit card account to pay down its balance. It is a more limited form of a transfer. The WHERE fragment is QuickBooks query syntax, not SQL: no OR, no JOIN, LIKE with only the % wildcard, Id only with = or IN, and string literals in single quotes. Paging is STARTPOSITION/MAXRESULTS inside the query — there is no cursor and no total, so a page shorter than maxResults is the last one. maxResults is capped at 1000.

[QuickBooks Online] List deposits with an optional WHERE clause. A deposit records money banked: customer payments held in Undeposited Funds moved into an asset account, or direct deposits recorded on their own lines. The WHERE fragment is QuickBooks query syntax, not SQL: no OR, no JOIN, LIKE with only the % wildcard, Id only with = or IN, and string literals in single quotes. Paging is STARTPOSITION/MAXRESULTS inside the query — there is no cursor and no total, so a page shorter than maxResults is the last one. maxResults is capped at 1000.

[QuickBooks Online] List transfers with an optional WHERE clause. A transfer moves funds between two accounts in the company's own chart of accounts. It is not a payment to anyone. The WHERE fragment is QuickBooks query syntax, not SQL: no OR, no JOIN, LIKE with only the % wildcard, Id only with = or IN, and string literals in single quotes. Paging is STARTPOSITION/MAXRESULTS inside the query — there is no cursor and no total, so a page shorter than maxResults is the last one. maxResults is capped at 1000.

[QuickBooks Online] SPARSE update of a credit card payment — only the fields you send are changed and every omitted field is left alone. This is the safe update and the one to reach for. A credit card payment moves money from a bank account to a credit card account to pay down its balance. It is a more limited form of a transfer. body is the entity record as a JSON object, the same shape a read returns. The body must carry the record's Id and SyncToken. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] SPARSE update of a deposit — only the fields you send are changed and every omitted field is left alone. This is the safe update and the one to reach for. A deposit records money banked: customer payments held in Undeposited Funds moved into an asset account, or direct deposits recorded on their own lines. body is the entity record as a JSON object, the same shape a read returns. The body must carry the record's Id and SyncToken. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] SPARSE update of a transfer — only the fields you send are changed and every omitted field is left alone. This is the safe update and the one to reach for. A transfer moves funds between two accounts in the company's own chart of accounts. It is not a payment to anyone. body is the entity record as a JSON object, the same shape a read returns. The body must carry the record's Id and SyncToken. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] Create a budget. A budget assigns an expected amount to an account or customer per month, quarter or year, which is what the budget-versus-actual reports measure against. body is the entity record as a JSON object, the same shape a read returns.

[QuickBooks Online] Delete a budget. This removes the budget and the figures in it and cannot be undone; the transactions it was measured against are untouched. A budget assigns an expected amount to an account or customer per month, quarter or year, which is what the budget-versus-actual reports measure against. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] FULL update of a budget. DATA LOSS WARNING: QuickBooks sets every writable field you omit to NULL, so the body must repeat the whole record exactly as a read returned it. This entity offers no sparse update, so read the record first and echo every writable field back. A budget assigns an expected amount to an account or customer per month, quarter or year, which is what the budget-versus-actual reports measure against. body is the entity record as a JSON object, the same shape a read returns. The body must carry the record's Id and SyncToken. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] Read one budget by its QuickBooks Id, including the SyncToken every update must echo back. A budget assigns an expected amount to an account or customer per month, quarter or year, which is what the budget-versus-actual reports measure against.

[QuickBooks Online] List budgets with an optional WHERE clause. A budget assigns an expected amount to an account or customer per month, quarter or year, which is what the budget-versus-actual reports measure against. The WHERE fragment is QuickBooks query syntax, not SQL: no OR, no JOIN, LIKE with only the % wildcard, Id only with = or IN, and string literals in single quotes. Paging is STARTPOSITION/MAXRESULTS inside the query — there is no cursor and no total, so a page shorter than maxResults is the last one. maxResults is capped at 1000.

[QuickBooks Online] Create a recurring transaction. A recurring transaction is a scheduled template - a transaction QuickBooks creates on a schedule, a reminder, or a template kept for later use. PRODUCT-GATED: QuickBooks Online Essentials and Plus. body is the entity record as a JSON object, the same shape a read returns.

[QuickBooks Online] Delete a recurring transaction. This removes the TEMPLATE and its schedule and cannot be undone, so QuickBooks creates no further transactions from it; transactions it has already created stay in the books. A recurring transaction is a scheduled template - a transaction QuickBooks creates on a schedule, a reminder, or a template kept for later use. PRODUCT-GATED: QuickBooks Online Essentials and Plus. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] Read one recurring transaction by its QuickBooks Id. A recurring transaction is a scheduled template - a transaction QuickBooks creates on a schedule, a reminder, or a template kept for later use. PRODUCT-GATED: QuickBooks Online Essentials and Plus.

[QuickBooks Online] List recurring transactions with an optional WHERE clause. A recurring transaction is a scheduled template - a transaction QuickBooks creates on a schedule, a reminder, or a template kept for later use. PRODUCT-GATED: QuickBooks Online Essentials and Plus. The WHERE fragment is QuickBooks query syntax, not SQL: no OR, no JOIN, LIKE with only the % wildcard, Id only with = or IN, and string literals in single quotes. Paging is STARTPOSITION/MAXRESULTS inside the query — there is no cursor and no total, so a page shorter than maxResults is the last one. maxResults is capped at 1000.

[QuickBooks Online] Create an inventory adjustment. An inventory adjustment changes the quantity on hand of inventory items for damage, write-off, shrinkage or expiry, and handles the underlying accounting and valuation itself. PRODUCT-GATED: US companies on QuickBooks Online Plus or Advanced. body is the entity record as a JSON object, the same shape a read returns.

[QuickBooks Online] Delete an inventory adjustment. This removes the transaction from the company's books and cannot be undone; where the entity can be VOIDED instead, voiding keeps the audit trail and is usually what an accountant wants. An inventory adjustment changes the quantity on hand of inventory items for damage, write-off, shrinkage or expiry, and handles the underlying accounting and valuation itself. PRODUCT-GATED: US companies on QuickBooks Online Plus or Advanced. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] Read one inventory adjustment by its QuickBooks Id, including the SyncToken every update must echo back. An inventory adjustment changes the quantity on hand of inventory items for damage, write-off, shrinkage or expiry, and handles the underlying accounting and valuation itself. PRODUCT-GATED: US companies on QuickBooks Online Plus or Advanced.

[QuickBooks Online] SPARSE update of an inventory adjustment — only the fields you send are changed and every omitted field is left alone. This is the safe update and the one to reach for. An inventory adjustment changes the quantity on hand of inventory items for damage, write-off, shrinkage or expiry, and handles the underlying accounting and valuation itself. PRODUCT-GATED: US companies on QuickBooks Online Plus or Advanced. body is the entity record as a JSON object, the same shape a read returns. The body must carry the record's Id and SyncToken. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] Create a company currency. A company currency is a currency active in this QuickBooks company - the list the Currency Center shows. PRODUCT-GATED: only companies with multicurrency enabled have any. body is the entity record as a JSON object, the same shape a read returns.

[QuickBooks Online] FULL update of a company currency. DATA LOSS WARNING: QuickBooks sets every writable field you omit to NULL, so the body must repeat the whole record exactly as a read returned it. This entity offers no sparse update, so read the record first and echo every writable field back. A company currency is a currency active in this QuickBooks company - the list the Currency Center shows. PRODUCT-GATED: only companies with multicurrency enabled have any. body is the entity record as a JSON object, the same shape a read returns. The body must carry the record's Id and SyncToken. Send the SyncToken from the most recent read of this record; an older one is rejected, and the fix is to re-read and retry rather than to retry the same body.

[QuickBooks Online] Read one company currency by its QuickBooks Id, including the SyncToken every update must echo back. A company currency is a currency active in this QuickBooks company - the list the Currency Center shows. PRODUCT-GATED: only companies with multicurrency enabled have any.

[QuickBooks Online] Read the rate held for ONE source currency, optionally as at a date. This is a bespoke route, not the query one: the query lists stored Exchangerate objects, while this answers the rate in force for a currency — today's, when asOfDate is omitted. An exchange rate is the rate held for a source currency against the company's home currency on a date. PRODUCT-GATED: only companies with multicurrency enabled have any.

[QuickBooks Online] List company currencies with an optional WHERE clause. A company currency is a currency active in this QuickBooks company - the list the Currency Center shows. PRODUCT-GATED: only companies with multicurrency enabled have any. The WHERE fragment is QuickBooks query syntax, not SQL: no OR, no JOIN, LIKE with only the % wildcard, Id only with = or IN, and string literals in single quotes. Paging is STARTPOSITION/MAXRESULTS inside the query — there is no cursor and no total, so a page shorter than maxResults is the last one. maxResults is capped at 1000.

[QuickBooks Online] List exchange rates with an optional WHERE clause. An exchange rate is the rate held for a source currency against the company's home currency on a date. PRODUCT-GATED: only companies with multicurrency enabled have any. The WHERE fragment is QuickBooks query syntax, not SQL: no OR, no JOIN, LIKE with only the % wildcard, Id only with = or IN, and string literals in single quotes. Paging is STARTPOSITION/MAXRESULTS inside the query — there is no cursor and no total, so a page shorter than maxResults is the last one. maxResults is capped at 1000.

[QuickBooks Online] Set the rate for a source currency as at a date. This REPLACES the rate held for that currency and date: the previous value is not kept, the change cannot be undone, and every conversion made afterwards uses the new rate. SourceCurrencyCode, Rate and AsOfDate are mandatory; TargetCurrencyCode defaults to the home currency. A rate where source and target are the same is forced to 1, and setting a rate for the home currency itself is a validation error. An exchange rate is the rate held for a source currency against the company's home currency on a date. PRODUCT-GATED: only companies with multicurrency enabled have any. body is the entity record as a JSON object, the same shape a read returns.