Unable to validate connnection on Tableau Cloud Integration<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Table of Contents IssueCause How validation builds the URL (OOB)Common misconceptions (and clarifications) The failure is caused by credentialsDoes the spoke auto‑inserts /api/?The Tableau REST version in the token is wrong. ResolutionRelated Links Issue When configuring the Tableau Cloud integration for SaaS License Management, the Validate connection step fails with:Connection validation is not successful. Please check connections and credentials and try again Cause One possible cause is that /api/ is not included in the Connection URL. How validation builds the URL (OOB) The Validate connection action in the Tableau Cloud spoke derives the REST signin endpoint from the Connection URL you provide. In the observed behavior, the action appends /<version>/auth/signin to the Connection URL verbatim. If the Connection URL does not already contain /api/, the final path becomes /<version>/auth/signin (missing /api) and Tableau Cloud returns 404. Including /api/ in the Connection URL yields the correct REST path /api/<version>/auth/signin, and validation completes successfully. Note: Tableau's REST API requires the /api/ segment before the versioned route for authentication (signin). It has been validated that /api/<version>/auth/signin returns a valid response, while the non-/api path returned 404 Common misconceptions (and clarifications) The failure is caused by credentials In this symptom pattern the request never reaches authentication; it fails with 404 Not Found due to the URL path, not invalid credentials. Does the spoke auto‑inserts /api/? The observed logs show the request was sent to /<version>/auth/signin without /api/, resulting in 404. Ensure /api/ is present in the Connection URL you configure. The Tableau REST version in the token is wrong. Even with a version value, the endpoint must include /api/. A missing /api/ produces the same 404 irrespective of the version number embedded in the call. Resolution You will need to add the /api/ to the connection URL , which is also recommended by Tableau (see Related Links ) Open the Connection & Credential record used by the Tableau Cloud integration profile.Set Connection URL to include the /api/ segment at the end for example: https://<server>.online.tableau.com/api/ Keep Content URL set to your Tableau site (contentUrl).Save and select Validate connection again.If validation fails, verify in your Outbound HTTP Logs (or traffic capture) that the request path is /api/<version>/auth/signin. Related Links Docs: Integrating with Tableau Cloud - ServiceNow Documentation Tableau.com: Signing In and Signing Out (Authentication) - Tableau REST API Help Documentation