When running the agentless json from postman we get the below error, even though the body is the same as when we run it as a data action from Genesys
{
"message": "No WhatsAppIntegration could be found with an id of {id}",
"code": "not.found",
"status": 404,
"messageWithParams": "No {type} could be found with an id of {id}",
"messageParams": {
"id": "",
"type": "WhatsAppIntegration"
},
"contextId": "be5fa339-5eea-4b63-903b-8d96bea970a6",
"details": [],
"errors": []
}
@Stefanie_Morgan you could verify by taking your fromAddress value you are putting in the body of the request and calling get-api-v2-conversations-messaging-integrations-whatsapp--integrationId- putting the same integrationId in there. Currently it's saying that integrationId doesn't exist in that (your token you use in Postman contains the org context, some customers use a few different orgs, so you may want to verify that too)
we only have the one set up in the current org which is the ID shown above. We have ran the above request api from postman and got the below
{
"message": "No whatsapp Integration could be found with an id of 2b5a26a3-e8ad-49f4-b53c-54a28f997a8f",
"code": "not.found",
"status": 404,
"messageWithParams": "No {type} could be found with an id of {id}",
"messageParams": {
"id": "2b5a26a3-e8ad-49f4-b53c-54a28f997a8f",
"type": "whatsapp Integration"
},
"contextId": "296917b4-f869-471c-b544-4ba4f6ca6d69",
"details": [],
"errors": []
}
we are a division aware org and have enabled roles that are custom and default to the org to see if that made a difference and no such luck as it doesnt seem to be able to see the platform integration
Possibly someone deleted it from your org then? Either way both of those APIs seem to be in agreement, saying that integrationId is no longer in the org
Hi @Stefanie_Morgan i can't provide you direct support on this public forum as I would have to gather potential sensitive information from you to investigate on our side. Opening a case with contact-genesys-cloud-care is how you would proceed there.
If it were me here are the general steps I would take to investigate if I were you though
Log into the org using the UI and your username/password
Click the Admin link at the top then Account Settings -> Organization Settings. Clicked Advanced drop down and look at the OrganizationId. Is this the same as you expected?
Click the Admin link again at the top and go to Message -> Platforms screen. Find your Whatsapp integration and use the developer tools to find the IntegrationId for it, copy this for future reference.
Click the Admin link again at the top and go to Integrations -> Oauth. Find the Oauth client you were using to generate the token you used in Postman (to call the Agentless api). Validate the information is exactly the same as what you used in Postman.
Validate the #3 integrationId is the same as you used in Postman too.
Of these steps #4 is the one were you are likely to find a conflict. Because the Oauth client/token you used in Postman is how Genesys maps what Org you are using. I think you'll find an issue there. If you still have problems, please reach out to customer care for more help.