Dissociate social account (multiple accounts)

This is one of the standard social account dissociation use cases delivered by the Dissociate Social Account from User Process. In this flow, the authenticated user has two or more associated social accounts.

Initial Request

Your client calls the Process Start API to initialize the Process:

**POST https://\{your.url\}/process/start/socialFederation.DissociateSocialMedia.v1.0**
<no body>

Response

Storefront Gateway looks up the current User entity, and determines the following:

The Use has at least one two associated social accounts

Therefore, the Process returns a list of associated accounts and requests for the user (or client) to specify one:

**RESPONSE - body**
{
   "processId": "b6e2a47f-564c-4577-8da2-0aa54c2cf224",
   "processName": "socialFederation.DissociateSocialMedia.v1.0",
   "displayMessage": "Please input required information",
   "parameters": {
      "socialConnection": "String"
   },
   "stepName": "SocialConnectionPrompt",
   "lastStep": false,
   "output": {
      "socialConnections": [
         "facebook:<redacted>",
         "google:<redacted>"
     ]
   }
}

`processId`	Unique identifier for the current instance of this Process.
`processName`	Full name of the Process, including the category and version number.
`stepName`	Name of the specific step that the Process is currently on.
`lastStep`	Boolean that indicates whether or not this was the last step in the Process.
`displayMessage`	Optional message that the UI can display to the user.
`parameters`	Object that specifies the info this Process requires to continue its task.
`socialConnection`	The social connection to dissociate from the User ID.
`output`	Object that contains data that the client can consume, retain, and use for additional operations.
`socialConnections`	List of associated social accounts that the user may freely dissociate from their Storefront Gateway profile. Associations are identified in the format of the name of the social provider and the unique identifier of the associated account within the social provider, separated by a colon (’:’).
Note: Social associations (or “social connections”) contain unique identifiers (typically given by the social providers themselves) to indicate which profile is associated, in cases where more than one profile from the same social provider are associated (e.g., a user has two separate Facebook accounts associated to their Storefront Gateway User ID). In this document, social ID values have been redacted.

Final Request

The client passes the user’s specified provider to the Process with the Process Step API:

**PUT https://\{your.url\}/process/step**
{
   "processId": "b6e2a47f-564c-4577-8da2-0aa54c2cf224",
   "parameters": {
      "socialConnection": "google:<redacted>"
   }
}

`processId`	Unique identifier for the current instance of this Process.
`parameters`	Data object that contains the data request in the previous Process response.
`socialConnection`	The social account to dissociate, as selected by the user. The association is defined in the format of the social provider and the unique identifier of the association associated account within the social provider, separated by a colon.

Process Complete

Storefront Gateway removes the association from the User entity, and returns a HTTP 200 status:

**RESPONSE - body**
{
   "processId": "b6e2a47f-564c-4577-8da2-0aa54c2cf224",
   "processName": "socialFederation.DissociateSocialMedia.v1.0",
   "lastStep": true
}

`processId`	Unique identifier for the current instance of this Process.
`processName`	Full name of the Process, including the category and version number.
`lastStep`	Boolean that indicates whether or not this was the last step in the Process.
The specified social account is no longer associated to the User.

Parent topic:Dissociate Social Account from User Process

Home

Introduction

For Merchants

For Resellers

Partner Ecosystem Management

Commerce Engine

Storefront Experience

APIs

Initial Request

Response

Final Request

Process Complete

​Initial Request

​Response

​Final Request

​Process Complete

Initial Request

Response

Final Request

Process Complete