Sign in

List all receive-payments

Returns a list of receive-payments. Use the cursor parameter to paginate through the results.

get/quickbooks-desktop/receive-payments

Query parameters

idsstring[]

Filter for specific receive-payments by their QuickBooks-assigned unique identifier(s).

IMPORTANT: If you include this parameter, QuickBooks will ignore all other query parameters for this request.

NOTE: If any of the values you specify in this parameter are not found, the request will return an error.

Filter for specific receive-payments by their QuickBooks-assigned unique identifier(s).

IMPORTANT: If you include this parameter, QuickBooks will ignore all other query parameters for this request.

NOTE: If any of the values you specify in this parameter are not found, the request will return an error.

[
  "123ABC-1234567890"
]
refNumbersstring[]

Filter for specific receive-payments by their ref-number(s), case-sensitive. In QuickBooks, ref-numbers are not required to be unique and can be arbitrarily changed by the QuickBooks user.

IMPORTANT: If you include this parameter, QuickBooks will ignore all other query parameters for this request.

NOTE: If any of the values you specify in this parameter are not found, the request will return an error.

Filter for specific receive-payments by their ref-number(s), case-sensitive. In QuickBooks, ref-numbers are not required to be unique and can be arbitrarily changed by the QuickBooks user.

IMPORTANT: If you include this parameter, QuickBooks will ignore all other query parameters for this request.

NOTE: If any of the values you specify in this parameter are not found, the request will return an error.

[
  "RECEIVE-PAYMENT-1234"
]
limitinteger

The maximum number of objects to return. Accepts values ranging from 1 to 150, defaults to 150. When used with cursor-based pagination, this parameter controls how many results are returned per page. To paginate through results, combine this with the cursor parameter. Each response will include a nextCursor value that can be passed to subsequent requests to retrieve the next page of results.

Example:150

The maximum number of objects to return. Accepts values ranging from 1 to 150, defaults to 150. When used with cursor-based pagination, this parameter controls how many results are returned per page. To paginate through results, combine this with the cursor parameter. Each response will include a nextCursor value that can be passed to subsequent requests to retrieve the next page of results.

cursorstring

The pagination token to fetch the next set of results when paginating with the limit parameter. Do not include this parameter on the first call. Use the nextCursor value returned in the previous response to request subsequent results.

Example:12345678-abcd-abcd-example-1234567890ab

The pagination token to fetch the next set of results when paginating with the limit parameter. Do not include this parameter on the first call. Use the nextCursor value returned in the previous response to request subsequent results.

updatedAfterstring

Filter for receive-payments updated on or after this date/time. Accepts the following ISO 8601 formats:

  • date-only (YYYY-MM-DD) - QuickBooks Desktop interprets the date as the start of the specified day in the local timezone of the end-user's computer (e.g., 2025-01-01 → 2025-01-01T00:00:00).
  • datetime without timezone (YYYY-MM-DDTHH:mm:ss) - QuickBooks Desktop interprets the timestamp in the local timezone of the end-user's computer.
  • datetime with timezone (YYYY-MM-DDTHH:mm:ss±HH:mm) - QuickBooks Desktop interprets the timestamp using the specified timezone.
Example:2025-01-01T12:34:56+00:00

Filter for receive-payments updated on or after this date/time. Accepts the following ISO 8601 formats:

  • date-only (YYYY-MM-DD) - QuickBooks Desktop interprets the date as the start of the specified day in the local timezone of the end-user's computer (e.g., 2025-01-01 → 2025-01-01T00:00:00).
  • datetime without timezone (YYYY-MM-DDTHH:mm:ss) - QuickBooks Desktop interprets the timestamp in the local timezone of the end-user's computer.
  • datetime with timezone (YYYY-MM-DDTHH:mm:ss±HH:mm) - QuickBooks Desktop interprets the timestamp using the specified timezone.
updatedBeforestring

Filter for receive-payments updated on or before this date/time. Accepts the following ISO 8601 formats:

  • date-only (YYYY-MM-DD) - QuickBooks Desktop interprets the date as the end of the specified day in the local timezone of the end-user's computer (e.g., 2025-01-01 → 2025-01-01T23:59:59).
  • datetime without timezone (YYYY-MM-DDTHH:mm:ss) - QuickBooks Desktop interprets the timestamp in the local timezone of the end-user's computer.
  • datetime with timezone (YYYY-MM-DDTHH:mm:ss±HH:mm) - QuickBooks Desktop interprets the timestamp using the specified timezone.
Example:2025-02-01T12:34:56+00:00

