Biconomy Gasless SDK (EOA)
DashboardMediumWebsite
  • 🚀Getting Started
  • Introduction
    • 🤘Why Biconomy?
    • 🙂How we simplify transactions
  • Products
    • 💸Gasless Transactions
      • Choose An Approach to Enable Gasless
        • Standard EIP 2771 Approach
          • 1. Register Artifacts on the Dashboard
          • 2. Code Changes
            • Using SDK
            • Using API
        • Custom Implementation Approach
          • 1. Register Artifacts on the Dashboard
          • 2. Code Changes
            • Using SDK
            • Using API
        • Smart Contract Wallet Approach
          • Gnosis
        • Network Agnostic Transactions
          • EIP-2771 Approach
          • Custom Approach
      • Conditional Whitelisting
      • Gasless SDK (EOA) 3
      • Networks Supported
    • ↔️Hyphen - Instant Cross-Chain Transfers
      • SDK
        • DepositManager
        • TransferManager
        • TokenManager
      • APIs
      • Helper Methods
      • Migrating from Hyphen V1
      • Contract Addresses
      • Hyphen Widget
  • Guides
    • 💻Dashboard
      • DApp Statistics
    • ⛽Gas Tank Deposits
      • Via Dashboard
      • Via Smart Contract
  • api
    • 🔧Native Meta Transaction
      • Get Retried Hashes
    • 🌎Dashboard APIs
    • ⚪Whitelist API
      • Whitelist Destination Address
      • Whitelist Proxy Contracts
    • 〰️ Check Limits
    • 💿Biconomy Data API
      • 👨‍🚀Unique User Data
      • 🧑‍🔧Per User Limits Data
      • ⛽Gas Tank Balance Data
  • SDK
    • 📙Gasless SDK (EOA)
      • Configuration
  • Tutorials
    • 🔰Native Meta Transactions
      • How To Build Your First DApp
        • Write Your First Smart Contract
        • Initialize Web3 on Client Side
        • Executing First Blockchain Transaction
      • Enable Native Meta Transactions
        • Smart Contract
          • Describe Your Structs
          • Declare Your Variables
          • Modify Respective Function
        • Client Side
          • Design Your JSON structure
          • Design Your Domain Separator
          • Design Data Types
          • Define Data To Sign
          • Generate Signatures
      • Integrate Biconomy
        • Register On Dashboard
        • Integrate Gasless SDK (EOA)
      • Summary
  • BICO Staking
    • 🪁Safety Module
  • Get in touch
    • 👥Contact Us
  • Misc
    • 🧩Projects on Biconomy
    • 🌐Supported Networks
    • 📫Contract Addresses
    • ✔︎ Smart Contracts Audit
    • ❓FAQs
Powered by GitBook
On this page
  • /api/v1/dapp/whitelist/proxy-contracts
  • /api/v1/dapp/whitelist/proxy-contracts
  • /api/v1/dapp/whitelist/proxy-contracts

Was this helpful?

  1. api
  2. Whitelist API

Whitelist Proxy Contracts

Authorize your DApp User's Proxy Contracts

PreviousWhitelist Destination AddressNext〰️ Check Limits

Last updated 4 years ago

Was this helpful?

If you have implemented native meta transactions via pproach like Gnosis or Argent, you need to whitelist all proxy contracts registered in your DApp before using meta transaction APIs.

This guide will help you whitelist, list and update the status of the whitelisted proxy contracts.

Before using this API, make sure you have from the dashboard which is visible in you View DApp section on dashboard.

/api/v1/dapp/whitelist/proxy-contracts

POST https://api.biconomy.io/api/v1/dapp/whitelist/proxy-contracts

Whitelist proxy addresses. Only whitelisted proxy addresses will be authorized to do meta transactions.

Headers

Name
Type
Description

Authorization

string

Token present on the dashboard for your DApp after you have generated token. This is specific to DApp registered and should be in the format "User <token generated>"

Request Body

Name
Type
Description

addresses

array

An array of proxy contract addresses for whitelisting for your dapp.

{
    "code": 200,
    "message": "Proxy contracts whitelisted successfully"
}
{
    "code": 400,
    "message": "No proxy address found in the request"
}
{
    "code": 401,
    "message": "Token is required in the request header"
}

/api/v1/dapp/whitelist/proxy-contracts

GET https://api.biconomy.io/api/v1/dapp/whitelist/proxy-contracts

Get a list of whitelisted proxy contracts.

Headers

Name
Type
Description

Authorization

string

Token present on the dashboard for your Dapp after you have generated token. It should be in the format "User <token generated>"

{
    "code": 200,
    "message": "Proxy addresses fetched successfully",
    "total": 5,
    "addresses": [ {
        address : "",
        status : true
    } ]
}
{
    "code": 401,
    "message": "Token is required in the request header"
}

/api/v1/dapp/whitelist/proxy-contracts

PATCH https://api.biconomy.io/api/v1/dapp/whitelist/proxy-contracts

Make your proxy contracts status active or inactive via this api. Only active proxy contracts will be allowed to relay meta transactions.

Headers

Name
Type
Description

Authorization

string

Token present on the dashboard for your Dapp after you have generated token. This is specific to DApp registered and should be in the format "User <token generated>"

Request Body

Name
Type
Description

status

boolean

Either 0 or 1. 0 => Inactive 1 => active

address

string

Address for changing the status.

{
    "code": 200,
    "message": "Address status updated successfully"
}
{
    "code": 400,
    "message": "Contract address format is invalid"
}

or 

{
    "code": 400,
    "message": "Address status should be a number of either 0 or 1"
}
{
    "code": 401,
    "message": "Token is required in the request header"
}
{
    "code": 404,
    "message": "Contract address does not exist"
}
⚪
external contract wallet a
generated an access token