Get an asset

data

• idstringrequired

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

• filenamestringrequired
• urlstringrequired

  Publicly reachable URL for the stored bytes.

• content_typestringrequired

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

• size_bytesintegerrequired
• 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

• created_atstring (date-time)required

meta

• pageinteger
• totalinteger
• limitinteger

  The page size actually applied, which is not necessarily the one asked for — the operation's own ceiling wins.

• pagesinteger

  total over limit, rounded up.

• next_cursorstring | null

  On a cursor-paged operation: send this back as cursor for the next page. Null on the last page. Absent on operations that do not page by cursor.

• has_moreboolean

  On a list operation whose meta is ListMeta: whether another page follows this one.