Filter for receive-payments updated on or before this date/time. Accepts the following ISO 8601 formats:

  • date-only (YYYY-MM-DD) - QuickBooks Desktop interprets the date as the end of the specified day in the local timezone of the end-user's computer (e.g., 2025-01-01 → 2025-01-01T23:59:59).
  • datetime without timezone (YYYY-MM-DDTHH:mm:ss) - QuickBooks Desktop interprets the timestamp in the local timezone of the end-user's computer.
  • datetime with timezone (YYYY-MM-DDTHH:mm:ss±HH:mm) - QuickBooks Desktop interprets the timestamp using the specified timezone.
transactionDateFromstring date

Filter for receive-payments whose date field is on or after this date, in ISO 8601 format (YYYY-MM-DD).

NOTE: QuickBooks Desktop interprets this date as the start of the specified day in the local timezone of the end-user's computer (e.g., 2025-01-01 → 2025-01-01T00:00:00).

Example:2025-01-01

Filter for receive-payments whose date field is on or after this date, in ISO 8601 format (YYYY-MM-DD).

NOTE: QuickBooks Desktop interprets this date as the start of the specified day in the local timezone of the end-user's computer (e.g., 2025-01-01 → 2025-01-01T00:00:00).

transactionDateTostring date

Filter for receive-payments whose date field is on or before this date, in ISO 8601 format (YYYY-MM-DD).

NOTE: QuickBooks Desktop interprets this date as the end of the specified day in the local timezone of the end-user's computer (e.g., 2025-01-01 → 2025-01-01T23:59:59).

Example:2025-02-01

Filter for receive-payments whose date field is on or before this date, in ISO 8601 format (YYYY-MM-DD).

NOTE: QuickBooks Desktop interprets this date as the end of the specified day in the local timezone of the end-user's computer (e.g., 2025-01-01 → 2025-01-01T23:59:59).

customerIdsstring[]

Filter for receive-payments received from these customers.

Filter for receive-payments received from these customers.

[
  "80000001-1234567890"
]
accountIdsstring[]

Filter for receive-payments associated with these accounts.

Filter for receive-payments associated with these accounts.

[
  "80000001-1234567890"
]
refNumberContainsstring

Filter for receive-payments whose refNumber contains this substring.

NOTE: If you use this parameter, you cannot also use refNumberStartsWith or refNumberEndsWith.

Example:PAYMENT-1234

Filter for receive-payments whose refNumber contains this substring.

NOTE: If you use this parameter, you cannot also use refNumberStartsWith or refNumberEndsWith.

refNumberStartsWithstring

Filter for receive-payments whose refNumber starts with this substring.

NOTE: If you use this parameter, you cannot also use refNumberContains or refNumberEndsWith.

Example:PAYMENT

Filter for receive-payments whose refNumber starts with this substring.

NOTE: If you use this parameter, you cannot also use refNumberContains or refNumberEndsWith.

refNumberEndsWithstring

Filter for receive-payments whose refNumber ends with this substring.

NOTE: If you use this parameter, you cannot also use refNumberContains or refNumberStartsWith.

Example:1234

Filter for receive-payments whose refNumber ends with this substring.

NOTE: If you use this parameter, you cannot also use refNumberContains or refNumberStartsWith.

refNumberFromstring

Filter for receive-payments whose refNumber is greater than or equal to this value. If omitted, the range will begin with the first number of the list. Uses a numerical comparison for values that contain only digits; otherwise, uses a lexicographical comparison.

Example:PAYMENT-0001

Filter for receive-payments whose refNumber is greater than or equal to this value. If omitted, the range will begin with the first number of the list. Uses a numerical comparison for values that contain only digits; otherwise, uses a lexicographical comparison.

refNumberTostring

Filter for receive-payments whose refNumber is less than or equal to this value. If omitted, the range will end with the last number of the list. Uses a numerical comparison for values that contain only digits; otherwise, uses a lexicographical comparison.

Example:PAYMENT-9999

Filter for receive-payments whose refNumber is less than or equal to this value. If omitted, the range will end with the last number of the list. Uses a numerical comparison for values that contain only digits; otherwise, uses a lexicographical comparison.

currencyIdsstring[]

Filter for receive-payments in these currencies.

Filter for receive-payments in these currencies.

[
  "80000001-1234567890"
]
includeLineItemsboolean

Whether to include line items in the response. Defaults to true.

Example:true

Whether to include line items in the response. Defaults to true.

Headers

Conductor-End-User-Idstring required

The ID of the End-User to receive this request.

Example:end_usr_1234567abcdefg

The ID of the End-User to receive this request.

Response

Returns a list of receive-payments.

objectType'list' required

The type of object. This value is always "list".

urlstring required

The endpoint URL where this list can be accessed.

nextCursorstring nullable required

The nextCursor is a pagination token returned in the response when you use the limit parameter in your request. To retrieve subsequent pages of results, include this token as the value of the cursor request parameter in your following API calls.

NOTE: The nextCursor value remains constant throughout the pagination process for a specific list instance; continue to use the same nextCursor token in each request to fetch additional pages.

remainingCountnumber nullable required

The number of objects remaining to be fetched.

hasMoreboolean required

Indicates whether there are more objects to be fetched.

Example response

{
  "objectType": "list",
  "url": "/v1/quickbooks-desktop/receive-payments",
  "data": [
    {
      "id": "123ABC-1234567890",
      "objectType": "qbd_receive_payment",
      "createdAt": "2025-01-01T12:34:56+00:00",
      "updatedAt": "2025-02-01T12:34:56+00:00",
      "revisionNumber": "1721172183",
      "customer": {
        "id": "80000001-1234567890",
        "fullName": "Acme Corporation"
      },
      "receivablesAccount": {
        "id": "80000001-1234567890",
        "fullName": "Accounts-Receivable"
      },
      "transactionDate": "2024-10-01",
      "refNumber": "PAYMENT-1234",
      "totalAmount": "1000.00",
      "currency": {
        "id": "80000001-1234567890",
        "fullName": "USD"
      },
      "exchangeRate": 1.2345,
      "totalAmountInHomeCurrency": "1234.56",
      "paymentMethod": {
        "id": "80000001-1234567890",
        "fullName": "Credit Card"
      },
      "memo": "Payment received at store location - cash",
      "depositToAccount": {
        "id": "80000001-1234567890",
        "fullName": "Undeposited Funds"
      },
      "creditCardTransaction": {
        "request": {
          "number": "xxxxxxxxxxxx1234",
          "expirationMonth": 12,
          "expirationYear": 2024,
          "name": "John Doe",
          "address": "1234 Main St, Anytown, USA, 12345",
          "postalCode": "12345",
          "commercialCardCode": "corporate",
          "transactionMode": "card_not_present",
          "transactionType": "charge"
        },
        "response": {
          "statusMessage": "Success",
          "creditCardTransactionId": "1234567890",
          "merchantAccountNumber": "1234567890",
          "authorizationCode": "1234567890",
          "avsStreetStatus": "pass",
          "avsZipStatus": "pass",
          "cardSecurityCodeMatch": "pass",
          "reconBatchId": "1234567890",
          "paymentGroupingCode": 2,
          "paymentStatus": "completed",
          "transactionAuthorizedAt": "2024-01-01T12:34:56Z",
          "transactionAuthorizationStamp": 2,
          "clientTransactionId": "1234567890"
        }
      },
      "unusedPayment": "100.00",
      "unusedCredits": "100.00",
      "externalId": "12345678-abcd-1234-abcd-1234567890ab",
      "appliedToTransactions": [
        {
          "transactionId": "123ABC-1234567890",
          "transactionType": "invoice",
          "transactionDate": "2024-10-01",
          "refNumber": "TXN-1234",
          "balanceRemaining": "100.00",
          "amount": "1000.00",
          "discountAmount": "50.00",
          "discountAccount": {
            "id": "80000001-1234567890",
            "fullName": "Discount Account"
          },
          "discountClass": {
            "id": "80000001-1234567890",
            "fullName": "Discounts"
          },
          "linkedTransactions": [
            {
              "id": "123ABC-1234567890",
              "objectType": "qbd_linked_transaction",
              "transactionType": "invoice",
              "transactionDate": "2024-10-01",
              "refNumber": "LINK-1234",
              "linkType": "amount",
              "amount": "1000.00"
            }
          ]
        }
      ],
      "customFields": [
        {
          "ownerId": "0",
          "name": "Customer Rating",
          "type": "string_1024_type",
          "value": "Premium"
        }
      ]
    }
  ],
  "nextCursor": "12345678-abcd-abcd-example-1234567890ab",
  "remainingCount": 10
}

Changes

