---
title: "One QuickBooks change review with a field-level before/after diff (#2642)"
method: GET
path: "/accountant/companies/{customerId}/integrations/quickbooks/change-reviews/{reviewId}"
tags: ["Accountants"]
---

# One QuickBooks change review with a field-level before/after diff (#2642)

`GET /accountant/companies/{customerId}/integrations/quickbooks/change-reviews/{reviewId}`

## Request

- Base URL: `https://api.medianfi.com/api/v1`
- URL: `https://api.medianfi.com/api/v1/accountant/companies/{customerId}/integrations/quickbooks/change-reviews/{reviewId}`
- Auth: one of:
  - HTTP bearer
  - API key in header `X-API-Key`

The diff covers economic fields only (dates, amounts, accounts, counterparties, currency, lines); SyncToken, metadata and display names are excluded, but reference names are shown alongside ids.

## Response `200`

The review

- object
  - `success` true, required
  - `data` QuickBooksChangeReviewDetail, required
    - `id` string, uuid, required
    - `companyId` string, uuid, required
    - `entityId` string, uuid, required
    - `realmId` string, required
    - `linkId` string, uuid, required
    - `objectType` string, required
    - `providerId` string, required
    - `changeKind` 'changed' | 'deleted', required
    - `beforeSourceObjectId` string, uuid, nullable, required
    - `beforeEconomicSha256` string, required
    - `afterSourceObjectId` string, uuid, nullable, required
    - `afterEconomicSha256` string, nullable, required
    - `detectedRunId` string, uuid, required
    - `lastDetectedRunId` string, uuid, required
    - `status` 'open' | 'resolved_take_qbo' | 'resolved_keep_median' | 'dismissed', required
    - `resolutionReason` string, nullable, required
    - `resolvedByUserId` string, uuid, nullable, required
    - `resolvedAt` string, date-time, nullable, required
    - `followupStatus` 'none' | 'reversal_pending' | 'reversed' | 'writeback_pending' | 'writeback_requested', required
    - `followupReason` 'client_must_correct_quickbooks' | 'writeback_not_possible' | 'null', nullable, required: Why a keep_median restore stays writeback_pending. client_must_correct_quickbooks — QuickBooks changed an amount, date, bank/card line, counterparty or other field post-back never writes, or deleted the object. writeback_not_possible — only account/class/memo changed but the write-back rules refused the correction. writeback_requested means a draft write-back batch was prepared; it still needs approval and posting.
    - `createdAt` string, date-time, required
    - `updatedAt` string, date-time, required
    - `link` object, required
      - `direction` 'pull' | 'push', required
      - `active` boolean, required
      - `journalEntryId` string, uuid, nullable, required
      - `transactionId` string, uuid, nullable, required
      - `arItemId` string, uuid, nullable, required
      - `apItemId` string, uuid, nullable, required
    - `diff` object[], required
      - `path` string, required
      - `category` 'date' | 'amount' | 'account' | 'counterparty' | 'currency' | 'other', required
      - `before` union, required
        - string
        - number
        - boolean
      - `after` union, required
        - string
        - number
        - boolean
      - `beforeName` string, nullable
      - `afterName` string, nullable

## Other responses

- `401`: Authentication required
- `403`: Insufficient permissions or not a company member
- `404`: Resource not found

---

[API](https://skmtc.dev/medianfi/apis/median-api.md) · [All operations](https://skmtc.dev/medianfi/apis/median-api/llms.txt) · [OpenAPI document](https://skmtc.dev/medianfi/apis/median-api/revisions/20090ea32b0d?raw)