You are currently reviewing an older revision of this page.
After enabling SAML authentication for Appian, Web API calls return a 200 OK response code with an unexpected response body that fails to parse in the external system calling the Web API. For example, the error observed in the Web API client may indicate that the response was invalid JSON or that a particular attribute could not be found in the response body.
200 OK
After enabling SAML authentication, the Web API is returning the HTML of the login page of the SAML provider instead of the expected data returned by the Web API.
Use the ?signin=native query parameter in the Web API URL when making the call from the external system to enable the call to be authenticated through Basic authentication instead of SAML. For example, if the Web API URL is https://appian.example.com/suite/webapi/get-data, the call should be made to https://appian.example.com/suite/webapi/get-data?signin=native.
?signin=native
https://appian.example.com/suite/webapi/get-data
https://appian.example.com/suite/webapi/get-data?signin=native
This article applies to Appian 17.1 and later using SAML authentication.
Last Reviewed: August 2019