Programmatic Wrap-Up Code Assignment via Conversations API

We’re trying to enforce specific wrap-up codes based on interaction metadata. The goal is to programmatically assign a wrap-up code to a participant after the agent clicks end. The platform does not expose a direct endpoint to set a wrap-up code on a specific conversation participant via a simple POST request to a wrap-up path; instead, wrap-up codes are typically managed through the routing configuration or applied via the conversation disconnect process.

Getting a 409 Conflict with code_already_set. Is there a way to override or check status first without polling? Just want to ensure the trace context hits the correct queue before the code locks.

3 Likes