Genesys Cloud - Developer Announcements!

 View Only

Sign Up

Back to discussions
Expand all | Collapse all

Caseplan Endpoints Return 400 Instead of 404 for Deleted defaultCaseOwnerId

  • 1.  Caseplan Endpoints Return 400 Instead of 404 for Deleted defaultCaseOwnerId

    Posted 3 hours ago

    Summary

    The following Case Management endpoints now return 400 Bad Request with the error code owner.deleted when the defaultCaseOwnerId references a deleted user:

    • POST /api/v2/casemanagement/caseplans
    • PATCH /api/v2/casemanagement/caseplans/{caseplanId}

    The returned error message is:

    “The owner with id [x] is deleted and cannot be assigned as case owner.”

    Previously, these endpoints returned:

    • HTTP Status: 404 Not Found
    • Error Code: not.found
    • Message: “The owner with id [x] was not found.”

    Effective Date

    Monday, July 13, 2026

    Details

    The previous 404 Not Found response was misleading because the referenced user still existed but had been deleted and therefore could not be assigned as a case owner.

    Returning a 400 Bad Requestwith a dedicated owner.deletederror code provides more accurate information and allows clients to distinguish between a non-existent user and a deleted user.

    Customer Impact

    Applications that specifically handle a 404 Not Found response when assigning a defaultCaseOwnerId must be updated to handle:

    • HTTP Status: 400 Bad Request
    • Error Code: owner.deleted

    Customer Action Required

    Customers should review any integrations, automation, or custom applications that create or update caseplans and:

    • Update error-handling logic to recognize 400 Bad Request responses with the owner.deleted error code.
    • Remove any assumptions that a deleted owner will result in a 404 Not Foundresponse.

    Failure to update error-handling logic may result in unexpected behavior when processing validation errors related to deleted case owners.

    This change affects a very narrow error path that occurs only when a client attempts to create or update a caseplan using a defaultCaseOwnerId that references a user who has been deleted.

    No customer impact is expected. The change does not affect successful requests and only improves the accuracy of the error returned for an already-invalid request.

    Impacted Resources

    • POST /api/v2/casemanagement/caseplans
    • PATCH /api/v2/casemanagement/caseplans/{caseplanId}

    Issue References

    WORKITEMS-7524

    Contacts

    @Luke Hebblethwaite  

    Please reply to this announcement with any questions. This helps the wider developer community benefit from the discussion. We encourage you to use this thread before contacting the designated person directly. Thank you for your understanding.



Related Content