Skip to main content
Solved

TimeXtender REST API override header


oscarcleve
Contributor
Forum|alt.badge.img+1

We have trouble with an endpoint in a TimeXtender REST API data source using the Override Headers functionality. The problem arose when we upgraded our TX software to the latest version of TDI/TIS and TX REST from 6848.1/6848.1 and 7.1.0.0.

We get this error message:
 

“Failed to execute request for endpoint 'NBABIItemWS'.
HTTP Status Code 401 Unauthorized
Response body:
<error xmlns="http://docs.oasis-open.org/odata/ns/metadata"><code>Unauthorized</code><message>The credentials provided are incorrect</message></error>”

 

We use the Override Headers functionality to limit page size for the particular endpoint. It seems that for some reason the authentication token is overwritten when using this feature, and there fore we can not authenticate. We have plenty of other endpoints in the same data source not using Override Headers, and those are working fine, so we suspect that the issue has to do with that setting.
 

We use this combination of versions:
 

 

Is there a way we can alter the call for the endpoint to make the authentication work? We don’t want to limit the page size for all endpoints in the data source.

Best answer by oscarcleve

We tried a few different things but ended up solving the issue by doing the call for this particular endpoint in a separate REST data connection. Thanks!

View original
Did this topic help you find an answer to your question?

4 replies

anders.e.jonsson
Contributor
Forum|alt.badge.img+1

Hi ​@oscarcleve 

I experienced the same. Tried both Headers and Connection variables. And setting in in the Endpoint works fine for us also.

BR
Anders


Thomas Lind
Community Manager
Forum|alt.badge.img+5
  • Community Manager
  • 1020 replies
  • March 13, 2025

Hi ​@oscarcleve 

It will not mix the two, so if you set a header in Authentication and then override the headers on the endpoint it will not use that set in the Authentication.

So you will need to do it in another way. Like what ​@anders.e.jonsson suggests.


Christian Hauggaard
Community Manager
Forum|alt.badge.img+5

@oscarcleve does the above answer your question? Please let us know if you have any follow up questions


oscarcleve
Contributor
Forum|alt.badge.img+1
  • Author
  • Contributor
  • 14 replies
  • Answer
  • March 19, 2025

We tried a few different things but ended up solving the issue by doing the call for this particular endpoint in a separate REST data connection. Thanks!


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings