Get ERC20 list asset bundle

Get the signatures bundle to allowlist an ERC20 token in the collateral bridge

Query Parameters

assetId string required

Asset ID of the asset bundle requested.

Responses

• 200
• 500
• default

---

A successful response.

application/json

Schema

Example (from schema)

---

Schema

assetSource string

Address of the asset on Ethereum.

nonce string

Nonce that uniquely identifies this signature bundle and prevents resubmission.

signatures string

Signatures bundle as hex encoded data, prefixed with 0x e.g: 0x + sig1 + sig2 + ... + sixN.

vegaAssetId string

Asset ID for the underlying Vega asset.

{
  "assetSource": "string",
  "nonce": "string",
  "signatures": "string",
  "vegaAssetId": "string"
}

An internal server error

application/json

Schema

Example (from schema)

---

Schema

code int32
details object[]
Array [
@type string
A URL/resource name that uniquely identifies the type of the serialized protocol buffer message. This string must contain at least one "/" character. The last segment of the URL's path must represent the fully qualified name of the type (as in path/google.protobuf.Duration). The name should be in a canonical form (e.g., leading "." is not accepted).
In practice, teams usually precompile into the binary all types that they expect it to use in the context of Any. However, for URLs which use the scheme http, https, or no scheme, one can optionally set up a type server that maps type URLs to message definitions as follows:
• If no scheme is provided, https is assumed.
• An HTTP GET on the URL must yield a [google.protobuf.Type][] value in binary format, or produce an error.
• Applications are allowed to cache lookup results based on the URL, or have them precompiled into a binary to avoid any lookup. Therefore, binary compatibility needs to be preserved on changes to types. (Use versioned type names to manage breaking changes.)
Note: this functionality is not currently available in the official protobuf release, and it is not used for type URLs beginning with type.googleapis.com.
Schemes other than http, https (or the empty scheme) might be used with implementation specific semantics.
]
message string

{
  "code": 0,
  "details": [
    {
      "@type": "string"
    }
  ],
  "message": "string"
}

An unexpected error response.

application/json

Schema

Example (from schema)

---

Schema

code int32
details object[]
Array [
@type string
A URL/resource name that uniquely identifies the type of the serialized protocol buffer message. This string must contain at least one "/" character. The last segment of the URL's path must represent the fully qualified name of the type (as in path/google.protobuf.Duration). The name should be in a canonical form (e.g., leading "." is not accepted).
In practice, teams usually precompile into the binary all types that they expect it to use in the context of Any. However, for URLs which use the scheme http, https, or no scheme, one can optionally set up a type server that maps type URLs to message definitions as follows:
• If no scheme is provided, https is assumed.
• An HTTP GET on the URL must yield a [google.protobuf.Type][] value in binary format, or produce an error.
• Applications are allowed to cache lookup results based on the URL, or have them precompiled into a binary to avoid any lookup. Therefore, binary compatibility needs to be preserved on changes to types. (Use versioned type names to manage breaking changes.)
Note: this functionality is not currently available in the official protobuf release, and it is not used for type URLs beginning with type.googleapis.com.
Schemes other than http, https (or the empty scheme) might be used with implementation specific semantics.
]
message string

{
  "code": 0,
  "details": [
    {
      "@type": "string"
    }
  ],
  "message": "string"
}

GET /api/v2/erc20/asset/list/bundle

Request

Base URL

https://vega-data.nodes.guru:3008

assetId — query required

curl / cURL

curl -L -X GET 'https://vega-data.nodes.guru:3008/api/v2/erc20/asset/list/bundle' \
-H 'Accept: application/json'

python / requests

curl -L -X GET 'https://vega-data.nodes.guru:3008/api/v2/erc20/asset/list/bundle' \
-H 'Accept: application/json'

go / native

curl -L -X GET 'https://vega-data.nodes.guru:3008/api/v2/erc20/asset/list/bundle' \
-H 'Accept: application/json'

nodejs / axios

curl -L -X GET 'https://vega-data.nodes.guru:3008/api/v2/erc20/asset/list/bundle' \
-H 'Accept: application/json'