List your uploaded assets

data

• assetsobject[]
• assets[].idstringrequired

  ast_…. POST /v1/order accepts this directly as an item's print_file, in place of a URL.

• assets[].filenamestringrequired
• assets[].urlstringrequired

  Publicly reachable URL for the stored bytes.

• assets[].content_typestringrequired

  One of image/png image/jpeg image/svg+xml application/pdf

• assets[].size_bytesintegerrequired
• assets[].sourcestringrequired

  Where the bytes came from: upload (sent through POST /v1/assets or the dashboard), mockup (a render from POST /v1/mockups/generate), listing (the photograph a checkout link gets on its first publish), design (artwork a design run generated), carryover (a listing image a listing import fetched and rehosted), manifest (a production batch's manifest), fixup (a copy of your artwork with its bleed, margin or outline fixed by POST /v1/artwork/validate with auto_fix). A fact, not a filter: every asset surface lists, exports and deletes a render exactly as an upload, and there is no ?source= on the list. Files stored before the field existed were classified from their filenames and read upload where nothing said otherwise.

  One of upload mockup listing design carryover manifest fixup

• assets[].created_atstring (date-time)required
• next_cursorstring | null

  The same as meta.next_cursor: send it back as cursor for the next page. Null on the last page.

• paginationobject
• pagination.pageinteger
• pagination.limitintegerrequired
• pagination.totalintegerrequired
• pagination.pagesinteger

meta

• pageintegerdeprecated

  The page number of the deprecated offset walk, on the lists that published it (orders and an order's events, on every request without cursor; products, on a request that sent page). Absent on a cursor walk, where no page number would be true.

• totalinteger

  Every row matching the request's filters, on the lists that count them (orders, an order's events, assets and products).

• limitinteger

  The page size applied, which is not necessarily the one asked for: a larger limit is clamped. Absent only on a GET /products request without cursor that sent no limit, which answers every match.

• pagesintegerdeprecated

  total over limit, rounded up, beside page (orders and an order's events). Absent on a cursor walk.

• next_cursorstring | nullrequired

  Send it back as cursor for the next page; null exactly when has_more is false. Opaque: pass it back unchanged. Good only on the list that returned it, with a key of the same account and mode (test or live), and with the same filters.

• has_morebooleanrequired

  Whether another page follows this one. Decided from one row past this page, never from a page that came back short — so a page after has_more: true can come back empty only if rows were deleted in between, and the walk still ends at the first has_more: false.

• sincestring | null

  On GET /order/{id}/events only: where to ask from next — the position of the last event in this answer, or, when it has none, the position the request read from. Send it back as since (with wait_seconds to wait for the next event). Unlike next_cursor it is not null at the end of the history; it is null only when the order has no events and the request named no position. Opaque, and bound like a cursor to this order, account and key mode.