Whitelist Proxy Contracts

Authorize your DApp User's Proxy Contracts

If you have implemented native meta transactions via external contract wallet approach 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 generated an access token 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

NameTypeDescription

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

NameTypeDescription

addresses

array

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

{
    "code": 200,
    "message": "Proxy contracts whitelisted successfully"
}

/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

NameTypeDescription

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
    } ]
}

/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

NameTypeDescription

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

NameTypeDescription

status

boolean

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

address

string

Address for changing the status.

{
    "code": 200,
    "message": "Address status updated successfully"
}

Last updated