Users

Exchange legacy client JWT for user credentials

Auth: Client JWT

Legacy compatibility endpoint for older chat component / mobile SDK flows that still exchange a Client JWT into Ethora user session tokens.

Use x-custom-token with payload data={type: 'client', appId: '', userId: ''}.

Preferred approach going forward:

  • authenticate the end user via the normal login/signup flows and pass the resulting user tokens directly, or
  • let the embedding app/backend provide the final Ethora user/session object to the chat component instead of relying on this exchange route.
post/v1/users/client

Request

  • Base URL: https://api.chat.ethora.com
  • URL: https://api.chat.ethora.com/v1/users/client
  • Auth: HTTP bearer

Response 

{
  success: boolean,
  user: {
    defaultWallet: {
      walletAddress: string
    },
    isSuperAdmin: {
      read: boolean,
      write: boolean
    },
    _id: string,
    firstName: string,
    lastName: string,
    email: string,
    username: string,
    tags: string[],
    profileImage: string,
    emails: [
      {
        loginType: string,
        email: string,
        verified: boolean,
        _id: string
      }
    ],
    appId: string,
    xmppPassword: string,
    roles: string[],
    isProfileOpen: boolean,
    isAssetsOpen: boolean,
    isAgreeWithTerms: boolean,
    homeScreen: string,
    registrationChannelType: string,
    createdAt: string,
    updatedAt: string
  },
  token: string,
  refreshToken: string
}

Changes

No recorded changes to this operation across all 1 revision of this API.