Legacy Dev Forum Posts

 View Only

Sign Up

Back to discussions
Expand all | Collapse all

Issue with PUT /api/v2/quality/surveys/scorable API

  • 1.  Issue with PUT /api/v2/quality/surveys/scorable API

    Posted 06-05-2025 18:29

    Siemff | 2024-02-09 10:13:28 UTC | #1

    Hello,

    We are currently working on implementing a custom solution for feedback management in Genesys Cloud. Our objective is to send text messages (via LINK Mobility) to customers, asking them to rate their satisfaction on a scale of 1-6 without including a link, as per business requirements.

    To achieve this, we are planning to build a custom app running in Azure that receives SMS messages through LINK Mobility. By using necessary APIs on the Genesys side. Out current challenge lies in utilizing the PUT /api/v2/quality/surveys/scorable API. We are not able to excute the API action. It says: Non-standard Authorization Warning This resource does not require authorization; the Authorization header should be omitted from this request.

    Here is a brief outline of our solution:

    1. Receive an SMS (via LinkMobility) in a custom app hosted in Azure.
    2. Use the POST /api/v2/analytics/conversations/details/query API to identify conversations related to the specific phone number. If a conversation with a conversationId is found, proceed to step #3.
    3. Utilize the GET /api/v2/quality/conversations/{conversationId}/surveys API with the identified conversationId. This API returns a list of surveys associated with the conversation. If the list contains one element, extract the selfUri and move to step #4.
    4. Use the PUT /api/v2/quality/surveys/scorable API to update the survey with the customer's response.

    The issue arises when we attempt to use the PUT /api/v2/quality/surveys/scorable API. We are encountering difficulties, and despite thorough testing, we have not been able to resolve the problem.

    We would appreciate any insights, guidance, or examples from the community regarding the correct implementation of the PUT /api/v2/quality/surveys/scorable API in this context. If there are alternative approaches or best practices that we should consider, we would be grateful for that information as well.

    Thank you in advance for your assistance.

    Best regards,

    Siem

    Eos_Rios | 2024-02-09 15:49:39 UTC | #2

    Have you tried doing what the error, and documentation, say to do, and not including the authorization header on that particular call?

    system | 2024-03-10 15:50:20 UTC | #3

    This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

    This post was migrated from the old Developer Forum.

    ref: 24566



Related Content