Ben_Marks | 2017-01-10 15:51:18 UTC | #1
To prove that Payroll exists:
curl -X GET \
-H "Authorization: bearer [redacted]" \
-H "Content-Type: application/json" \
https://api.mypurecloud.com/api/v2/groups
... "id": "a4578397-5dab-47bf-9c91-dff729f1a31a", "name": "Payroll" ...
Then I try to search for it:
curl -X POST \
-H "Authorization: bearer <redacted>" \
-H "Content-Type: application/json" \
-d '{"query": [{"fields": ["name"], "value": "Payroll", "type": "EXACT"}]}' \
https://api.mypurecloud.com/api/v2/groups/search
{"status":404,"code":"not.found","message":"Resource not found in Microservice Service","contextId":"99be22fa-e0a8-4f25-b8c5-24106b696ba5","details":[],"errors":[]}
Not sure what is going on as this was working as recently as last week. Normally this is done via the javascript SDK but curl produces the exact same response.
tim.smith | 2017-01-09 22:41:46 UTC | #2
Issue SRCH-1066 has been opened to look into this. The cause is that a new feature was rolled out to check the user's permissions, but client credentials don't have a user context. Currently, the only way to work around this is to log in with a user (implicit or auth code OAuth flows) and make the request.
sean.allison | 2017-01-10 00:18:19 UTC | #3
Searches for public groups (groups with public visibility) will work with client credentials after this ticket is resolved. The ticket @tim.smith mentioned is in review and will be resolved shortly.
system | 2017-08-28 19:29:47 UTC | #4
This post was migrated from the old Developer Forum.
ref: 773