Ideogram Contract Upgrade

Overview

Move a bounded adapter contract to a current Ideogram route without mixing the change with a broad product migration. Diff OpenAPI and endpoint documentation, update owned types and fixtures, run shadow comparisons, and preserve an explicit traffic rollback.

Prerequisites

• Current adapter SHA, endpoint inventory, target contract, consumers, and accountable owner.
• Captured sanitized fixtures and compatibility requirements.
• Canary budget, traffic control, storage parity, and rollback deadline.

Current Contract

The current surface spans V4, P-Image, V3, outcome-focused tools, custom training, and routes labeled Legacy Endpoints. V4 generation uses endpoint-specific multipart forms; text_prompt and json_prompt are mutually exclusive, and current V4 FLASH support must not be inferred from V3 examples.

Authentication

Keep the same server-side Api-Key boundary unless a documented first-party auth change is part of the reviewed diff. Never copy production credentials or payloads into migration fixtures.