Transaction metadata labels

GET /metadata/txs/labels

List of all used transaction metadata labels.

Request

Query Parameters

count integer

Possible values: >= 1 and <= 100

Default value: 100

The number of results displayed on one page.

page integer

Possible values: >= 1 and <= 21474836

Default value: 1

The page number for listing the results.

order string

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.

Responses

• 200
• 400
• 403
• 404
• 418
• 429
• 500

---

Return the account metadata content in CBOR

application/json

Schema

Example (from schema)

---

Schema

• Array [
label string required

Metadata label

cip10 string nullable required

CIP10 defined description

count string required

The count of metadata entries with a specific label

• ]

[
  {
    "label": "1990",
    "cip10": null,
    "count": "1"
  },
  {
    "label": "1967",
    "cip10": "nut.link metadata oracles registry",
    "count": "3"
  },
  {
    "label": "1968",
    "cip10": "nut.link metadata oracles data points",
    "count": "16321"
  }
]

Bad request

application/json

Schema

Example (from schema)

---

Schema

status_code integer required
error string required
message string required

{
  "status_code": 400,
  "error": "Bad Request",
  "message": "Backend did not understand your request."
}

Authentication secret is missing or invalid

application/json

Schema

Example (from schema)

---

Schema

status_code integer required
error string required
message string required

{
  "status_code": 403,
  "error": "Forbidden",
  "message": "Invalid project token."
}

Component not found

application/json

Schema

Example (from schema)

---

Schema

status_code integer required
error string required
message string required

{
  "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

application/json

Schema

Example (from schema)

---

Schema

status_code integer required
error string required
message string required

{
  "status_code": 418,
  "error": "Requested Banned",
  "message": "IP has been auto-banned for flooding."
}

Usage limit reached

application/json

Schema

Example (from schema)

---

Schema

status_code integer required
error string required
message string required

{
  "status_code": 429,
  "error": "Project Over Limit",
  "message": "Usage is over limit."
}

Internal Server Error

application/json

Schema

Example (from schema)

---

Schema

status_code integer required
error string required
message string required

{
  "status_code": 500,
  "error": "Internal Server Error",
  "message": "An unexpected response was received from the backend."
}

Loading...