SuperTokens is an open source authentication solution offering features like: Different types of login: Email / password, Passwordless (OTP or Magic link based).

SuperTokens.com

Hi <@498057949541826571> , for social signin, which apis can be used that u provide in https://app.swaggerhub.com/apis-docs/supertokens/FDI/1.18.0

I am using thord party password less, 
actually in mobile we dont have the redirectUrl kind of things

mobile FE they are not using the suprtoken sdk

they just want to utilize the backend apis

yea, it's there in our custom Ui docs. Please have a look at that

```import { ThirdPartyProviderInput } from "supertokens-node/recipe/thirdpartypasswordless/types";

let providers: ThirdPartyProviderInput[] = [
    {
        config: {
            thirdPartyId: "apple",
            clients: [{
                clientType: "web-and-android",
                clientId: "...",
                additionalConfig: {
                    "keyId": "...",
                    "privateKey": "...",
                    "teamId": "...",
                }
            }, {
                clientType: "ios",
                clientId: "...",
                additionalConfig: {
                    "keyId": "...",
                    "privateKey": "...",
                    "teamId": "...",
                }
            }]
        }
    }
]```

this is the backend , now from frontend if in need to call the web one then clientType will be 'web' or 'web-and-android'

also will the clientId , keyID , teamId and private key same for both the clientTypes in case of apple signin

> now from frontend if in need to call the web one then clientType will be 'web' or 'web-and-android'
It will be web-and-android

but in the frontend web when we are configuring we pass the client type as 'web' because in google we have 'web' and 'android' separate. so how can we then pass different client Types from FE based on the social providers

There is no clientType “web” since you have not used that in your config.

```    providers: [
      {
        config: {
          thirdPartyId: THIRD_PARTY.GOOGLE,
          clients: [
            {
              clientId: process.env.GOOGLE_CLIENT_ID,
              clientSecret: process.env.GOOGLE_CLIENT_SECRET,
              clientType: CLIENT_TYPE.WEB,
            },
            {
              clientId: process.env.IOS_GOOGLE_CLIENT_ID,
              clientType: CLIENT_TYPE.IOS,
            },
            {
              clientId: process.env.ANDROID_GOOGLE_CLIENT_ID,
              clientType: CLIENT_TYPE.ANDROID,
            },
          ],
        },
      },```
this is my google config in backend
and 
```SuperTokens.init({
  appInfo: {
    appName: "Testing",
    websiteDomain: baseURL,
    apiDomain: apiBaseURL,
  },
  clientType: "web",```
this is my config at frontend in web. 
now the question is , in apple signin i am using 'web-and-android' and in google separate 'web' , but always i am getting clientType as 'web' . due to this apple is not working as client Type does not match