Relysia
Relysia WalletAPI DocumentationGithub RepositoryDemo
  • Relysia SDK
  • Getting Started
    • Setup
    • API
    • Infrastructure
  • Wallets
    • Wallets
    • Mnemonic
    • Addresses
    • Metrics
    • Balance
    • History
  • Payments
    • Lookup
    • Sweep
    • URI
    • Transactions
    • Raw Transactions
    • Invoices
      • Create Invoice
      • Get Invoice
      • Pay Invoice
    • Payments
    • Asm
  • token
    • Basics
    • Token Issuance
    • NFT Issuance
    • Atomic Swaps
    • Details
    • Leaderboard
  • Utility
    • Post
    • Upload
    • Conversion
    • Paymail
    • Transpile-Compile
  • Enterprise Wallet
    • Overview
    • Authentication
    • Management
    • Wallet
    • Smart Contracts
    • Transaction
    • Fee Manager
    • Events
  • Realtime Transaction Notification
    • Use Case
    • Setup and Configuration
    • Events and Messages
  • More
    • Metashard
    • Satolearn
Powered by GitBook
On this page
  1. Enterprise Wallet

Authentication

Obtaining an authorization token

Authentication allows all types of users to obtain an Auth id_token, which can then be utilized as an Authorization Bearer token for users with defined roles, including administrators.

This authToken serves as proof of a user's authentication and can be used to authorize access to protected resources

Login

Login API allows users to securely authenticate and retrieve their Auth Token and User Role.

The endpoint accepts HTTP POST requests and expects the following headers:

  • serviceId (required): The unique identifier for each project.

and JSON payload with the following parameters:

  • email (required): The email of the user.

  • password (required): The password of the user.

curl --location --request POST 'https://api.enterprise.relysia.com/api/v1/login' \
--header 'serviceid: serviceid' \
--header 'Content-Type: application/json' \
--data-raw '{
    "email":"test@change.com",
    "password":"password"
}

Upon successful authentication, the Login API returns a JSON response with the following parameters:

  • token : The Auth Token used for authorization.

  • role : The role of the authenticated user.

PreviousOverviewNextManagement

Last updated 2 years ago