Hi Greg,

Thank you for the information. The GraphQL API seems the answer of everything by this time….

But I'd like to explain why I'm not entirely convinced by this approach.

In my original use case, I don't need to communicate through a new server-side app, or "client" as it's referred to in the documentation. The first step in the GraphQL setup, according to the documentation, is to "Register a client," which involves manually creating a new "client" (Quick-access menu > Development > API > Clients. Click the Add client). This means I have to create a new application, register it with Totara, and then build the logic to authenticate users and so on.

My main concern is that, unlike with a traditional web service, where I can simply create an endpoint on Totara and start using it directly, the GraphQL approach requires an additional step of setting up a "client." This essentially means having an extra application to serve as an intermediary or bridge to the API, which adds unnecessary complexity in my case.

In short, its requirement for a registered client makes it less straightforward for my specific needs, where a simple web service endpoint would suffice without the need for an extra application layer.