create_item_asset

Creates a new item-type asset, including amount, public key, signature, and related metadata fields where required by the release you target.

Endpoint

POST https://mempool.lineage.to/create_item_asset

Headers

Request body (fields)

• item_amount — number of Item assets to create.
• script_public_key — receiving or controlling address (encoding depends on the network).
• public_key and signature — key material used for the creation.
• drs_tx_hash_spec — whether you follow the default DRS identifier scheme for item assets; naming may vary by product release (string or structured value per the node you use).

Complete JSON example

{
  "item_amount": 1,
  "script_public_key": "<receiving or controlling lock / address encoding>",
  "public_key": "<hex>",
  "signature": "<hex>",
  "drs_tx_hash_spec": "default"
}

Example

curl -sS -X POST "https://mempool.lineage.to/create_item_asset" \
  -H "Content-Type: application/json" \
  -H "x-cache-id: 0123456789abcdef0123456789abcdef" \
  -d @item-asset.json

Responses

200 on success, 400 on validation or signing issues. content includes created asset data (e.g. amount, tx_hash, metadata) in successful responses.

Envelope fields (typical)

• id — idempotency id (matches x-cache-id).
• status — one of Success, Error, or Pending.
• reason — human-readable detail; especially useful for errors.
• route — logical route name for the call.
• content — payload; shape depends on the operation.

Example success payload

{
  "id": "0123456789abcdef0123456789abcdef",
  "status": "Success",
  "reason": "Item asset created",
  "route": "create_item_asset",
  "content": {
    "item_amount": 1,
    "tx_hash": "<32-byte-hex transaction id>",
    "metadata": {}
  }
}

Example error envelope (typical 400)

{
  "id": null,
  "status": "Error",
  "reason": "Bad Request",
  "route": null,
  "content": null
}