topic Re: REST token refreshed. 'Test Connection' succeeds. Save fails due to parsing error in Integration, Extension & APIs

REST token refreshed. 'Test Connection' succeeds. Save fails due to parsing error

GarythDen — Thu, 21 Aug 2025 08:19:48 GMT

We have been using a REST API for over a year to extract data. API requires a periodic refresh of the token.

Refreshed the token in Postman.

Entered token into my Qlik SaaS data connection as we usually do.

Test Connection returns 'Connection Succeeded'

Save returns: connection string validation error: parsing connection string for 'xxxxxx-xxxx-xxxxx-xxxx' failed: dcaas API call 'POST /v1/data-sources/actions/parse-properties' failed with code: 400

DCERROR-0071

And it can not save the token.

Could this be a change that happened on the API side ? OR could it be something changed on the Qlik SaaS side ?

Re: REST token refreshed. 'Test Connection' succeeds. Save fails due to parsing error

alex_colombo — Thu, 21 Aug 2025 09:23:32 GMT

Hey @GarythDen , with token you mean an API key or an OAuth token? 400 error seems to be bad request, and not something about authentication.

What are you doing with this end point? Seems it is not a public API. Could you please share request headers and the body of request if present?

Re: REST token refreshed. 'Test Connection' succeeds. Save fails due to parsing error

GarythDen — Thu, 21 Aug 2025 09:44:16 GMT

Hi @alex_colombo

It is an OAuth2 token, with a Bearer header prefix. Not a public API, an API to extract our company data from cloud. (Oracle BI API).

In the Create Connection dialog I have correct URL and body and header as far as I can see, corresponding to the Postman side. It worked fine before with all these settings and the Postman setup can complete request.

Usually I update the Query Header to read:

Authorization Bearer <token>

Now it wont accept the new token upon saving (Parsing error above), but will accept if tested.

This is pointing towards an actual issue with the REST connector on the Qlik side...

Re: REST token refreshed. 'Test Connection' succeeds. Save fails due to parsing error

GarythDen — Thu, 21 Aug 2025 09:47:35 GMT

I have just resolved the issue.

It will not save the new token unless you have clicked the 'Encrypted' check box next to the Query Header fields in the REST connector dialog.

This is not obvious at all. Qlik please look into this