Skip to main content
All CollectionsTreez Product UpdatesSellTreez API
SellTreez API Product Update 56.0.0
SellTreez API Product Update 56.0.0
T
Written by Treez Admin
Updated over a week ago
HC-header (2).png

12/3/2023

NEW!

External Invoice API

New invoice payment information is available for read-only.

  1. New Field: 'outstanding_balance'

This field has been introduced to the response body and reflects the amount still owed on the invoice. The value is calculated as total_cost minus any payments already made.

  1. New Field: 'payment_status'

This field is now included in the response body, indicating the overall payment status of the invoice. The possible values are: DRAFT, PARTIALLY PAID, and PAID.

  1. New summary of all payments made. This payments array includes the following information:

  • payment_date: The date and time of the payment (e.g., 2023-05-19T10:00:01.000-07:00).

  • payment_user: The user name of the Treez user who applied the payment.

  • payment_amount: The amount of the payment.

  • transaction_type: The type of transaction, such as Cash Handling or Credit Note.

  • payment_source: The source for the payment (e.g., Account Name if transaction_type is Cash Handling, or N/A if transaction_type is Credit Note).

  • payment_notes: Any notes entered for the payment.

If there are no payments or the payment_status is DRAFT, the corresponding fields in the payments array will display NULL.

Fixes

External Ticket API

  • Resolved the problem of duplicate orders being created despite encountering a 504 error.

  • Restored the product-id on merged products.

External Product API

  • Resolved the issue where a new product record was created despite receiving a 400 response due to a duplicated barcode value.

External Ticket API Cash > POS Ticket Adjustment

  • Within the Ticket API, corrected an inconsistency in the rewards_points_used value for tickets involving rewards payments. The rewards payment portion of a ticket can no longer be modified in the POS Ticket Adjustment report.

Did this answer your question?