Hi Patti,
From my understanding, the key difference may be that the surveys generated through recording policies are created as part of the normal conversation-linked survey lifecycle, which makes them retrievable/scorable through the /quality/surveys/scorable APIs.
Whereas POST /api/v2/quality/surveys appears to generate more of a standalone direct survey URL rather than the same internally managed "scorable" survey instance.
That may explain why:
- the direct survey URL itself works
- but retrieving/scoring it through /quality/surveys/scorable returns 404.
So from my understanding, the scorable APIs may only work for surveys originating from the standard conversation/recording-policy survey flow rather than standalone direct survey creation.
Hope this helps.
------------------------------
Phaneendra
Technical Solutions Consultant
------------------------------
Original Message:
Sent: 05-15-2026 18:51
From: Patti Oaks
Subject: Score a direct web survey
We are using the
post /api/v2/quality/surveys to generate a direct survey link for a web message.
Instead of displaying the URL to the customer we are using the inbound message flow to ask the customer the survey questions and obtaining the answers.
This worked for us when creating the URL via the recording policy and adding the survey but does not seem to be working using the post /api/v2/quality/surveys
We have tried get /api/v2/quality/surveys/scorable to retrieve the direct web survey (using the url from the post) but we are getting a 404 not found error.
Is there a reason we can't retrieve and score a direct web survey versus being able to via a web survey using the recording policies?
#WebMessaging
------------------------------
Patti Oaks
Engineer
------------------------------