Because there’s too many difference on how JWT is used in API.
In some case, you will not use the Bubble native JWT process.
Two example: Zoom have JWT token. You don’t need to use that in JWT auth in Bubble because the JWT token is provided as a bearer api key. So you call endpoint directly with the JWT.
In Google, the JWT provided need to be used in Bubble JWT Auth. It will look like this:
The best thing you can do is to share the API doc url and maybe someone can jump it.
I didn’t get time to check for the Jitsi one and this one is special because the token is use in an iFrame and seem to be created on the fly.