RHi @sonofthetech there seems to be a token mismatch, meaning you might be using a wrong token, but I am not sure, so I will look into this and get back to you, apologies for the delay
Rcan you please paste full curl method you are sending?. You can omit the token but will it would help me to understand better.
Thanks
Thanks
R@sonofthetech - Hi there! Were you able to check this out? 
Rhi @sonofthetech perfect and glad it worked out with PAT, let me know if you need more help else you can close this by marking comment with 
Rhi @sonofthetech let me ask around, I also dont know about this
Rhi @sonofthetech Unfortunately, there’s no direct way to exchange a session for a JWT in Zitadel. Sessions and tokens operate in separate contexts, and Zitadel avoids mixing these mechanisms for security reasons.
For Web, Use the Authorization Code Flow with your custom UI. After authentication, redirect users to Zitadel’s OIDC endpoint to obtain an authorization code. Exchange this code for a JWT (access token) on your backend.
For Mobile, Use the same Authorization Code Flow with PKCE.
For Web, Use the Authorization Code Flow with your custom UI. After authentication, redirect users to Zitadel’s OIDC endpoint to obtain an authorization code. Exchange this code for a JWT (access token) on your backend.
For Mobile, Use the same Authorization Code Flow with PKCE.
Ras for the docs, you can start reading from here https://zitadel.com/docs/apis/openidoauth/endpoints#authorization_endpoint
this should answer all your questions
the idea is start auth -> get token -> use that token for introspection
I hope this helps
this should answer all your questions
the idea is start auth -> get token -> use that token for introspection
I hope this helps