Category: API
Summary: API endpoints are changing the way responses are returned when an empty 200 response is returned from some DELETE endpoints.
Context: This supersedes the old announcement
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 and a status code of 204 will be returned. Update - see below.
Impact: Any clients that are depending on a populated response body or a 200 status code for these API endpoints may now incur unexpected errors, clients should expect a 204 with Content-length: 0
UPDATE The response status will stay as a 200 and a valid JSON body will be returned '{}', this is to prevent a breaking change and to align with the HTTP spec. Clients should expect a 200 response and a response body of {}.
Note: No other 2xx responses are impacted
Date of Change: On or after 8 February 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}
DELETE /api/v2/externalcontacts/organizations/{externalOrganizationId}/trustor