[SUPERSEDED] Response body changes for some Delete methods

Announcements
1

Category: API

Summary: Superseded by the new announcement

API endpoints are changing the way responses are returned when an empty 200 response is returned from some DELETE endpoints.

Context: Previously when a DELETE request was sent, a 200 status code and a response body of 'null' was returned. Due to an upgrade in a third party serialization library, This API as of effective date below will not return a response body when the body is empty (e.g. content-length:0)

Impact: Any clients that are depending on a populated response body for these API endpoints may now incur unexpected errors, clients should rely on the HTTP status code of the response before checking a response body.

Note: No other 2xx responses are impacted

Date of Change: On or after 14/01/2020

Impacted APIs: External Contacts

DELETE /api/v2/externalcontacts/contacts/{contactId}/notes/{noteId}

DELETE /api/v2/externalcontacts/contacts/{contactId}

DELETE /api/v2/externalcontacts/organizations/{externalOrganizationId}/notes/{noteId}

DELETE /api/v2/externalcontacts/organizations/{externalOrganizationId}

DELETE /api/v2/externalcontacts/relationships/{relationshipId}

PUT /api/v2/externalcontacts/organizations/{externalOrganizationId}/trustor/{trustorId}

DELETE /api/v2/externalcontacts/organizations/{externalOrganizationId}/trustor

2