Recent searches


No recent searches

Sell APP Development



Posted Feb 08, 2022

Hi. im developing a sell app integration, but im having trouble with the location of the app.

This is my manifest file:

"location": {
    "sell": {
      "person_card":"assets/iframe.html",
      "lead_card":"assets/iframe.html",
      "deal_card": "assets/iframe.html"
    }
  }
 
For some reason, the apps only loads on the lead card location. Besides this, im calling a rest api from the client.request(). On support works fine (the same app, same endpoint, etc) but on sell it gives an cors error.

0

2

2 comments

image avatar

Eric Nelson

Zendesk Developer Advocacy

Hey there,

Currently only chat and support apps support multiple locations. We talk about it here.
 

You can also specify multiple locations across Zendesk products in your manifest file (currently only Zendesk Support and Zendesk Chat are supported). Example:

 
For your api request, to confirm you're calling a third-party endpoint? Would you be able to provide a code snippet so I can take a look?

Thanks!

0


Thanks for your help, we solved the location issue.

Below we'll send you a code snippet regarding the request which is blocked by CORS policy.
 
function getTemplates() {
  var requestOptions = {
        url: "https://api.smooch.io/v1.1/apps/" + appidSunco + "/integrations/" + integrationIdSunco + "/messageTemplates",
      type: 'GET',
      headers: { "Authorization": "Basic " + apikeySunco },
      dataType: 'json'
  };
  client.request(requestOptions)
      .then(function (data) {
          doSomething(data);
      });
}

This function on Support works fine, but on sell we get the following CORS error:
 
Access to XMLHttpRequest at 'https://guruyu.proxy.futuresimple.com/proxy/v2/to/https%3A%2F%2Fapi.smooch.io%2Fv1.1%2Fapps%2F6078c86da31211500d4685703%2Fintegrations%2F61978eb887216600e84402c3%2FmessageTemplates' from origin 'https://app.futuresimple.com' has been blocked by CORS policy: The value of the 'Access-Control-Allow-Credentials' header in the response is '' which must be 'true' when the request's credentials mode is 'include'. The credentials mode of requests initiated by the XMLHttpRequest is controlled by the withCredentials attribute.
 
Thanks in advance

0


Please sign in to leave a comment.

Didn't find what you're looking for?

New post