Hi, I am running a supertokens implementation with...
# support-questions-legacy
l
Hi, I am running a supertokens implementation with social login and react native clientside and nest.js in the backend connected to the local supertokens instance via the SDK. We've got a user-profiles table to compliment the supertokens login for our app (mainly for their profile information) and atm i automatically create one when a user logs in by overriding the ThirdParty.init signInUp function, so i just grab the user_id and email and create a userprofile with that data as well, which works fine, but it hit me that a social login to apple or google (the two we currently support) should be able to supply a lot more info then just an email, for example a profile pic, a name, maybe a phone number as well. I took a look at the return type of the signInUp method and it seems it doesn't really return anything relevant for me except the email. Is there anyway to override this and get more data out of the social login for me to create a more complete userprofile with? Thanks in advance for the help! 🙂
r
using the access token, you can query the provider and get any info you like
l
Thank you so much! 😄
p
hey @rp_st , can you provide a little more insight on how this is supposed to be used? I see the #TODO comment in the example code, is this intended to be added to the return response so the frontend could use it?
r
@pageler the todo there is supposed to be replaced by querying the provider with the access token and then saving that info somewhere. You can save that info in your own db, or in our user metadata recipe.