Error processing integration responseThe response body could not be converted to an Appian valueThe jsonText parameter was not valid JSON. Received: [...

Question

First Scenario:
I have created a "GET" web API in Appian Community Edition and called it through a integration from another Appian environment, but I receive body in the "HTML" format instead of Json and receiving below error.
Second Scenario:Whereas, When I create it other way around like creating web API in other Appian environment and calling it from Appian community Edition returns a proper Json value in the response body. Why I am receiving "HTML" value in response body in First Scenario, it is like Appian community Edition doesn't support web APIs?

shubhama926776 · Accepted Answer

Integration is not properly authenticated when calling the Appian Community Edition web API. Instead of returning the JSON data, Appian sends an HTML login or error page. The main causes are usually missing or incorrect authentication (such as lacking API keys or user credentials) or insufficient permissions for the account making the request. To receive a proper JSON response, ensure you use the correct authentication method and that the user or service account has the necessary access to the API.

Or

Community Edition doesn't support external web API calls properly. Community Edition has "DevOps, Infrastructure, and Import/Export features disabled", causing APIs to return HTML instead of JSON when called externally.
Community Edition can consume external APIs but cannot serve them to external systems. You need a paid Appian environment for full web API functionality.

jessek855119 · Answer

There might be a few reasons for this. For the rest of this reply, I'm assuming that Community Edition (CE) sites allow external calls into Web API's (i.e. no cross origin blocking or allow/deny lists).

Could you show a bit more of the "body" that's being returned? It's hard to tell (since the body isn't shown), but when I've received a similar response from similar situations for non-CE sites, the Appian environment had returned a login page rather than the expected response. This was due to various authentication configurations, both from the target Appian environment and the client that didn't have headers set correctly.

Could you describe more about your authentication setup?

Sign up

Login with SSO

Login to the community

Login with SSO