Skip to main content

Account Linking

We provide FACEIT Connect to implement account linking and Single Sign On for registered FACEIT users. Based on the OAuth2 standard, FACEIT Connect enables application developers to build applications that utilize authentication and data from all FACEIT Developer Tools, including our APIs.

FACEIT Connect Documentation​

For further details and implementation notes, please see the latest version of the FACEIT Connect documentation.

Authorization Code Flow with PKCE​

Use this flow if your app uses a server, can securely store a client secret and make server-to-server requests to the FACEIT API. Suitable for applications that access FACEIT on behalf of a user.

FACEIT standard OAuth2 endpoints are available here.

The very first step is to create an OAuth2 Consent Screen and OAuth2 Client for your App. You can do this from the App studio section of the Developer Portal.

These are the basic info associated with an OAuth2 Client and Consent Screen:

  • Icon - an icon representing your application’s logo.
  • Client ID - a public string generated by FACEIT that represents the name of your app. You can give your app a label on FACEIT to make easier to identify, but the Client ID provided by FACEIT will be always in a GUID format.
  • Client Secret - a secret token randomly generated by FACEIT for a specific Client ID. Your Client Secret is a password, so make sure to keep it somewhere safe. Additionally, generating a new client secret on FACEIT will immediately invalidate the current one, which will make your API requests fail until your app is updated.
  • Redirect URL - a URL pointing to a web page on your application or website to which FACEIT will redirect the user after successful authentication. FACEIT will append the Authorization code or OAuth token as a query parameter on this URL.