Skip to content

OmnAPI AI Music, Image, Lyrics, and Music Video API

Overview

Choose a product for the result you need. OmnAPI uses one server-side API key and credit balance, with Task receipts for asynchronous work.

Your goalStart hereWhat you receive
Generate a song from a sound promptProducerMUSIC resources, with optional lyrics and artwork
Generate or derive Suno songsSunoA Generation with song candidates and a billing Task
Turn a song into a music videoMusic VideoA video workflow, scenes, and final video URLs
Run a selected video, image, or audio operationViduOperation-specific generated resources
Create a structured lyric packageLyricsLyrics, language plans, and music-ready prompts
Crop, repeat, reorder, or fade audioAudio editingOne edited MP3 or WAV
Extract timed lyrics from audioSubtitlesTimeline and subtitle files

For a minimal integration, create your first task.

  1. Authenticate with a server-side API key and review the operation’s price.
  2. Submit a request with a saved idempotency key where supported.
  3. Save the receipt before waiting. Acceptance does not mean output is ready.
  4. Read the Task until terminal, or receive a webhook.
  5. Consume the product’s result and retain needed files before expiry.

The Task model explains execution and billing fields. Product views can differ: Suno Generations expose candidates and live playback, while Music Video provides scene and final-video views. Follow the product guide for its result paths instead of assuming every HTTP response has one shape.

Check authentication, permissions, and credits and settlement. A published endpoint may have operation- or account-specific availability. The receipt and actual availability response remain authoritative.

If a write times out, recover the original operation before creating another one. OmnAPI is focused on media generation workflows; these guides do not describe a streaming chat-token API.