Options for HighQ API Authentication Without User Interaction

I am building a scheduler that needs to pull data from HighQ APIs on a recurring schedule. I understand that the APIs are secured with OAuth 2.0.

My goal is to authenticate the scheduler without requiring user sign‑in or manual token rotation. Ideally, I would like to use the Client Credentials flow (app‑only authentication), but I haven’t found documentation confirming whether HighQ supports this.

  • Does HighQ provide an authentication option that avoids user interaction (e.g., client credentials)?

  • If not, what alternatives exist besides maintaining and rotating refresh tokens?

  • Are there recommended best practices for long‑running background processes that need to call the APIs securely?

Any guidance, documentation links, or examples would be greatly appreciated.

  • 0
    Thomson Reuters Thomson Reuters staff member

    Hi,

    We will look into it.

    Thank you.