CryptiumPayDocs
API reference

Get a catalog item

Retrieve one item owned by the authenticated merchant, including an archived item.

GET/api/items/{item_id}

Read one owned item, including archived items. Requires merchant-id and signature headers.

Request fields from the OpenAPI specification
FieldTypeRequiredDescription
item_idpathstringYesCatalog item UUID.

Source: download OpenAPI 3.1. Examples below use illustrative values.

Set CRYPTIUM_API_URL to your API origin. Authenticated examples also use CRYPTIUM_MERCHANT_ID and CRYPTIUM_API_KEY from your server environment. Replace the example IDs and asset codes with values from your deployment.

cURL
signature=$(printf '%s' '{}' | openssl dgst -sha256 -hmac "$CRYPTIUM_API_KEY" -r)
signature=${signature%% *}
curl --silent --show-error --fail-with-body --max-time 15 \
  --request GET "${CRYPTIUM_API_URL%/}/api/items/11111111-1111-4111-8111-111111111111" \
  --header "merchant-id: $CRYPTIUM_MERCHANT_ID" \
  --header "signature: $signature"

cURL requires OpenSSL and cURL 7.76+. JavaScript uses Node.js 18+; Python 3 uses the standard library; PHP requires the cURL extension. JSON bodies are compact UTF-8: sign the serialization described in authentication.

Example response

{
  "id": "11111111-1111-4111-8111-111111111111",
  "merchant_id": "33333333-3333-4333-8333-333333333333",
  "name": "Example item",
  "amount": "19.95",
  "currency": "USD",
  "description": null,
  "icon_url": null,
  "success_url": null,
  "archived_at": null,
  "created_at": "2026-10-24T12:00:00.000Z",
  "updated_at": "2026-10-24T12:00:00.000Z"
}

The path ID must be a UUID. A missing item and an item belonging to another merchant both return 404 ITEM_NOT_FOUND.

An archived item remains readable, but cannot be used for a new invoice from item. archived_at contains the archival timestamp when archived.

Sign {} for the bodyless GET. The item ID is in the path and is not included in the current signature payload.

On this page