Changed in 4 of the 46 revisions of this API.110469

  • daabb801a1731See the full diff
    • ●

      added the new unknown enum value to the data/items/appliedToTransactions/items/transactionType response property for the response status 200

      response-property-enum-value-added

  • 10d4e9ebd1df3812See the full diff
    • ▲

      response property data/items/appliedToTransactions/items/amount list-of-types was widened by adding types null to media type application/json of response 200

      response-property-list-of-types-widened

    • ▲

      response property data/items/appliedToTransactions/items/balanceRemaining list-of-types was widened by adding types null to media type application/json of response 200

      response-property-list-of-types-widened

    • ▲

      response property data/items/appliedToTransactions/items/discountAmount list-of-types was widened by adding types null to media type application/json of response 200

      response-property-list-of-types-widened

    • ▲

      response property data/items/appliedToTransactions/items/linkedTransactions/items/amount list-of-types was widened by adding types null to media type application/json of response 200

      response-property-list-of-types-widened

    • ▲

      response property data/items/appliedToTransactions/items/linkedTransactions/items/linkType list-of-types was widened by adding types null to media type application/json of response 200

      response-property-list-of-types-widened

    • ▲

      response property data/items/appliedToTransactions/items/linkedTransactions/items/refNumber list-of-types was widened by adding types null to media type application/json of response 200

      response-property-list-of-types-widened

    • ▲

      response property data/items/appliedToTransactions/items/refNumber list-of-types was widened by adding types null to media type application/json of response 200

      response-property-list-of-types-widened

    • ▲

      response property data/items/appliedToTransactions/items/transactionDate list-of-types was widened by adding types null to media type application/json of response 200

      response-property-list-of-types-widened

    • ▲

      response property data/items/exchangeRate list-of-types was widened by adding types null to media type application/json of response 200

      response-property-list-of-types-widened

    • ▲

      response property data/items/externalId list-of-types was widened by adding types null to media type application/json of response 200

      response-property-list-of-types-widened

    • ▲

      response property data/items/memo list-of-types was widened by adding types null to media type application/json of response 200

      response-property-list-of-types-widened

    • ▲

      response property data/items/refNumber list-of-types was widened by adding types null to media type application/json of response 200

      response-property-list-of-types-widened

    • ▲

      response property data/items/totalAmountInHomeCurrency list-of-types was widened by adding types null to media type application/json of response 200

      response-property-list-of-types-widened

    • ▲

      response property data/items/unusedCredits list-of-types was widened by adding types null to media type application/json of response 200

      response-property-list-of-types-widened

    • ▲

      response property data/items/unusedPayment list-of-types was widened by adding types null to media type application/json of response 200

      response-property-list-of-types-widened

    • ▲

      response property nextCursor list-of-types was widened by adding types null to media type application/json of response 200

      response-property-list-of-types-widened

    • ▲

      response property remainingCount list-of-types was widened by adding types null to media type application/json of response 200

      response-property-list-of-types-widened

    • ▲

      the data/items/appliedToTransactions/items/discountAccount response's property type/format changed from object null/ to / for status 200

      response-property-type-changed

    • ▲

      the data/items/appliedToTransactions/items/discountClass response's property type/format changed from object null/ to / for status 200

      response-property-type-changed

    • ▲

      the data/items/currency response's property type/format changed from object null/ to / for status 200

      response-property-type-changed

    • ▲

      the data/items/customer response's property type/format changed from object null/ to / for status 200

      response-property-type-changed

    • ▲

      the data/items/depositToAccount response's property type/format changed from object null/ to / for status 200

      response-property-type-changed

    • ▲

      the data/items/paymentMethod response's property type/format changed from object null/ to / for status 200

      response-property-type-changed

    • ▲

      the data/items/receivablesAccount response's property type/format changed from object null/ to / for status 200

      response-property-type-changed

    • ▲

      removed the required property data/items/appliedToTransactions/items/discountAccount/fullName from the response with the 200 status

      response-required-property-removed

    • ▲

      removed the required property data/items/appliedToTransactions/items/discountAccount/id from the response with the 200 status

      response-required-property-removed

    • ▲

      removed the required property data/items/appliedToTransactions/items/discountClass/fullName from the response with the 200 status

      response-required-property-removed

    • ▲

      removed the required property data/items/appliedToTransactions/items/discountClass/id from the response with the 200 status

      response-required-property-removed

    • ▲

      removed the required property data/items/currency/fullName from the response with the 200 status

      response-required-property-removed

    • ▲

      removed the required property data/items/currency/id from the response with the 200 status

      response-required-property-removed

    • ▲

      removed the required property data/items/customer/fullName from the response with the 200 status

      response-required-property-removed

    • ▲

      removed the required property data/items/customer/id from the response with the 200 status

      response-required-property-removed

    • ▲

      removed the required property data/items/depositToAccount/fullName from the response with the 200 status

      response-required-property-removed

    • ▲

      removed the required property data/items/depositToAccount/id from the response with the 200 status

      response-required-property-removed

    • ▲

      removed the required property data/items/paymentMethod/fullName from the response with the 200 status

      response-required-property-removed

    • ▲

      removed the required property data/items/paymentMethod/id from the response with the 200 status

      response-required-property-removed

    • ▲

      removed the required property data/items/receivablesAccount/fullName from the response with the 200 status

      response-required-property-removed

    • ▲

      removed the required property data/items/receivablesAccount/id from the response with the 200 status

      response-required-property-removed

    • ○

      added qbd_credit_card_transaction subschema #2 to the data/items/creditCardTransaction response property anyOf list for the response status 200

      response-property-any-of-added

    • ○

      added subschema #1 subschema #2 to the data/items/appliedToTransactions/items/discountAccount response property anyOf list for the response status 200

      response-property-any-of-added

    • ○

      added subschema #1 subschema #2 to the data/items/appliedToTransactions/items/discountClass response property anyOf list for the response status 200

      response-property-any-of-added

    • ○

      added subschema #1 subschema #2 to the data/items/currency response property anyOf list for the response status 200

      response-property-any-of-added

    • ○

      added subschema #1 subschema #2 to the data/items/customer response property anyOf list for the response status 200

      response-property-any-of-added

    • ○

      added subschema #1 subschema #2 to the data/items/depositToAccount response property anyOf list for the response status 200

      response-property-any-of-added

    • ○

      added subschema #1 subschema #2 to the data/items/paymentMethod response property anyOf list for the response status 200

      response-property-any-of-added

    • ○

      added subschema #1 subschema #2 to the data/items/receivablesAccount response property anyOf list for the response status 200

      response-property-any-of-added

    • ○

      removed the amount enum value from the data/items/appliedToTransactions/items/linkedTransactions/items/linkType response property for the response status 200

      response-property-enum-value-removed

    • ○

      removed the quantity enum value from the data/items/appliedToTransactions/items/linkedTransactions/items/linkType response property for the response status 200

      response-property-enum-value-removed

    • ○

      removed the undefined enum value from the data/items/appliedToTransactions/items/linkedTransactions/items/linkType response property for the response status 200

      response-property-enum-value-removed

    • ○

      removed qbd_credit_card_transaction subschema #2 from the data/items/creditCardTransaction response property oneOf list for the response status 200

      response-property-one-of-removed

  • 8e0b7df2044d32343See the full diff
    • ▲

      the response property data/items/appliedToTransactions/items/amount became nullable for the status 200

      response-property-became-nullable

    • ▲

      the response property data/items/appliedToTransactions/items/balanceRemaining became nullable for the status 200

      response-property-became-nullable

    • ▲

      the response property data/items/appliedToTransactions/items/discountAccount became nullable for the status 200

      response-property-became-nullable

    • ▲

      the response property data/items/appliedToTransactions/items/discountAmount became nullable for the status 200

      response-property-became-nullable

    • ▲

      the response property data/items/appliedToTransactions/items/discountClass became nullable for the status 200

      response-property-became-nullable

    • ▲

      the response property data/items/appliedToTransactions/items/linkedTransactions/items/amount became nullable for the status 200

      response-property-became-nullable

    • ▲

      the response property data/items/appliedToTransactions/items/linkedTransactions/items/linkType became nullable for the status 200

      response-property-became-nullable

    • ▲

      the response property data/items/appliedToTransactions/items/linkedTransactions/items/refNumber became nullable for the status 200

      response-property-became-nullable

    • ▲

      the response property data/items/appliedToTransactions/items/refNumber became nullable for the status 200

      response-property-became-nullable

    • ▲

      the response property data/items/appliedToTransactions/items/transactionDate became nullable for the status 200

      response-property-became-nullable

    • ▲

      the response property data/items/currency became nullable for the status 200

      response-property-became-nullable

    • ▲

      the response property data/items/customer became nullable for the status 200

      response-property-became-nullable

    • ▲

      the response property data/items/depositToAccount became nullable for the status 200

      response-property-became-nullable

    • ▲

      the response property data/items/exchangeRate became nullable for the status 200

      response-property-became-nullable

    • ▲

      the response property data/items/externalId became nullable for the status 200

      response-property-became-nullable

    • ▲

      the response property data/items/memo became nullable for the status 200

      response-property-became-nullable

    • ▲

      the response property data/items/paymentMethod became nullable for the status 200

      response-property-became-nullable

    • ▲

      the response property data/items/receivablesAccount became nullable for the status 200

      response-property-became-nullable

    • ▲

      the response property data/items/refNumber became nullable for the status 200

      response-property-became-nullable

    • ▲

      the response property data/items/totalAmountInHomeCurrency became nullable for the status 200

      response-property-became-nullable

    • ▲

      the response property data/items/unusedCredits became nullable for the status 200

      response-property-became-nullable

    • ▲

      the response property data/items/unusedPayment became nullable for the status 200

      response-property-became-nullable

    • ▲

      the response property nextCursor became nullable for the status 200

      response-property-became-nullable

    • ▲

      the response property remainingCount became nullable for the status 200

      response-property-became-nullable

    • ▲

      added qbd_credit_card_transaction subschema #2 to the data/items/creditCardTransaction response property oneOf list for the response status 200

      response-property-one-of-added

    • ▲

      the data/items/appliedToTransactions/items/discountAccount response's property type/format changed from / to object null/ for status 200

      response-property-type-changed

    • ▲

      the data/items/appliedToTransactions/items/discountClass response's property type/format changed from / to object null/ for status 200

      response-property-type-changed

    • ▲

      the data/items/currency response's property type/format changed from / to object null/ for status 200

      response-property-type-changed

    • ▲

      the data/items/customer response's property type/format changed from / to object null/ for status 200

      response-property-type-changed

    • ▲

      the data/items/depositToAccount response's property type/format changed from / to object null/ for status 200

      response-property-type-changed

    • ▲

      the data/items/paymentMethod response's property type/format changed from / to object null/ for status 200

      response-property-type-changed

    • ▲

      the data/items/receivablesAccount response's property type/format changed from / to object null/ for status 200

      response-property-type-changed

    • ●

      added the new amount enum value to the data/items/appliedToTransactions/items/linkedTransactions/items/linkType response property for the response status 200

      response-property-enum-value-added

    • ●

      added the new quantity enum value to the data/items/appliedToTransactions/items/linkedTransactions/items/linkType response property for the response status 200

      response-property-enum-value-added

    • ●

      added the new undefined enum value to the data/items/appliedToTransactions/items/linkedTransactions/items/linkType response property for the response status 200

      response-property-enum-value-added

    • ○

      removed the pattern ^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))$ from the query request parameter transactionDateFrom

      request-parameter-pattern-removed

    • ○

      removed the pattern ^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))$ from the query request parameter transactionDateTo

      request-parameter-pattern-removed

    • ○

      removed qbd_credit_card_transaction subschema #2 from the data/items/creditCardTransaction response property anyOf list for the response status 200

      response-property-any-of-removed

    • ○

      removed subschema #1 subschema #2 from the data/items/appliedToTransactions/items/discountAccount response property anyOf list for the response status 200

      response-property-any-of-removed

    • ○

      removed subschema #1 subschema #2 from the data/items/appliedToTransactions/items/discountClass response property anyOf list for the response status 200

      response-property-any-of-removed

    • ○

      removed subschema #1 subschema #2 from the data/items/currency response property anyOf list for the response status 200

      response-property-any-of-removed

    • ○

      removed subschema #1 subschema #2 from the data/items/customer response property anyOf list for the response status 200

      response-property-any-of-removed

    • ○

      removed subschema #1 subschema #2 from the data/items/depositToAccount response property anyOf list for the response status 200

      response-property-any-of-removed

    • ○

      removed subschema #1 subschema #2 from the data/items/paymentMethod response property anyOf list for the response status 200

      response-property-any-of-removed

    • ○

      removed subschema #1 subschema #2 from the data/items/receivablesAccount response property anyOf list for the response status 200

      response-property-any-of-removed

    • ○

      response property data/items/appliedToTransactions/items/amount list-of-types was narrowed by removing types null from media type application/json of response 200

      response-property-list-of-types-narrowed

    • ○

      response property data/items/appliedToTransactions/items/balanceRemaining list-of-types was narrowed by removing types null from media type application/json of response 200

      response-property-list-of-types-narrowed

    • ○

      response property data/items/appliedToTransactions/items/discountAmount list-of-types was narrowed by removing types null from media type application/json of response 200

      response-property-list-of-types-narrowed

    • ○

      response property data/items/appliedToTransactions/items/linkedTransactions/items/amount list-of-types was narrowed by removing types null from media type application/json of response 200

      response-property-list-of-types-narrowed

    • ○

      response property data/items/appliedToTransactions/items/linkedTransactions/items/linkType list-of-types was narrowed by removing types null from media type application/json of response 200

      response-property-list-of-types-narrowed

    • ○

      response property data/items/appliedToTransactions/items/linkedTransactions/items/refNumber list-of-types was narrowed by removing types null from media type application/json of response 200

      response-property-list-of-types-narrowed

    • ○

      response property data/items/appliedToTransactions/items/refNumber list-of-types was narrowed by removing types null from media type application/json of response 200

      response-property-list-of-types-narrowed

    • ○

      response property data/items/appliedToTransactions/items/transactionDate list-of-types was narrowed by removing types null from media type application/json of response 200

      response-property-list-of-types-narrowed

    • ○

      response property data/items/exchangeRate list-of-types was narrowed by removing types null from media type application/json of response 200

      response-property-list-of-types-narrowed

    • ○

      response property data/items/externalId list-of-types was narrowed by removing types null from media type application/json of response 200

      response-property-list-of-types-narrowed

    • ○

      response property data/items/memo list-of-types was narrowed by removing types null from media type application/json of response 200

      response-property-list-of-types-narrowed

    • ○

      response property data/items/refNumber list-of-types was narrowed by removing types null from media type application/json of response 200

      response-property-list-of-types-narrowed

    • ○

      response property data/items/totalAmountInHomeCurrency list-of-types was narrowed by removing types null from media type application/json of response 200

      response-property-list-of-types-narrowed

    • ○

      response property data/items/unusedCredits list-of-types was narrowed by removing types null from media type application/json of response 200

      response-property-list-of-types-narrowed

    • ○

      response property data/items/unusedPayment list-of-types was narrowed by removing types null from media type application/json of response 200

      response-property-list-of-types-narrowed

    • ○

      response property nextCursor list-of-types was narrowed by removing types null from media type application/json of response 200

      response-property-list-of-types-narrowed

    • ○

      response property remainingCount list-of-types was narrowed by removing types null from media type application/json of response 200

      response-property-list-of-types-narrowed

    • ○

      the data/items/appliedToTransactions/items/linkedTransactions/items/transactionDate response's property pattern ^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))$ was removed for the status 200

      response-property-pattern-removed

    • ○

      the data/items/transactionDate response's property pattern ^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))$ was removed for the status 200

      response-property-pattern-removed

    • ○

      added the required property data/items/appliedToTransactions/items/discountAccount/fullName to the response with the 200 status

      response-required-property-added

    • ○

      added the required property data/items/appliedToTransactions/items/discountAccount/id to the response with the 200 status

      response-required-property-added

    • ○

      added the required property data/items/appliedToTransactions/items/discountClass/fullName to the response with the 200 status

      response-required-property-added

    • ○

      added the required property data/items/appliedToTransactions/items/discountClass/id to the response with the 200 status

      response-required-property-added

    • ○

      added the required property data/items/currency/fullName to the response with the 200 status

      response-required-property-added

    • ○

      added the required property data/items/currency/id to the response with the 200 status

      response-required-property-added

    • ○

      added the required property data/items/customer/fullName to the response with the 200 status

      response-required-property-added

    • ○

      added the required property data/items/customer/id to the response with the 200 status

      response-required-property-added

    • ○

      added the required property data/items/depositToAccount/fullName to the response with the 200 status

      response-required-property-added

    • ○

      added the required property data/items/depositToAccount/id to the response with the 200 status

      response-required-property-added

    • ○

      added the required property data/items/paymentMethod/fullName to the response with the 200 status

      response-required-property-added

    • ○

      added the required property data/items/paymentMethod/id to the response with the 200 status

      response-required-property-added

    • ○

      added the required property data/items/receivablesAccount/fullName to the response with the 200 status

      response-required-property-added

    • ○

      added the required property data/items/receivablesAccount/id to the response with the 200 status

      response-required-property-added

  • 5f832f6956754014See the full diff
    • ▲

      added the pattern ^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))$ to the query request parameter transactionDateFrom

      request-parameter-pattern-added

    • ▲

      added the pattern ^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))$ to the query request parameter transactionDateTo

      request-parameter-pattern-added

    • ▲

      response property data/items/appliedToTransactions/items/amount list-of-types was widened by adding types null to media type application/json of response 200

      response-property-list-of-types-widened

    • ▲

      response property data/items/appliedToTransactions/items/balanceRemaining list-of-types was widened by adding types null to media type application/json of response 200

      response-property-list-of-types-widened

    • ▲

      response property data/items/appliedToTransactions/items/discountAmount list-of-types was widened by adding types null to media type application/json of response 200

      response-property-list-of-types-widened

    • ▲

      response property data/items/appliedToTransactions/items/linkedTransactions/items/amount list-of-types was widened by adding types null to media type application/json of response 200

      response-property-list-of-types-widened

    • ▲

      response property data/items/appliedToTransactions/items/linkedTransactions/items/linkType list-of-types was widened by adding types null to media type application/json of response 200

      response-property-list-of-types-widened

    • ▲

      response property data/items/appliedToTransactions/items/linkedTransactions/items/refNumber list-of-types was widened by adding types null to media type application/json of response 200

      response-property-list-of-types-widened

    • ▲

      response property data/items/appliedToTransactions/items/refNumber list-of-types was widened by adding types null to media type application/json of response 200

      response-property-list-of-types-widened

    • ▲

      response property data/items/appliedToTransactions/items/transactionDate list-of-types was widened by adding types null to media type application/json of response 200

      response-property-list-of-types-widened

    • ▲

      response property data/items/exchangeRate list-of-types was widened by adding types null to media type application/json of response 200

      response-property-list-of-types-widened

    • ▲

      response property data/items/externalId list-of-types was widened by adding types null to media type application/json of response 200

      response-property-list-of-types-widened

    • ▲

      response property data/items/memo list-of-types was widened by adding types null to media type application/json of response 200

      response-property-list-of-types-widened

    • ▲

      response property data/items/refNumber list-of-types was widened by adding types null to media type application/json of response 200

      response-property-list-of-types-widened

    • ▲

      response property data/items/totalAmountInHomeCurrency list-of-types was widened by adding types null to media type application/json of response 200

      response-property-list-of-types-widened

    • ▲

      response property data/items/unusedCredits list-of-types was widened by adding types null to media type application/json of response 200

      response-property-list-of-types-widened

    • ▲

      response property data/items/unusedPayment list-of-types was widened by adding types null to media type application/json of response 200

      response-property-list-of-types-widened

    • ▲

      response property nextCursor list-of-types was widened by adding types null to media type application/json of response 200

      response-property-list-of-types-widened

    • ▲

      response property remainingCount list-of-types was widened by adding types null to media type application/json of response 200

      response-property-list-of-types-widened

    • ▲

      the data/items/appliedToTransactions/items/discountAccount response's property type/format changed from object null/ to / for status 200

      response-property-type-changed

    • ▲

      the data/items/appliedToTransactions/items/discountClass response's property type/format changed from object null/ to / for status 200

      response-property-type-changed

    • ▲

      the data/items/currency response's property type/format changed from object null/ to / for status 200

      response-property-type-changed

    • ▲

      the data/items/customer response's property type/format changed from object null/ to / for status 200

      response-property-type-changed

    • ▲

      the data/items/depositToAccount response's property type/format changed from object null/ to / for status 200

      response-property-type-changed

    • ▲

      the data/items/paymentMethod response's property type/format changed from object null/ to / for status 200

      response-property-type-changed

    • ▲

      the data/items/receivablesAccount response's property type/format changed from object null/ to / for status 200

      response-property-type-changed

    • ▲

      removed the required property data/items/appliedToTransactions/items/discountAccount/fullName from the response with the 200 status

      response-required-property-removed

    • ▲

      removed the required property data/items/appliedToTransactions/items/discountAccount/id from the response with the 200 status

      response-required-property-removed

    • ▲

      removed the required property data/items/appliedToTransactions/items/discountClass/fullName from the response with the 200 status

      response-required-property-removed

    • ▲

      removed the required property data/items/appliedToTransactions/items/discountClass/id from the response with the 200 status

      response-required-property-removed

    • ▲

      removed the required property data/items/currency/fullName from the response with the 200 status

      response-required-property-removed

    • ▲

      removed the required property data/items/currency/id from the response with the 200 status

      response-required-property-removed

    • ▲

      removed the required property data/items/customer/fullName from the response with the 200 status

      response-required-property-removed

    • ▲

      removed the required property data/items/customer/id from the response with the 200 status

      response-required-property-removed

    • ▲

      removed the required property data/items/depositToAccount/fullName from the response with the 200 status

      response-required-property-removed

    • ▲

      removed the required property data/items/depositToAccount/id from the response with the 200 status

      response-required-property-removed

    • ▲

      removed the required property data/items/paymentMethod/fullName from the response with the 200 status

      response-required-property-removed

    • ▲

      removed the required property data/items/paymentMethod/id from the response with the 200 status

      response-required-property-removed

    • ▲

      removed the required property data/items/receivablesAccount/fullName from the response with the 200 status

      response-required-property-removed

    • ▲

      removed the required property data/items/receivablesAccount/id from the response with the 200 status

      response-required-property-removed

    • ○

      added qbd_credit_card_transaction subschema #2 to the data/items/creditCardTransaction response property anyOf list for the response status 200

      response-property-any-of-added

    • ○

      added subschema #1 subschema #2 to the data/items/appliedToTransactions/items/discountAccount response property anyOf list for the response status 200

      response-property-any-of-added

    • ○

      added subschema #1 subschema #2 to the data/items/appliedToTransactions/items/discountClass response property anyOf list for the response status 200

      response-property-any-of-added

    • ○

      added subschema #1 subschema #2 to the data/items/currency response property anyOf list for the response status 200

      response-property-any-of-added

    • ○

      added subschema #1 subschema #2 to the data/items/customer response property anyOf list for the response status 200

      response-property-any-of-added

    • ○

      added subschema #1 subschema #2 to the data/items/depositToAccount response property anyOf list for the response status 200

      response-property-any-of-added

    • ○

      added subschema #1 subschema #2 to the data/items/paymentMethod response property anyOf list for the response status 200

      response-property-any-of-added

    • ○

      added subschema #1 subschema #2 to the data/items/receivablesAccount response property anyOf list for the response status 200

      response-property-any-of-added

    • ○

      removed the amount enum value from the data/items/appliedToTransactions/items/linkedTransactions/items/linkType response property for the response status 200

      response-property-enum-value-removed

    • ○

      removed the quantity enum value from the data/items/appliedToTransactions/items/linkedTransactions/items/linkType response property for the response status 200

      response-property-enum-value-removed

    • ○

      removed the undefined enum value from the data/items/appliedToTransactions/items/linkedTransactions/items/linkType response property for the response status 200

      response-property-enum-value-removed

    • ○

      removed qbd_credit_card_transaction subschema #2 from the data/items/creditCardTransaction response property oneOf list for the response status 200

      response-property-one-of-removed

    • ○

      the data/items/appliedToTransactions/items/linkedTransactions/items/transactionDate response's property pattern ^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))$ was added for the status 200

      response-property-pattern-added

    • ○

      the data/items/transactionDate response's property pattern ^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))$ was added for the status 200

      response-property-pattern-added