Proxy error: UnprocessableEntity, Failed to get installation and oauth information for app | The place for Zendesk users to come together and share
Skip to main content
January 20, 2022
Question

Proxy error: UnprocessableEntity, Failed to get installation and oauth information for app

  • January 20, 2022
  • 48 replies
  • 176 views

I have been guided here by Zendesk support, I am receiving the error Proxy error: {:code=>"UnprocessableEntity", :status=>"422", :title=>"Unprocessable Entity", :message=>"Failed to get installation and oauth information for app."} when I attempt to create a request to a 3rd party server, I have followed your extensive guide but still recieving the above.

48 replies

Parth14
March 25, 2024

Eric, Will, did you guys ever find a solution to this? I am attempting the exact same thing and getting this issue. 

manifest.json

 "location": {
    "support": {
      "nav_bar": "assets/iframe.html"
    }
  },
  "parameters": [
    {
      "name": "access_token",
      "type": "oauth"
    }
  ],
  "oauth": {
    "client_id": "*********************************",
    "client_secret": "**********************************",
    "access_token_uri": "https://app.ninjarmm.com/oauth/token",
    "scopes": [
      "control monitoring management"
    ]
  },

bottom of iframe.html
  <script>
    // Initialise Apps framework client. See also:
    var client = ZAFClient.init();
    client.invoke('resize', { width: '100%', height: '200px' });
    async function getDevices() {
      const options = {
        type: "GET",
        headers: {
          Authorization: "Bearer {{setting.access_token}}",
        },
        secure: true,
      };
      await client.request(options).then((response) => {
        console.log(response.json());
      });
    }
    getDevices()
  </script>
 
Tipene
Employee
March 29, 2024
Hey Parth,
 
Are you running this locally or is the app uploaded to your Zendesk instance?
Parth14
March 29, 2024

Hi Tipene, uploaded to zendesk apps. I dont think i can run secure credentials locally. 

Tipene
Employee
March 29, 2024
Thanks for the update. I'm going to pull this in to a private ticket so I can grab a few more details. You should see an email coming through from me shortly!
November 18, 2024
hello @Tipene Hughes sir 

const file = new File([blobData], mediaData.fileName, {
type: blobData.type,
});
const formData = new FormData();
formData.append("media", file);
formData.append("title", file.name);
formData.append("content_type", file.type);
formData.append("account", spokiAccount?.id);
const metadata = await client.metadata();

 
const sendMedia = await client.request({
url: `${BASE_URL}/media/`,
type: "POST",
dataType: "json",
data: formData,
headers: {
"Content-Type": "multipart/form-data",
X-secret:
typeof metadata.installationId === "string"
? spokiAccessKey
: "{{setting.spokiAccessKey}}",
},
secure: !(typeof metadata.installationId === "string"),
});


"hello @tipene sir When I pass FormData as the payload in my API call, the media file is not included in the payload when I check the request in the browser's network tab. Why is this happening, and how can I fix it? Also, can you confirm if my code is correct?"
 

 

Greg K
Employee
November 19, 2024

Hi Rocky! It's difficult to say exactly what problems you may be experiencing based on the code that you shared. I initially thought it may be due to the secure settings that you're using, but I don't think that's the case. Are you able to successfully send this to your service or even something like pastebin from a tool like Postman? It will help narrow down whether the issue is with the code or with the apps framework. Please share any other troubleshooting that you've done.

March 6, 2025

Hi - Is there a solution for the Proxy error: UnprocessableEntity, Failed to get installation and oauth information for app.  I have an app that when installed, works initially but then returns this error. If I reinstall the app it works again.  The app is authenticated correctly via Oauth in the App settings.  I have "parameters": [{"name": "token","type": “oauth”}] set in the manifest and the correct OAuth block.  Within my request I am using Authorization:"Bearer {{setting.token}}" as per the docs. I am wondering if it occurs once the authorisation token has expired and isn't being refreshed. I am using Auth0 as the OAuth provider.

Greg K
Employee
March 7, 2025

Hi Andy! My first guess would be an issue with the refresh if it's missing certain values on the initial token response. Take a look at this note and let me know if either of those are missing.

March 10, 2025

From the OAuth Docs and sample request, I get the following response which looks to be as expected { "access_token":"e…w", "refresh_token":"GEb…XbL", "id_token":"eyJ…EoQ", "token_type":"Bearer", "expires_in":86400 }

Greg K
Employee
March 10, 2025
Would you mind sharing the relevant parts of your manifest, while obfuscating any secrets and also the code block where you make the request?