Suno API Quickstart
This guide is the fastest path to a working Suno API integration on TTAPI. It is designed for teams that want to go from API key to first completed song without reading every endpoint page first. For the complete endpoint directory, start with the Suno API overview.What this quickstart covers
- Getting your
TT-API-KEY - Choosing the first Suno endpoint to call
- Creating lyrics or going straight to music generation
- Fetching asynchronous results
- Continuing the workflow with cover, extend, stems, or export steps
1. Prepare your account
Before you call Suno endpoints, make sure you have:- A valid
TT-API-KEY - Access to the TTAPI gateway described in Gateway & Auth
- Enough quota for the endpoints you plan to use in Audio Pricing
2. Pick your starting endpoint
Use the endpoint that matches your real starting asset:| Starting point | Best first endpoint |
|---|---|
| You have only a prompt or song idea | Suno Music API |
| You want help writing lyrics first | Suno Lyrics API |
| You already have reference audio | Suno Upload API |
| You want to reuse an existing song structure | Suno Extend API or Suno Cover API |
3. Follow the standard Suno workflow
For most production apps, the flow looks like this:- Optionally create lyrics through the Lyrics API.
- Submit the main generation request through the Music API.
- Track job completion through Fetch V2 or a
hookUrl. - Post-process the result with Extend, Cover, Stems, Full Stems, or WAV export.
4. Know which steps are usually asynchronous
Many Suno integrations are built around background jobs. That means your app often needs to:- Store the returned
jobId - Poll Fetch V2 until the job is finished
- Or receive a webhook callback through
hookUrl
5. Add the most useful follow-up endpoints
Once the first generation flow works, these are usually the next endpoints teams adopt:- Suno Extend API to continue a good song idea
- Suno Cover API to restyle an existing song
- Suno Stems API to split vocals and accompaniment
- Suno Upload API to start from source audio
- Suno WAV API when delivery quality matters
Common integration mistakes
- Starting with the wrong endpoint instead of matching the real source asset
- Treating async jobs as if they return final media immediately
- Forgetting to store
jobIdfor result polling - Using Suno Stems API when you actually need the more detailed Full Stems API
- Skipping pricing review before enabling higher-cost post-processing endpoints