Genesys Cloud - Developer Community!

 View Only

Sign Up

  • 1.  Question about the structure of the topic v2.conversations.{id}.transcription

    Posted 06-04-2026 04:05
    Edited by Stéphane Labrune 06-04-2026 09:15

    "Hello,

    with the events from the topic v2.conversations.{id}.transcription, in which cases can I have more than one element in the alternatives array (detail.eventBody.transcripts.alternatives) ? 

    Comparing with the REST API results, I don't see in which case this is possible."

    Best regards.


    #PlatformAPI

    ------------------------------
    Stéphane Labrune
    NA
    ------------------------------



  • 2.  RE: Question about the structure of the topic v2.conversations.{id}.transcription

    Posted 06-04-2026 12:27

    Hello,

    I have just checked with the engineering team in charge of speech analytics.

    The fact that multiple values were possible in the alternatives property is for legacy reasons. Some former speech analytics services which could send several alternatives.

    But it is not the case anymore. Now, Genesys Cloud will not send more than one alternative.

    Regards,



    ------------------------------
    Jerome Saint-Marc
    Senior Development Support Engineer
    ------------------------------



  • 3.  RE: Question about the structure of the topic v2.conversations.{id}.transcription

    Posted 06-05-2026 02:30

    Thank you for the response, it confirms what I observed.

    Regards,



    ------------------------------
    Stéphane Labrune
    NA
    ------------------------------

    Original Message


  • 4.  RE: Question about the structure of the topic v2.conversations.{id}.transcription

    Posted 06-05-2026 10:43

    Hi Stéphane,

    Thanks for confirming this with engineering - that aligns with what I've seen as well 👍

    Just to add a bit of context for others reading this:
    even though the alternatives array is still part of the event structure, it's effectively always a single element today, so it's safe to treat it that way in most implementations.

    That said, since it remains an array for backward compatibility, it's still a good practice to handle it generically (iterate instead of assuming index [0]) to stay future-proof.

    Best regards,

    Cesar



    ------------------------------
    Cesar Padilla
    INDRA COLOMBIA
    ------------------------------

    Original Message


Related Content