GET/api/v1/assets
List every asset observed on the chain, newest first.
Without parameters: the whole registry, as before. limit and offset cut a page out of it; q, issuer, supply and resolved narrow it first, and order=named_first brings attested names to the front. All of them are the caller's view, never moderation: everything stays reachable without them.
Three headers carry what a pager needs: X-Registry-Count (assets listed at all), X-Total-Count (assets matching the filters, before the page is cut) and X-Unresolved-Count (those among them without a resolved description). The response carries an ETag; send it back in If-None-Match and an unchanged listing answers 304 with no body.
Parameters
- limitinteger · query
Keep only the newest N assets. Omitted: the whole registry (what a client doing its own search or mirroring wants).
- offsetinteger · query
Skip this many assets before the first one returned. With
limit, a page. The totals a pager needs come back as headers.- resolvedboolean · query
true: keep only assets whose description is known, so their name is attested rather than an id. Omitted: everything, which stays the default - this is a caller's view preference, never moderation.- qstring · query
Keep assets whose name or description contains this text (case ignored), or whose asset id or issuer key starts with it.
- issuerstring · query
Keep only assets minted under this issuance key (hex).
- supply"sealed" | "open" · query
sealed: finalized assets only.open: the others.- order"named_first" | "active" · query
named_first: sealed names, then free-text labels, then unnamed, chain order kept inside each group.active: latest public event (issuance, burn or seal) first. Omitted: newest first.
Answers
- 200AssetSummaryResponse[]
ETagValidator forIf-None-MatchX-Registry-CountAssets listed, before any filterX-Total-CountAssets matching the filters, beforeoffsetandlimitX-Unresolved-CountMatching assets without a resolved description- 304
The listing the caller holds is still current
- 400ProblemDetails
A problem document (RFC 9457):
type,title,status,detail.- 503ProblemDetails
A problem document (RFC 9457):
type,title,status,detail.
curl "https://api.cachetzec.com/api/v1/assets"