Skip to main content

Assets

What this lets you do

Upload one reference image and download a finished image without exposing storage details.

What you need

  • A server-side DreamLayer key
  • A supported PNG, JPEG, or WebP input for image-to-image
  • The owner account for every asset request

Steps

1. Create an input asset

POST /v1/input-assets creates one normalized owner-scoped PNG and returns:
Source metadata, filenames, and local paths are not part of the managed execution contract. Expired inputs are cleaned automatically.

2. Download a finished asset

A completed job returns at most one PNG asset in V1. Download URLs authorize only the owning account and must not reveal internal storage paths or private routing metadata.

Confirm it worked

The input response reports normalized PNG metadata. A completed execution returns one owned download URL that serves the finished PNG.

Common errors

  • 413: reduce the file bytes, dimensions, or pixels.
  • 404: use a current asset owned by the authenticated account.
  • Expired inputs must be uploaded again.

Troubleshooting

Do not cache an input beyond its expires_at value. Do not put signed download URLs in public logs or monitoring.

Next steps