Legacy Dev Forum Posts

 View Only

Sign Up

Back to discussions
Expand all | Collapse all

Adding Multiple Wrap-Up Codes

  • 1.  Adding Multiple Wrap-Up Codes

    Posted 06-05-2025 18:21

    jheckbert | 2022-01-20 16:18:53 UTC | #1

    Hi there,

    I am new to Genesys Cloud and looking for a way to add many wrap-up codes to the system. I found in API explorer this for adding:

    { "name": "Wrap-up1", "dateCreated": "", "dateModified": "", "modifiedBy": "", "createdBy": "" }

    I have a few questions for this :slight_smile:

    1. Do I leave the "optional" fields blank if I don't put anything there?
    2. Looking to understand what the above looks like if I want to add multiple codes at one time. Example Wrap-Up1, Wrap-Up2, etc....

    tim.smith | 2022-01-20 16:27:38 UTC | #2

    Welcome to Genesys Cloud!

    You can use POST /api/v2/routing/wrapupcodes to create new wrap up codes. You cannot create more than one at a time; there is no bulk variety of this endpoint. Once created, you can bulk assign them to queues using POST /api/v2/routing/queues/{queueId}/wrapupcodes.

    jheckbert, post:1, topic:13272
    Do I leave the "optional" fields blank if I don't put anything there?

    The only property you should set is name. The rest are meant to be readonly for the request.

    jheckbert, post:1, topic:13272
    Looking to understand what the above looks like if I want to add multiple codes at one time. Example Wrap-Up1, Wrap-Up2, etc....

    Make multiple requests. Be sure to take note of the Platform API Rate Limits and associated API behavior when making many requests quickly.

    jheckbert | 2022-01-20 16:30:17 UTC | #3

    Thank you Tim!

    Much appreciate the quick response and great infomation!!

    Eos_Rios | 2022-01-20 16:35:40 UTC | #4

    jheckbert, post:1, topic:13272
    { "name": "Wrap-up1", "dateCreated": "", "dateModified": "", "modifiedBy": "", "createdBy": "" }

    Just in case Tim wasn't clear, the general way to handle optional fields is to not supply them at all, not to leave them blank, so literally just send;

    { "name": "Wrap-up1" }

    And only supply elements you want to explicitly set/send values for.

    jheckbert | 2022-01-20 16:48:00 UTC | #5

    Eos_Rios, post:4, topic:13272
    Just in case Tim wasn't clear, the general way to handle optional fields is to not supply them at all, not to leave them blank, so literally just send; 
    {
"name": "Wrap-up1"
}

    And only supply elements you want to explicitly set/send values for.

    Great clarification!

    system | 2022-02-20 16:47:36 UTC | #6

    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: 13272



Related Content