Assets
GET /assets
List of assets. If an asset is completely burned, it will stay on the list with quantity 0 (order of assets is immutable).
Request
Query Parameters
Possible values: >= 1
and <= 100
Default value: 100
The number of results displayed on one page.
Possible values: >= 1
and <= 21474836
Default value: 1
The page number for listing the results.
Possible values: [asc
, desc
]
Default value: asc
The ordering of items from the point of view of the blockchain, not the page listing itself. By default, we return oldest first, newest last. Ordering in this case is based on the time of the first mint transaction.
- 200
- 400
- 403
- 404
- 418
- 429
- 500
Return list of assets
Schema
- Array [
- ]
Asset identifier
Current asset quantity
[
{
"asset": "b0d07d45fe9514f80213f4020e5a61241458be626841cde717cb38a76e7574636f696e",
"quantity": "1"
},
{
"asset": "b0d07d45fe9514f80213f4020e5a61241458be626841cde717cb38a76e75d",
"quantity": "100000"
},
{
"asset": "6804edf9712d2b619edb6ac86861fe93a730693183a262b165fcc1ba1bc99cad",
"quantity": "18605647"
}
]
Bad request
Schema
{
"status_code": 400,
"error": "Bad Request",
"message": "Backend did not understand your request."
}
Authentication secret is missing or invalid
Schema
{
"status_code": 403,
"error": "Forbidden",
"message": "Invalid project token."
}
Component not found
Schema
{
"status_code": 404,
"error": "Not Found",
"message": "The requested component has not been found."
}
IP has been auto-banned for extensive sending of requests after usage limit has been reached
Schema
{
"status_code": 418,
"error": "Requested Banned",
"message": "IP has been auto-banned for flooding."
}
Usage limit reached
Schema
{
"status_code": 429,
"error": "Project Over Limit",
"message": "Usage is over limit."
}
Internal Server Error
Schema
{
"status_code": 500,
"error": "Internal Server Error",
"message": "An unexpected response was received from the backend."
}