Read accounts

Before data can be read, we should already have a user access token for this user.

If not, you'll need to authorize them first.

Reading accounts

Using the session received above, we can trigger readAccounts to read all user accounts.

// ... initialize the SDK
// contractDetails - The same one used in getAuthorizeUrl().
// userAccessToken - The user access token from the authorization step.

const data = await sdk.readAccounts({
    contractDetails,
    userAccessToken,
});

Received response should be something like:

{
  "accounts": [
    {
      "createdDate": 1693931692826,
      "id": "40_XXXX",
      "providerFavIcon": "providerFavIconUrl",
      "providerLogo": "logoUrl",
      "reference": "xxxxxxxxxxx",
      "serviceGroupId": 1,
      "serviceGroupName": "Social",
      "serviceTypeId": 40,
      "serviceTypeName": "Instagram",
      "serviceTypeReference": "instagram",
      "sourceId": 420,
      "type": "USER",
      "updatedDate": 1693931704516
    },
    {
      "createdDate": 1693931692826,
      "id": "40_XXXX",
      "providerFavIcon": "providerFavIconUrl",
      "providerLogo": "logoUrl",
      "reference": "xxxxxxxxxxx",
      "serviceGroupId": 1,
      "serviceGroupName": "Social",
      "serviceTypeId": 1,
      "serviceTypeName": "Facebook",
      "serviceTypeReference": "facebook",
      "sourceId": 1,
      "type": "USER",
      "updatedDate": 1693931704516
    }
],
}