How to set up Epic Account Services (EAS) with your product.
Epic Account Services (EAS) provides game developers with access to a cross-platform Epic Account ecosystem and its associated social features, enabling Epic users to access their friends across a wide variety of supported platforms regardless of the storefronts or engines a game uses. EAS exposes API operations to authenticate Epic users and access their friends and presence. EAS also serves as a prerequisite for certain Epic Games Store online features, such as in-app purchase flow.
Epic Account Services is available in a Preview mode, and is a subject to certain temporary limitations. In particular, the service is not yet available to users who would require parental consent to use it when accessed from outside of Epic Games Store. Additionally, audience restrictions apply for unverified applications.
Epic Account Services is a stand-alone offering of Epic Online Services (EOS). It introduces a separate family of Epic Account-specific services in addition to the standard identity provider-agnostic set of EOS services, built upon EOS Organization User ID and Product User ID. Such services do not require the use of Epic Account Services, but developers can always choose to enable EAS as one of the supported EOS identity providers. Check the EOS Connect interface for more details.
Acceptable use of Epic Account Services is defined in the Service Addendum for Epic Account Services. For information about how to set up your application for Epic Account Services, refer to Getting Started with Epic Account Services.
Epic Account vs. EOS Organization/Product User IDs
There are several important commonalities and differences between the Epic Account system and the EOS Organization/Product User ID system.
Both (a) Epic Account and (b) EOS Organization / Product User ID systems are fully cross-platform, and both support a wide variety of external authentication methods. However, in contrast to an ecosystem-wide Epic Account, an EOS Organization User ID is always specific to a developer's organization. Product User ID is always specific to a product.
As a result, the same external identity, such as a console account, is always linked at most to one (a) Epic Account at a time, but can be linked to multiple (b) EOS Organization User IDs simultaneously, though no more than once per Organization. Likewise the same EOS Organization User ID can point at most to one EOS Product User ID per each product. Check our Glossary of Terms for more information.
OpenID Specification Compatibility
EAS authentication and authorization flow is compatible with OpenID Connect Core 1.0 and Discovery 1.0 specifications with minor extensions. EAS OpenID Provider Configuration is available at https://api.epicgames.dev/epic/oauth/v1/.well-known/openid-configuration.
Information about the user experience of the consent flow and how users can manage permissions
Information about Epic Account data privacy and visibility
Design guidelines for integrating with Epic Account Services for authentication