POSTCreate Assets

Create or update the assets linked to products. Each item names one parent_code and, per channel, an ordered list of URLs: the Nth URL becomes rank N and is stored under the Nth image attribute of that channel's image configuration. A blank URL, or the text null, none, nan or nat, is skipped but keeps its position, so the following URLs keep their rank. A channel cannot hold more URLs than its image configuration has positions. A URL may appear only once per channel list, and a parent_code may appear only once per channel and asset_type in a request. The parent_code must belong to a product in the store: when none exists the code is skipped and reported in error_info with reason product_not_found, while the other items are still written. Pass product_uuid to skip that check for an item. Each new image asset is stored first without an asset_id; the assets service then re-hosts the image and assigns asset_id and the Streamoid URL, so read them back with GET /v1/assets. For an image added to a product and channel that already has assets this always runs. For the first image of a product and channel, or an image that links an existing unlinked document to the product, the assets service runs the store's enabled automations instead, and asset_id is assigned only when image_upload is one of them. Assets of any other asset_type are stored but never re-hosted, so they get no asset_id from this call. A request carries at most 100 items and 10 MiB, otherwise it fails with 413. failed counts assets the assets service rejected plus one per unknown parent_code.