Trying to use the platform API but I am not sure where the query params come from?
client_id can be found?client_secrete?Am I right that the username and password are the ones to the Shapediver platform? Can this endpoint be used only with client_id and client_secrete? So not to expose our passwords in code?
Is it correct to think that this is the first step (getting the oauth token) if I want to communicate with the Geometry API?
We will add documentation and examples on how to use the platform API in the coming weeks.
Hi @snabela do you have an estimate when this documentation will be available? Even some bullet points would be so great, just to clarify which end-points need to be called, in which order.
Thx 
Hi @snabela until you guys will be ready with the API documentation, would it be possible to have a simple example for the following workflow calling your back-end APIs?
This would be really helpful in the meantime, so we can figure out other things along the way.
Thank you
@Balazs_Kisfali please note the following:
The Geometry Backend API and TypeScript SDK is released and ready to be used. The documentation is not great yet, but will be improved. We can provide improvements to the documentation on by one depending on your specific questions asked here in the forum.
The Platform Backend API and TypeScript SDK are not released yet to be used by our users. We will release it once a crucial feature required to properly use it (API tokens) will be released, which we plan to happen in May.
It would be interesting to learn about details of the use case you are after.
@snabela thanks for your reply. So, for the Geometry backend we need a token, correct? But to get the token we shall use the Platform backend, right? …so to use the Geometry backend we need to wait until May, if I understand well.
Please check out this section in our documentation: Geometry Backend - Authorization
Thanks @snabela I’ve already visited this part of the docs. Can you please guide on how to obtain the JWT from the Platform Backend?
@Balazs_Kisfali this was precisely my point, as described in the documentation you do not need a JWT, the ticket is sufficient.
Hi @snabela ok, then I misunderstood it somewhere, and also I even tried some weeks ago this: curl -X POST https://sdr7euc1.eu-central-1.shapediver.com/api/v2/ticket/{BACKEND_TICKET}
I used one our backend ticket but it didn’t work and through an authentication error. So this this where my questions started. …but the solution now was actually not only to add the ticket but also the base url. In the example I noticed sdr7euc1... which was very new to me, but my seems requires https://sdeuc1.eu-central-1.shapediver.com. With the later one and a proper backend ticket it works ok now
Thanks for your help 
Hi @Balazs_Kisfali, the EMBEDDING and the BACKEND tabs of the model edit page on the platform show ticket and modelViewUrl (aka the API endpoint, or base url).
The bottom of the help page about the Geometry Backend also provides an overview of these API endpoints. Your account seems to be linked to the shared Rhino 6 system.
Thanks, that was my finding too, which finally worked well
