Right now I'm doing a second call to the endpoint in the thirdPartySignInUpPOST section but really hate it. I'm looking to do the same thing with Apple "name" scope where I don't think I can go back to Apple as they only send it once (supposedly)

So you send the auth code to the third-party (Google) a second time (using their APIs) and get the info that way?

Sends the access token to third party to get info

@davido_k I came up with an approach that doesn't require a second load. Let me know if you're interested in hearing about it. I use

id_token

in my backend, so I'm not sure if it applies to you, but maybe it's worth a shot?

Thanks, @dbottisti . I'm actually doing the id_token for google sign-in via js already but that's only one of my current paths.