Nirodha_Udwela | 2020-02-18 00:13:37 UTC | #1
Hey Guys,
I am new to using Purecloud API and not sure if this has been answered. But I am getting this 404 error when I am trying to get campaign schedule using postman. Below is the error I get. Not sure how to fix this.
{ "reason": "Not Found", "code": 404, "detail": "Entity [person] is not found by guid [f6b226e1-e7ec-44b2-89ff-4ff53fe17954]", "payload": { "code": "NOTFOUND", "entity": "person", "id": "f6b226e1-e7ec-44b2-89ff-4ff53fe17954" } }
anon28885283 | 2020-02-18 01:39:56 UTC | #2
Can you share the endpoint URI you're using? Also do you get the same error when you try to run it on the API Explorer?
Nirodha_Udwela | 2020-02-18 03:06:25 UTC | #3
Hey Prince,
this is the end point - https://apps.mypurecloud.com.au/api/v2/outbound/schedules/campaigns/18d05043-a14d-456b-9e27-3d781039ed81
it works when I use the developer tool and with my login. but I get an external error if i tried to do it again.
tim.smith | 2020-02-18 15:52:00 UTC | #4
I believe this endpoint doesn't work with client credentials. If f6b226e1-e7ec-44b2-89ff-4ff53fe17954 is your client ID, that's the case. You can open a case with PureCloud Care to report this error. I can't say if this resource not working with client credentials is a bug or a feature, but that error message means the resource isn't properly checking for client credentials; it should be throwing the not.a.user error as a 400 if this isn't supposed to work with client credentials, not a 404 on the user id.
Nirodha_Udwela | 2020-02-18 22:31:42 UTC | #5
Hey Tim,
Thanks for the help. I have created a support ticket, see what they say.
system | 2020-03-20 22:31:45 UTC | #6
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 7146