Genesys Cloud - Developer Community!

 View Only

Sign Up

  • 1.  /api/v2/settings

    Posted 20 days ago

    Hi,
    I was asked to look at a bulk update to all users in an Org.  There is a setting called "thisBrowserIsTheOneToAnswerFrom" and the UI obtains this with a call to an API endpoint /api/v2/settings.  I don't see this on the API Explorer so it makes me think it's not expected to be used outside of the UI.
    It appears to require user credentials so doing a bulk update looks to be out of the question.
    The setting is reached by navigating to the Calls section for the logged in user then clicking the settings cog.  the setting on screen appears as "Placing calls with another app?".
    Anyone got a bright idea?  


    #PlatformAPI

    ------------------------------
    Paul Lewis
    DevOps Engineer
    ------------------------------


  • 2.  RE: /api/v2/settings

    Posted 20 days ago

    Good Day Paul

    I had a look in the console logs to see if there is perhaps another API that can be utilized but could not find anything,  I also found these 2 ideas created as Aha Ideas - https://genesyscloud.ideas.aha.io/ideas/TEL-I-327 & https://genesyscloud.ideas.aha.io/ideas/OP-I-656.  Unfortunately both Ideas are in the "Will not implement" state so I dont think this is something that will be implemented.

    Regards



    ------------------------------
    Stephan Taljaard
    EMBEDIT s.r.o
    ------------------------------



  • 3.  RE: /api/v2/settings

    Posted 19 days ago

    Genesys Cloud "RESTful API-first approach".



    ------------------------------
    Angus Huckle
    Chapter Lead
    ------------------------------

    Original Message


  • 4.  RE: /api/v2/settings
    Best Answer

    Posted 19 days ago

    Hi Paul,

    You're correct in your assumption-/api/v2/settings is an internal (UI-driven) endpoint and not part of the publicly supported Platform API surface. In practice, these types of settings are often tied to per-session or per-browser context, which explains why:

    • They require user-level authentication
    • They don't show up in the API Explorer
    • They are not exposed for administrative or bulk control

    The specific flag "thisBrowserIsTheOneToAnswerFrom" looks very much like a client-side preference used by the Genesys Cloud web app to control call-handling behavior for WebRTC/softphone selection. These are typically stored and enforced at the user agent/browser level, not as a centrally managed user attribute.

    What you can consider

    Even though bulk updating via API isn't feasible, there are a few angles worth evaluating:

    1. Policy / Process workaround
      If this setting is operationally important, some customers handle this via:

      • User onboarding instructions
      • Browser standardization (VDI, managed endpoints, etc.)
      • Enforcing usage of specific call methods (e.g., WebRTC vs. external phone)

    2. Genesys Cloud Embeddable Framework / SDKs
      If you control the client experience (e.g., embedding Genesys Cloud), you might be able to influence call behavior programmatically at runtime rather than relying on that setting.

    3. Telephony configuration alignment
      In some cases, similar outcomes can be achieved by adjusting:

      • Default station / phone assignments
      • WebRTC phone settings
      • Call handling behaviors via provisioning

    4. Browser profile management
      Since this is likely tied to browser state, centrally managed environments (e.g., Citrix, AVD, or Chrome profiles) could help ensure consistency without needing API access.

    Bottom line

    This isn't just an API limitation-it's more of a design boundary between platform configuration and client-side behavior. Unless Genesys decides to expose it as an admin-level setting, controlling it programmatically at scale isn't currently aligned with how the platform handles these preferences.

    Hope that helps add a bit more direction to the investigation.



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



  • 5.  RE: /api/v2/settings

    Posted 16 days ago

    Very well structured and thought out reply.
    Our developer had already come to the conclusion he's going to have to leverage an existing widget thats in use to do some background http get and put since the javascript SDK does not support this (due to I suppose no listing on the API developer page). 

    In Summary
    - Genesys use an endpoint in the UI that's not documented
    - We can use the same endpoint 
    - No Javascript SDK wrapper so has to be http get/put 

    As Angus pointed out in an earlier post, API-First might be true but it'd also be nice if API's used in UI were also made available in SDK's. :)



    ------------------------------
    Paul Lewis
    DevOps Engineer
    ------------------------------

    Original Message


Related Content