anon35336826 | 2021-05-26 15:38:05 UTC | #1
Category: API
Summary: Change to response code for certain bulk division update scenarios for Messaging Campaigns
Context: Currently, if updating messaging campaigns' divisions via /api/v2/authorization/divisions/{divisionId}/objects/messagingcampaign, when any entity fails to update the operation will immediately abort and return a generic "500 Internal Server Error" response. That case will be updated to return a "409 Conflict" with the detail code "bulk.move.unable.to.move", which will make it consistent with the rest of the /api/v2/authorization/divisions/{divisionId}/objects/{objectType} endpoints. It will also update all entities that it can and report on all entities it could not update in the error response, which is also more consistent with the other endpoints. Other cases that currently return a 500 will continue to behave as they do now.
Impact: When calling this endpoint, error handling should now also handle 409 Conflict responses if it does not. There is no evidence that this error case has been encountered by any customer in at least the last 30 days.
Date of Change: No later than June 4, 2021
Impacted APIs:
- /api/v2/authorization/divisions/{divisionId}/objects/messagingcampaign
References: OD-199
system | 2021-06-26 15:38:44 UTC | #2
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 11029