TRKD API supports 2 types of token

-- standard service token using username and application.

-- effective user token, or impersonation token sometimes called, whereby from a service token you create additional token using an effective user identity, typically to identify individual end user of trkd api clients' website - for example in quote list and portfolio services you could use this to manage unique quote lists for each your users.

-- "unmanaged effective users" are where the effective user string is completely under control of trkdapi client and is opaque string to trkdapi itself, where we have no knowledge of it, validation, control or creation -- its all under client control i..e completely unmanaged by trkd side, hence that description.

Some service do not support the concept of effective users and simply and only need the original service token - as per the error message the is the case for news service:

Unmanaged effective users are not supported by this service

Simply change to use service token (which you must have created in first place already)

If you thought you were using service token anyway and not using effective user token, and the above explanation doesn't make sense to you, please post actual xml request and response as text not as screen image. At very least, post value of the ErrorReference element in the fault response (again: as text, not as image)

@895669342

I have checked an error "Unmanaged effective users are not supported by this service ..."

message. It seems you do not have a permission to subscribe this news headline service. Please contact your Refinitiv representative to verify your TRKD user/permission.

Hello @895669342

I can replicate the issue with my Unmanaged effective users credential (CreateImpersonationToken_2). I got the same "Unmanaged effective users are not supported by this service. Retry your request with either a Reuters type effective user or a service user only." error message as you.

I can get data with my Service Token (CreateServiceToken_Request_1) credential . Could you please re-test with a service token user/operation?

hello @robin @Wasin Waeosri

thank you! The cause of this problem,The http request parameter configuration is miscalled into the https mode request. Because the http request cannot use the "Effective Username" parameter.