25.1 April Service Pack

Settings: External Organizations - TPOs (update)

The V3 Get External Organization API has been enhanced to return Fee Setup information including TPO Fees collection and Late Fees settings for a given organization. The following new "entities" filters were added:

• TpoFees
• LateFees
• FeeSetup - Includes both TpoFees and LateFees

EDC-1110

Webhooks

The following new events were added to the ServiceOrder Webhook resource:

• deliveryFailed
• fulfillmentFailed

EDC-1136

Fixed Issue

EDC-1139 - An issue was observed in certain situations when working with a rate lock request that has been extended multiple times (usually 3 or more). When updating the Buy Side section with the V1 Update a Rate Lock Request API, the latest Buy Side lock price adjustments can be replaced with values from the original Buy Side lock extension price adjustment.

With this fix, the following scenarios now occur:

• If the user includes buyside.LockExtendPriceAdjustment (field 3365) in the payload, it will be set to the last extension adjustment in the 'buySide.adjustments' object.
• If the user does not include buyside.LockExtendPriceAdjustment (field 3365) in the payload, the extension adjustments in the 'buySide.adjustments' object will be set in the order in which they were provided in the request payload.

📘

Best Practice

When updating a rate lock extension request, the Buy Side data will automatically be updated on the extension request based on the extension request submitted. Therefore, there is no need to submit Buy Side data when updating a rate lock extension request. If you do send Buy Side data in a rate lock extension request, the buyside adjustments should ideally be provided in the sequential order in which the extension requests originally occurred. Retrieve the Rate Lock Request to get the sequential order of the adjustments.