LogoLogo
  • Introduction to Unizen
    • Unizen Overview
      • Unizen Liquidity Distribution Mechanism (ULDM)
        • ULDM Performance
      • Unizen Interoperability Protocol (UIP)
        • LayerZero
        • DeBridge
        • Stargate
        • Celer
        • Axelar
        • Thorchain
    • Unizen Dashboard
      • General
      • Portfolio
      • History
    • Unizen Trade
      • Fees
    • Unizen Explore
      • Unizen Omni-Chain Data Pool
    • Unizen Earn
  • ZCX
    • Token Utility
    • Tokenomics
  • API - Introduction
    • Introduction
    • Before you get started
      • Understanding Price Impact and Price Slippage in Token Swaps
      • Token Allowance Management for Non-updatable Allowance Tokens
      • Tokens with taxes
      • Wrapping and Unwrapping Native Tokens
      • Quote expiration deadline
    • Security Best Practices for Integrating Unizen
      • Why disable CORS
      • How to integrate with a reverse proxy
    • Version 2 of our smart contracts
      • Migration to smart contract v2
  • API - GET STARTED
    • QuickStart guide
    • Swagger
    • Information endpoints
      • GET /trade/v1/info/chains
      • GET /trade/v1/info/sources
      • GET/v1/info/cross-providers
      • GET /trade/v1/info/token/search
      • GET /v1/info/token/popular
      • GET /trade/v1/info/token/{chainId}/{tokenAddress}
      • GET /trade/v1/info/tokenLogo/{chainId}/{tokenAddress}
      • GET /info/thorchain-inbound-address
      • GET /trade/v1/info/tx/{txHash}
      • GET /trade/v1/info/trade/{chainId}/{txHash}
      • GET /trade/v1/info/trades
    • Approval
      • GET /trade/v1/{chainId}/approval/spender
      • GET /trade/v1/{chainId}/approval/transaction
      • GET /trade/v1/{chainId}/approval/allowance
    • Single-Chain Swap
      • GET /trade/v1/{chainId}/quote/single
      • GET /trade/v1/{chainId}/swap/single
      • Send transaction in evm chains
      • Send transaction in Solana
    • Cross-Chain Swap
      • GET /trade/v1/{chainId}/quote/cross
      • GET /trade/v1/{chainId}/swap/cross
      • Send transaction
    • Gasless orders
      • POST /trade/v1/gasless/typed-data
      • POST /v1/gasless/estimate
      • POST /v1/gasless/create
      • POST /v1/gasless/cancel
      • GET /trade/v1/gasless/status/{orderId}
      • GET /v1/gasless/orderByAddress/{address}
    • UTXO Assets and Cosmos Swap
      • GET /trade/v1/{chainId}/quote/cross 1
      • GET /trade/v1/{chainId}/swap/cross
      • Sending transactions
    • Efficient Quote Retrieval with Batch Processing
      • GET /trade/v1/{chainId}/batch_quote/single
    • Error Messages
  • GASLESS TRADES
    • Obtaining gasless quotes
    • Gas estimation
    • Executing the trade
    • Following the orders
  • On-Chain Contracts - Get Started
    • Integration with Unizen Contracts for Token Swapping
    • Registering Errors on Smart Contract Calls
  • PERMIT2
    • What is Permit2?
    • Usage in our api
  • WIDGET - Get Started
    • Embed the Unizen Widget
    • Playground
  • Other
    • Smart Contracts
    • Security Audits
    • Roadmap
  • links
    • Unizen
    • Marketing Website
    • Medium
    • Twitter
    • Discord
    • Telegram
Powered by GitBook
On this page

Was this helpful?

  1. API - GET STARTED

Information endpoints

The information that you need to perform the best swaps.

PreviousQuickStart guideNextGET /trade/v1/info/chains

Last updated 1 year ago

Was this helpful?

Here's an example project built with Next.js. Its purpose is to demonstrate how to integrate the Unizen API for single-chain and cross-chain trade:

A list of endpoints that returns information needed for other endpoints to perform a trade:

  1. /trade/v1/info/chains: This endpoint provides a list of chains available within the API.

  2. /trade/v1/info/sources: This endpoint returns a list of exchanges available for each chain.

  3. /trade/v1/info/cross-providers: It returns information of the different cross-providers enabled on our system.

  4. /trade/v1/info/token/search: This endpoint allows users to perform search of tokens within the API. It typically accepts search parameters and returns results a list of tokens that match the specified criteria.

  5. /trade/v1/info/token/popular: This endpoint returns a list of popular tokens. A chain id can be sent as optional param.

  6. /trade/v1/info/token/{chainId}/{tokenAddress}: This endpoint returns the information of a concrete token given its contract address and chain id where it is deployed.

  7. /trade/v1/info/tokenLogo/{chainId}/{tokenAddress}: This endpoint returns the token logo of a given token. It's an image.

  8. /trade/v1/info/thorchain-inbound-address:This endpoint returns the contract addresses of the smart contracts that involves BTC trading .

  9. /trade/v1/info/trade/{txHash}: This endpoint returns the information of a cross chain trade given its transaction hash in the chain from.

  10. /trade/v1/info/trade/{chainId}/{txHash}This endpoint returns the information of a trade conducted using our API. It can be single or cross chain. For cross chain trades, the txHash has to be the on on the origin chain.

These endpoints are interconnected, with /chains providing an overview of available chains, /sources identifying the exchanges available in our API on each chain, and /search enabling users to query and retrieve specific information of tokens based on their requirements. The combination of these endpoints helps users navigate and access the desired data efficiently.

https://github.com/unizen-io/unizen-dex-aggregator-example