Ideogram Data Lifecycle

Overview

Map and enforce the lifecycle of every datum that crosses an Ideogram workflow. Distinguish prompts, JSON descriptions, source media, masks, generated outputs, temporary links, safety decisions, metadata, logs, and custom-training assets because each has different ownership and retention needs.

Prerequisites

• Use case, data owner, tenant, classification, rights basis, region, retention, and deletion SLO.
• Architecture for upload, API, async state, webhook, polling, download, storage, review, publication, backup, and telemetry.
• Vendor terms and privacy review appropriate to the workload.

Current Contract

V4 describe can transform an uploaded image into a structured json_prompt; its bounding boxes use normalized [0,1000] coordinates in [y_min,x_min,y_max,x_max] order. Output URLs expire. Custom training supports datasets of 10–100 images, optional captions or ZIP upload, model training, and model-status retrieval.

Authentication

Keep IDEOGRAM_API_KEY outside data stores and send it only as Api-Key from a trusted server. Application authorization must bind every input, generated object, dataset, and trained-model reference to its tenant and purpose.