Options
All
  • Public
  • Public/Protected
  • All
Menu

Hierarchy

Implements

Index

Constructors

constructor

Properties

Readonly config

The resolved configuration of IdentityServiceClient class. This is resolved and normalized from the constructor configuration interface.

middlewareStack

middlewareStack: MiddlewareStack<ServiceInputTypes, ServiceOutputTypes>

Methods

cancelGameLink

completeGameLink

completeIdentityAvatarUpload

destroy

  • destroy(): void
  • Destroy underlying resources, like sockets. It's usually not necessary to do this. However in Node.js, it's best to explicitly shut down the client's agent when it is no longer needed. Otherwise, sockets might stay open for quite a long time before the server terminates them.

    Returns void

followIdentity

getGameLink

  • Returns the current status of a linking process.

    Once status is complete, the identity's profile should be fetched again since they may have switched accounts.

    Parameters

    Returns Promise<GetGameLinkCommandOutput>

  • Returns the current status of a linking process. Once status is complete, the identity's profile should be fetched again since they may have switched accounts.

    Parameters

    Returns void

  • Returns the current status of a linking process. Once status is complete, the identity's profile should be fetched again since they may have switched accounts.

    Parameters

    Returns void

getIdentityHandles

getIdentityProfile

getIdentitySelfProfile

getIdentitySummaries

listActivities

listFollowers

listFollowing

listFriends

listMutualFriends

prepareGameLink

  • Begins the process for linking an identity with the Rivet Hub.

    Importance of Linking Identities

    When an identity is created via rivet.api.identity#SetupIdentity, the identity is temporary and is not shared with other games the user plays.

    In order to make the identity permanent and synchronize the identity with other games, the identity must be linked with the hub.

    Linking Process

    The linking process works by opening identity_link_url in a browser then polling rivet.api.identity#GetGameLink to wait for it to complete.

    This is designed to be as flexible as possible so identity_link_url can be opened on any device. For example, when playing a console game, the user can scan a QR code for identity_link_url to authenticate on their phone.

    Parameters

    Returns Promise<PrepareGameLinkCommandOutput>

  • Begins the process for linking an identity with the Rivet Hub.

    Importance of Linking Identities

    When an identity is created via rivet.api.identity#SetupIdentity, the identity is temporary and is not shared with other games the user plays. In order to make the identity permanent and synchronize the identity with other games, the identity must be linked with the hub.

    Linking Process

    The linking process works by opening identity_link_url in a browser then polling rivet.api.identity#GetGameLink to wait for it to complete. This is designed to be as flexible as possible so identity_link_url can be opened on any device. For example, when playing a console game, the user can scan a QR code for identity_link_url to authenticate on their phone.

    Parameters

    Returns void

  • Begins the process for linking an identity with the Rivet Hub.

    Importance of Linking Identities

    When an identity is created via rivet.api.identity#SetupIdentity, the identity is temporary and is not shared with other games the user plays. In order to make the identity permanent and synchronize the identity with other games, the identity must be linked with the hub.

    Linking Process

    The linking process works by opening identity_link_url in a browser then polling rivet.api.identity#GetGameLink to wait for it to complete. This is designed to be as flexible as possible so identity_link_url can be opened on any device. For example, when playing a console game, the user can scan a QR code for identity_link_url to authenticate on their phone.

    Parameters

    Returns void

prepareIdentityAvatarUpload

removeIdentityGameActivity

reportIdentity

searchIdentities

send

setIdentityGameActivity

setupIdentity

  • Gets or creates an identity.

    Passing an existing identity token in the body refreshes the token.

    Temporary Accounts

    Until the identity is linked with the Rivet Hub (see rivet.api.identity#PrepareGameLink), this identity will be temporary but still behave like all other identities.

    This is intended to allow users to play the game without signing up while still having the benefits of having an account. When they are ready to save their account, they should be instructed to link their account (see rivet.api.identity#PrepareGameLink).

    Storing Token

    identity_token should be stored in some form of persistent storage. The token should be read from storage and passed to rivet.api.identity#SetupIdentity every time the client starts.

    Parameters

    Returns Promise<SetupIdentityCommandOutput>

  • Gets or creates an identity. Passing an existing identity token in the body refreshes the token.

    Temporary Accounts

    Until the identity is linked with the Rivet Hub (see rivet.api.identity#PrepareGameLink), this identity will be temporary but still behave like all other identities. This is intended to allow users to play the game without signing up while still having the benefits of having an account. When they are ready to save their account, they should be instructed to link their account (see rivet.api.identity#PrepareGameLink).

    Storing Token

    identity_token should be stored in some form of persistent storage. The token should be read from storage and passed to rivet.api.identity#SetupIdentity every time the client starts.

    Parameters

    Returns void

  • Gets or creates an identity. Passing an existing identity token in the body refreshes the token.

    Temporary Accounts

    Until the identity is linked with the Rivet Hub (see rivet.api.identity#PrepareGameLink), this identity will be temporary but still behave like all other identities. This is intended to allow users to play the game without signing up while still having the benefits of having an account. When they are ready to save their account, they should be instructed to link their account (see rivet.api.identity#PrepareGameLink).

    Storing Token

    identity_token should be stored in some form of persistent storage. The token should be read from storage and passed to rivet.api.identity#SetupIdentity every time the client starts.

    Parameters

    Returns void

signupForBeta

unfollowIdentity

updateIdentityProfile

updateIdentityStatus

validateIdentityProfile

watchEvents