HomeDocumentationAPI ReferenceRelease NotesRecipesPartner with UsLegal
Release Notes
Back to All

Release notes v2.9.9.7.1 | August 10th, 2020

over 4 years ago by Zachary Speltz

Customer API:

  • Treez has updated the way merged customers are displayed through our API, enabling Partners and operators to better track merged profiles. When using GET/ Customer endpoints, the resulting post-merge account will be the primary and have a value called MERGED_CUSTOMER_IDS associated with it. This field will display all profile IDs that have been merged into the resulting account, and will have a STATUS listed as ‘MERGED’. On top of that, a note will be added into the NOTES field that details the time and date of when the merge occurred. When using the GET/ Customer endpoints with merged and deactivated profiles you’ll see similar behavior as with an active profile. The STATUS for a merged and deactivated account will be listed as ’DEACTIVATED’ and associated with a new field called MERGED_INTO_CUSTOMER_ID which will display the member ID that profile was merged into.

  • The changes to our APIs for Merged profiles also carries over to our Update Customer API. When you attempt to use the Update Customer API with an account that has been merged and deactivated the request will fail and Treez will return an error message that will include the Member ID for MERGED_INTO_CUSTOMER_ID (i.e. the resulting customer profile).

  • There is a new event that will trigger our customer webhooks. Whenever two accounts have been merged in Treez you’ll receive separate payloads for both the surviving profile and the merged/deactivated profile. The payloads will include the values MERGED_INTO_CUSTOMER_ID and MERGED_CUSTOMER_IDS.

  • A new fix is headed your way! Previously, when the config MEDICAL_ID_REQUIRED was enabled it would require both MEDICAL and MEDICAL_MMID patient types to have an MMID number when generating a new account with the Treez API. With the new fix, when MEDICAL_ID_REQUIRED is enabled the Create Customer API will only require MEDICAL_MMID patients to have a MMID number associated with their account upon creation.

Ticket API

  • A new change has been made with the fulfillment board in Treez that will impact tickets generated through the API. Going forward, the “Verification Skipped” warning will no longer display on orders associated with previously verified customers.