Problem Statement:.Update the Sandbox APIs Key with the Production API Key 

Ticket Number: 692274728656

JIRA Ticket: https://adjettercrm.atlassian.net/browse/PMP-7724; https://adjettercrm.atlassian.net/browse/PMP-6653

Client: Laundry Mate

Clarification Provided: If this is the previous auth key then, we can replace this in whatsapp configuration with- 

Current Auth Key in the system

cvVZKQgE9AMC7lwCMtFpUDLwOngpPL0/PQOSm4QjkHXYMHFaPQGOOF7CCCSektddiw2t4XBTr5c75nYC+b4c46Zlu7oOUliFs1hwK7im

 Have added the new product key in the WhatsApp configuration.

cvVZKQgE9AMC7lwAPdJpUDLwYnc4O7YcElydrZRXxwLOE3dYDVDJfEbHZiHl9OVbw2iTljJ70tYI0SNN/Z139swE9oIMUEWYsVRmKrn4PMk=.

Explanation: Updated Authentication Key for Kapture: cvVZKQgE9AMC7lwCMtFpUDLwOngpPL0/PQOSm4QjkHXYMHFaPQGOOF7CCCSektddiw2t4XBTr5c75nYC+b4c46Zlu7oOUliFs1hwK7im

The new API which was built, was to send the details of the ticket when it was resolved in our system. These new details were then sent to the vendor, through the API. Since there was a delay in receiving the details, the vendor shared a new Authentication/Product Key. This Product Key was then used in the configuration page (What’sApp Configuration Page)  for the vendor, and not for the API which was built from Kapture end.

To be Actioned: Complete correlation to be acquired. 

Alternative: However, the trigger can be added from “Ticket Escalation” instead of the “SMS Template” and make the configuration changes. This is applicable for internal purposes only, as the vendor will not receive these details.