IDRX Documentation
  • Introduction
    • IDRX Whitepaper
    • Supported Chain and Contract Address
  • IDRX Account
    • Create Account
    • Sign In
    • Forgot Password
    • Account Verification (KYC)
    • Business Account
  • Services
    • Mint IDRX
    • Redeem IDRX
    • Bridge IDRX
    • Get Other Tokens
    • Redeem Other Stablecoin
    • Fees
  • API
    • Getting Started
    • Generating a Signature
    • Onboarding API
      • POST /api/auth/onboarding
      • GET /api/auth/members
      • POST /api/auth/add-bank-account
      • GET /api/auth/get-bank-accounts
      • DELETE /api/auth/delete-bank-account/:bankId
    • Transaction API
      • POST /api/transaction/mint-request
      • POST /api/transaction/redeem-request
      • POST /api/transaction/bridge-request
      • GET /api/transaction/method
      • GET /api/transaction/user-transaction-history
      • GET /api/transaction/rates
      • GET /api/transaction/get-additional-fees
  • Smart Contract
    • Staking
      • Staking Type
      • Staking IDRX
      • Claim Staking Reward
      • Unbond Staked IDRX
      • Claim Unbonded IDRX
      • Claim Principal and Staking Rewards
      • Application Binary Interface
  • Integration
    • Overview
    • Onboarding a new user
    • Managing bank accounts
    • Processing mint requests
      • Getting other tokens
    • Processing redeem requests
      • Redeeming from other tokens
Powered by GitBook
On this page
  • Parameters
  • Example Request
  • Response
  1. API
  2. Transaction API

POST /api/transaction/bridge-request

Use this API to request a IDRX bridge transaction.

PreviousPOST /api/transaction/redeem-requestNextGET /api/transaction/method

Last updated 23 days ago

Check to see the list of chains where IDRX is available

Parameters

  1. txHashBurn (String):

    This parameter represents the unique transaction hash or identifier associated with the burning (redeeming) of IDRX tokens.

  2. bridgeToChainId (Number):

    This parameter identifies the target blockchain network where the stable tokens are being bridged.

  3. bridgeFromChainId (Number):

    This parameter indicates the source blockchain network from which the stable tokens are being bridged.

  4. amount (String):

    This parameter specifies the quantity or value of stable tokens being bridged.

  5. bridgeNonce (String):

    This parameter is a unique identifier received from the burning transaction event. It acts as a nonce, ensuring the uniqueness of the bridging transaction.

Example Request

curl -X POST '<https://idrx.co/api/transaction/mint-bridge-request>' --header 'idrx-api-key: <API_KEY>' --header 'idrx-api-sig: <signature>' --header 'idrx-api-ts': <timestamp>'

Payload

{
  "txHashBurn": "string",
  "bridgeToChainId": 0,
  "bridgeFromChainId": 0,
  "amount": "string",
  "bridgeNonce": "string"
}

Response

If the request is successful, the response will be as shown below:

{
  "statusCode": 201,
  "message": "success",
  "data": {
    "id": 3,
    "userId": 1,
    "bridgeFromChainId": 80001,
    "bridgeToChainId": 97,
    "txHashBurn": "0x38ef6a20db393505fbae51f5f9ec9197013cee21bccafabf8ef37261aa2039d9",
    "txHashMint": null,
    "qredoTxId": null,
    "signedTx": null,
    "bridgeNonce": "0",
    "amount": "100000",
    "bridgeStatus": "REQUESTED",
    "deleted": false
  }
}

To check the status of your transaction, you can use the .

this page
Transaction History API
Page cover image