Ideogram Authentication and Installation

Overview

Establish a reviewable Ideogram API boundary before any paid generation runs. Separate developer-account enrollment, team ownership, billing, secret storage, and application authorization so a valid key never becomes accidental authority for a browser or untrusted tenant.

Prerequisites

• A named Ideogram team Owner and accountable application owner.
• Accepted developer terms, a payment method, and positive prepaid API credit.
• A server-side secret manager and an environment-specific rollback plan.

Current Contract

Ideogram API subscriptions and web-app subscriptions are billed separately. Keys are created in the API dashboard, displayed once, revocable, and shared against the team's credit balance. Team roles are Owner, Admin, and Member; multiple keys do not create separate balances.

Authentication

Store the key as IDEOGRAM_API_KEY and send it only in the Api-Key header to https://api.ideogram.ai. Never place it in source control, URLs, browser bundles, prompts, logs, screenshots, or client telemetry. Treat application user authorization as a separate control.