KyberDeveloper · Powering Liquidity for the Ecosystem

KyberDeveloper · Powering Liquidity for the Ecosystem

  • Home
  • Integrations
  • Reserves
  • KyberPRO
  • Addresses
  • API/ABI
  • Trade Debugger
  • Tracker
  • GitHub

›Widgets

Getting Started

  • Introduction

RESTful API

  • RESTful API Overview
  • RESTful API

Widgets

  • Widgets Overview
  • KyberWidget
  • Sign In Widget

Core Smart Contracts

  • IKyberNetworkProxy
  • KyberNetworkProxy
  • IKyberNetwork
  • ISimpleKyberProxy
  • IKyberMatchingEngine
  • KyberMatchingEngine
  • IKyberHint
  • KyberHintHandler
  • IKyberFeeHandler
  • KyberFeeHandler
  • IKyberStaking
  • KyberStaking
  • IKyberDao
  • KyberDao
  • IKyberStorage
  • KyberStorage
  • IKyberHistory
  • KyberHistory
  • IKyberReserve
  • KyberReserve
  • ConversionRates
  • LiquidityConversionRates
  • IEpochUtils
  • EpochUtils

Contract ABIs

  • ABIs

Plugins

  • Plugins Overview
  • WooCommerce Plugin

Code Snippets

  • Token Quantity Conversion

Misc Contracts

  • KyberNetwork
  • ConversionRatesInterface
  • OrderbookReserveInterface
  • PermissionGroups
  • SanityRates
  • SanityRatesInterface
  • Withdrawable

Sign In Widget

Developer Registration

Contact one of our Kyber developers in the KyberDeveloper group at https://t.me/KyberDeveloper to get a developer account. The following information is required:

ParameterDescription
NameApplication name that will be displayed to the user when asked for login permissions
Redirect URIThe URI that Kyber's servers will redirect the users to and that will handle the data that Kyber passes; you can possibly provide multiple URIs, but they must be HTTPS (You can use ngrok or localtunel to create https uris for testing)
IconAn icon in SVG format with 1024x1024 resolution

You will then be provided with 2 items:

  1. APP_ID, which is considered public and will be used in your public-facing code.
  2. APP_SECRET to be kept secret and used only on the server side.

/authorized-users

Path Parameters

ParameterRequiredDescription
uidNoUser ID
kyc_statusNoEither pending, approved or none. a user has not yet submitted KYC, or his/her KYC was rejected, none is returned.

Examples

Using uid

https://kyberswap.com/api/authorized_users&access_token=ACCESS_TOKEN&uid=42

Using kyc_status

https://kyberswap.com/api/authorized_users&access_token=ACCESS_TOKEN&kyc_status=pending https://kyberswap.com/api/authorized_users&access_token=ACCESS_TOKEN&kyc_status=none

About auth 2.0

Refer to https://aaronparecki.com/oauth-2-simplified/ for more information.

← KyberWidgetIKyberNetworkProxy →
  • Developer Registration
  • /authorized-users
    • Path Parameters
    • Examples
  • About auth 2.0
KyberDeveloper · Powering Liquidity for the Ecosystem
EssentialsGetting StartedDesign PrinciplesProtocol OverviewSmart Contract Architecture
IntegrationsDAppsVendorsWalletsPlatform Fees
ReservesFed PriceAutomated Price
© 2019 Kyber Network. All rights reserved.
Follow us on Facebook
Follow us on Twitter
Follow us on Github
Follow us on Reddit
Join our Telegram group
Subscribe to our Youtube channel
Read our blog on Medium