Transaction Search API not working as documented about cybersource-rest-client-dotnet HOT 1 OPEN

Just got this email yesterday that went out to all cybersource customers! Looks like they are making a change in the API design to follow what is documented online.

Dear Merchant:
Cybersource is updating the HTTP response code returned by the Transaction Search REST API in certain scenarios.
When your search criteria does not match any transactions, the API currently responds with a response code of 404. With the upcoming update, we will change the response code to 201, in conformance with the published API specification.
As part of this change, the API response will contain a "totalCount" field with a value of ‘0’, which indicates to the client that there were ‘0’ transactions that matched the search criteria.
This update will go into effect early September. For more information about Transaction Search API, see the API Developer Guides in the Cybersource Developer Center.

Regards,
CyberSource Customer Support

For your reference, in the “no transactions found” scenario, see this sample JSON response body which accompanies an HTTP 201 response code.
Sample 201 Response:
{
"_links": {
"self": {
"href": "https://apitest.cybersource.com/tss/v2/searches/5106e95c-024b-4237-adc7-test123456",
"method": "GET"
}
},
"searchId": "5106e95c-024b-4237-adc7-test123456",
"save": false,
"name": "MRN",
"query": "clientReferenceInformation.code:invalidMRN AND submitTimeUtc:[NOW/DAY-7DAYS TO NOW/DAY+1DAY}",
"count": 0,
"totalCount": 0,
"limit": 100,
"offset": 0,
"sort": "id:asc,submitTimeUtc:asc",
"timezone": "America/Chicago",
"submitTimeUtc": "2019-08-21T18:27:19Z"
}

from cybersource-rest-client-dotnet.