Skip to main content
venkateshg4665
venkateshg4665
Known Participant
August 6, 2026
Solved

Integration Call in Web Api

  • August 6, 2026
  • 11 replies
  • 87 views

Hello Team, I have created a Web API that triggers a process model. To consume this API, I created an integration object in Appian using the Web API URL. When I test the integration, it returns a 200 (OK) status code, but the process model is not getting triggered. After checking the response, I found that the integration is being redirected to the login page, and because the login page loads successfully, the response status is returned as 200. Could you please suggest the correct approach for implementing the integration on top of the Web API? Do I need to configure authentication differently or use another integration method to avoid the login page redirection?

Best answer by stefanhelzle0001

Well, using “None” is bad. One option is to create a service account, an API key, and us this for authentication.

11 replies

harshas2775
harshas2775
Brainy
August 6, 2026

Currently what authentication you have applied? If its Basic authentication then check that you are not part of a SAML system group or Service Accounts system group. 
If you have setup API key authentication check that service account has proper access granted to access the web api and initiate the process model. Here is the relative documentation for more information.

venkateshg4665
venkateshg4665Author
Known Participant
August 6, 2026

How can I check which authentication method is being used for the Web API? For the Integration, I am using None as the authentication type, and I do not have access to the Admin Console. Is there any other way to verify which authentication is used for WEB Api?

stefanhelzle0001
stefanhelzle0001Answer
Brainy
August 6, 2026

Well, using “None” is bad. One option is to create a service account, an API key, and us this for authentication.

kapils024874
kapils024874
Inspiring
August 6, 2026

Hi ​@venkateshg4665 ,

The behavior suggests an authentication issue rather than a Web API issue. A 200 response with the Appian login page usually means the request wasn't authenticated, so it was redirected. If the Web API is within the same Appian environment, it's generally better to start the process directly using a!startProcess() or the Start Process Smart Service instead of calling your own Web API.

If the Web API must be used, ensure the integration is configured with the appropriate authentication (Basic/OAuth/API Key) and that the integration user has permission to execute the Web API and start the process model.

venkateshg4665
venkateshg4665Author
Known Participant
August 6, 2026

Hi ​@kapils024874  While creating the Web API, I don't see any option to specify the authentication type. How can I check or change the authentication method for the Web API?

J
jessek855119
Participating Frequently
August 6, 2026

You can’t change the authentication method for a specific web API object. Part of Appian’s security guarantee is that developers cannot override this type of security for any one API when the system admins want to enforce authentication for the platform. So you will need to follow the documentation for API authentication.

Web API object security is tied to the security groups of the Web API object.

  • Service accounts and user groups are put into those groups, as appropriate.
  • Service accounts may be assigned web api keys or OAuth credentials.
  • Appian Users who call the web api object endpoint from within another Appian object (e.g. a UI) will use the security of the integration object, thus the integration object’s authentication method needs to be setup correctly.
  • Appian Users who call the web api URL endpoint directly in a browser may use session-based authentication.
J
jessek855119
Participating Frequently
August 6, 2026

This used to be possible with Authentication: None and some additional request headers that direct Appian to use session based authentication. It was a bit fragile though, and IMO isn’t worth investigating now.

The simplest way to do this is to get a web api key from your system admin, tied to a service account that is specific to your app and the use case of ‘loopback’.

L
lalithyak964917
Known Participant
August 7, 2026

Since no valid authentication is provided (none), Appian redirects the request to the login page.The login page itself loads successfully, so the Integration object receives HTTP 200 OK.However, the Web API logic is never executed, so the process model is not triggered. 
so use the API and create the service account and check 

    Terms & ConditionsAccessibility statement