KIIEX – powered by KiiChain
  • Learn
    • What is KIIEX?
    • What is KiiChain?
    • KiiChain
      • Vision of KiiChain
      • Use Cases
      • Roadmap
      • Whitepaper
    • Tokenomics
      • Intro Coin Details
      • Coin Unlocking Schedule
      • Utility
      • Evergreen Model
    • Getting Started
      • Get a Wallet
      • Set Up a Web Wallet
      • Connect Wallet to Explorer App
  • Kii Ambassadors
  • CONNECT TO KIIEX
    • Set up your KIIEX Account
      • Upgrade your Account to Enterprise Level
    • Authenticate with API Key
    • Stablecoin FX Quick Start
      • Swap USDT to COPM with UI
    • KIIEX API's
      • System
      • User
      • Authentication
      • Models
  • BUILD ON KIICHAIN
    • Developer Hub
    • Testnet Oro
    • Endpoints - Cosmos
      • EVM
        • VM
        • ERC20
        • FeeMarket
      • IBC
      • Kiichain
        • TokenFactory
      • Cosmwasm
      • Cosmos
        • Auth
        • Authz
        • Bank
        • Tendermint
        • Consensus
        • Distribution
        • Evidence
        • Feegrant
        • Gov
        • Slashing
        • Staking
        • Tx
        • Upgrade
    • Developer Tools
      • RWA Protocol
      • Rust SDK
      • JS/TS SDK
        • Kiijs-evm
        • Kiijs-proto
        • Kiijs-utils
      • Deploy a smart contract
      • Deploy a dApp
      • Testnet faucet
    • Smart Contracts
    • Modules
      • TokenFactory
      • EVM
  • Precompiled contracts
  • Validate the Network
    • Getting Started
      • What is a delegator?
      • What is a validator?
    • Run a Validator / Full Node
      • Getting started
      • Step-by-Step Guide
        • Becoming a Validator
        • Recovering Legacy Addresses
      • Maintaining a validator
      • Incentive
      • Technical requirements
      • Validator Security
    • Economics
      • Staking Requirements
      • Delegation / Staking
      • Rewards
      • Block Rewards Formula
      • APR
    • Delegator Information
      • Choosing a validator
      • Directives of delegators
      • Incentive to stake
      • Security considerations
      • Risks to consider
Powered by GitBook
LogoLogo
On this page

Was this helpful?

Export as PDF
  1. CONNECT TO KIIEX

Authenticate with API Key

This page explains how to securely connect to our API using an API Key. It outlines the required authentication details and how to generate a digital signature to ensure safe and verified communicatio

PreviousUpgrade your Account to Enterprise LevelNextStablecoin FX Quick Start

Last updated 1 day ago

Was this helpful?

Step by step

  1. Create your user API Key and add permissions

    1. Create API KEY

  2. Create a Signature

    1. Create a Signature

  3. Authenticate via API

    1. Authenticate via API

Create API KEY

Navigate through the admin UI to your user profile.

Click on the API KEYS option.

Click on 'Create your API KEY'. You will see the following:

Depending on how you plan to use your API KEY, please choose from the available options. If you want to restrict usage by IP address, you can add the allowed IP in the designated field. Remember, you can always modify this later.

When you click on 'Create API Key', you will see your API KEY, API SECRET, and NONCE displayed on screen only once. You can download them using the 'Export to JSON' button. It's very important to store them in a safe place, as you will need them later.

To save, click the button confirming that you've securely stored your credentials, then close the modal. Your new API KEY will now appear in the list, and you can edit or delete it as needed.

Create a Signature

To generate a signature, you will need the API Secret, Nonce, User ID, and API Key, which are all generated, You can generate a signature by using a tool such as https://codebeautify.org/hmac-generator The algorithm will be SHA256, the Key will be the API Secret, and the plain text message will be composed of a combination the Nonce, User ID, and API key, in that exact order with no spaces. An example is listed below.

Authenticate via API

Follow the example in the image, add the APIKEY, Signature, UserId, and Nonce to the request headers, and call the AuthenticateUser endpoint. This will successfully authenticate you.

In the response, you will receive a session token. Use it in all subsequent requests by including it in the headers as the value of aptoken.

  • Step by step
  • Create API KEY
  • Create a Signature
  • Authenticate via API
  • POSTAuthenticate user session

Authenticate user session

post
Body
one ofOptional
Responses
200
Authentication result
application/json
post
POST /ap/AuthenticateUser HTTP/1.1
Host: apstage.proxy.kiiex.io
Content-Type: application/json
Accept: */*
Content-Length: 85

{
  "APIKey": "text",
  "Signature": "text",
  "UserId": "text",
  "UserName": "text",
  "Nonce": "text"
}
200

Authentication result

{
  "authenticated": true,
  "user": {
    "userId": 1,
    "userName": "text",
    "email": "text",
    "emailVerified": true,
    "accountId": 1,
    "omsId": 1,
    "use2FA": true
  }
}