25.1 April Service Pack

📘

Scheduled for April 5, 2025

Settings: External Organizations - TPOs (update)

As part of a 25.1 Service Pack release scheduled for April 5th, 2025, the V3 Get External Organization API will be enhanced to return Fee Setup information including TPO Fees collection and Late Fees settings for a given organization. The following new "entities" filters are being added:

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

EDC-1110

Webhooks

As part of a 25.1 Service Pack release scheduled for April 5th, 2025, the following new events are being 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 or the V1 Submit a Rate Lock Request (with action=revise) 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 the 3365 field (the LockExtendPriceAdjustment) values in the payload, it will be set to the calculated FieldID (calculating fieldId based on the lockextensionsequence number).
• If the user does not include the 3365 field value in the payload, the calculated FieldID value will remain unchanged in the update rate lock API call.

📘

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, this will override what was automatically updated from the extension request.