Skip to main content

🚀 apiv2 is live!

Soundverse’s Enterprise API has moved to apiv2.soundverse.ai, with new self-serve account setup, API keys, and billing all managed at platform.soundverse.ai. Everything below this point documents the legacy api.soundverse.ai domain — if you’re setting up a new integration, click through for current endpoints, request/response shapes, and auth.
🔗 Soundverse Platform  |  Current API Docs (apiv2)
Soundverse’s Enterprise API lets you generate and edit music programmatically covering AI song generation (with lyrics + vocals), instrumental music generation, extend, lyrics, singing, stem separation, and loop/trim, with both streaming (SSE) and synchronous workflows depending on the endpoint. Soundverse is constantly adding new endpoints to make it an extensive platform with all potential Audio AI usecases.
The endpoints, base domain, and key-issuance flow described on this page are for the legacy api.soundverse.ai API. Accounts and API keys created through the current self-serve platform (platform.soundverse.ai) are not recognized on this legacy domain and will return 403 Invalid API Key there — use apiv2.soundverse.ai instead. See the current docs for up-to-date endpoints.
Base domain (legacy — you’ll hit different paths depending on the endpoint/version): https://api.soundverse.ai. For new integrations, use https://apiv2.soundverse.ai instead — see the current API docs. Pick your API plan based on expected usage:
  • Starter (includes Royalty-Free)
  • Growth (includes Sample)
  • Scale (includes Distribution)
  • Pay as you go (Choose any License)
Soundverse’s API licensing is plan-based by default and you can upgrade licenses via dashboard, or contact the Soundverse Support.

​
How to get an API key

  1. Sign in at platform.soundverse.ai and set up your enterprise account.
  2. Generate a key from the dashboard’s API Keys page.
  3. Send it on every request using a Bearer header against apiv2.soundverse.ai (see the current docs for endpoint-specific examples).
Legacy flow (existing api.soundverse.ai integrations only): purchase a plan, open the old API Dashboard, and generate a key from there. Keys from that flow are not valid on apiv2.soundverse.ai, and keys from the new platform dashboard are not valid on api.soundverse.ai — the two are separate systems.
Example header:

​
How to choose the right license

Here’s the simplest way to decide (you can also show this as a tooltip / helper in your onboarding):
  • Royalty-Free (default on many plans): broad commercial use for exported tracks, but no reselling raw/unmodified exports as libraries/sample packs.
  • Sample: you can sample/chop/transform exports inside a new work, but still not resell raw exports “as is.”
  • Distribution: use when you want explicit rights to release to DSPs/social platforms (Spotify/Apple/YouTube/TikTok, etc.).
  • Sync: use when pairing music to picture (film/TV/ads/games/apps/campaigns), typically project/campaign scoped.
  • Full Ownership: exclusive buy-out of the master for that track—best for high-stakes brand work / catalogs / label deals, with broad exploitation rights.
Plan mapping:
  • Starter includes Royalty-Free
  • Growth includes Sample
  • Scale includes Distribution, with upgrades optional
  • Pay as you go has All Licenses, but costs more
FAQ links (recommended to surface in your docs)

​
Available API Endpoints (legacy api.soundverse.ai)

Building something new? Check platform.soundverse.ai/docs for the current endpoint list on apiv2.soundverse.ai first — not every legacy endpoint below has an apiv2 equivalent yet.

​
AI Song Generation

​
AI Music (Instrumental) Generation

​
AI Extend

​
AI Remix

​
AI Lyric Generation

​
AI Singing

​
AI Stem Separation

​
Loop And Trim

​
AI Chat (Beta)

​
Check Status (/v5/status)

  • Method: GET
  • Path: /v5/status
  • Query parameters:
    • message_id (required) — string ID of the request to check
Example Request
Successful Response (200)
Errors
  • 401 — Invalid API key format. Use Bearer <your_api_key>.
  • 422 — Validation Error (invalid or missing message_id).