Why teams evaluate this API
Built for teams migrating from Suno-specific integrations or adding direct Suno workflows alongside broader music generation APIs.
Create Suno songs through simple prompts, custom lyrics, reusable public Voices, and managed upload + Extend/Cover with one OmnAPI task model.
Built for teams migrating from Suno-specific integrations or adding direct Suno workflows alongside broader music generation APIs.
Set OMNAPI_KEY on your server and create REQUEST_ID once for this logical request. Reuse that ID on transport retries. A new generation can incur a charge; review current pricing first.
curl --fail-with-body --max-time 60 -X POST "https://api.omnapi.com/api/v1/suno/songs" \
-H "x-api-key: $OMNAPI_KEY" \
-H "Idempotency-Key: $REQUEST_ID" \
-H "Content-Type: application/json" \
--data '{
"mode": "simple",
"prompt": "Upbeat city pop, bright guitars, summer night drive",
"model": "chirp-fenix"
}'This example selects chirp-fenix explicitly. Save taskId and inspect /api/v1/suno/generations/{taskId} for individual clip playback states; the shared Task API provides execution and billing details.
See the authentication and task quickstart and complete request schema.
No. Producer Compose is a higher-level composition surface. Suno Songs is the direct Suno workflow surface for teams that specifically want Suno generation modes.
Yes, but the new public API is task-first and uses `/api/v1/suno/*`. Keep a compatibility facade during migration if existing clients cannot change request and response shapes immediately.