Suno’s API account portal is platform.suno.com. Suno presents it as a place to manage a Suno API account, but the public material reviewed here does not provide a complete integration contract or a runnable generation example. The separate gcui-art/suno-api project is an unofficial wrapper; its cookie instructions and routes are not Suno’s official API specification. (platform.suno.com)
Choose the documentation for the API you intend to call
| Intended path | Documentation | What it establishes |
|---|---|---|
| Suno’s own API | Suno Platform | An API account portal. The material reviewed here does not establish the generation endpoint, authentication contract, request fields, or result flow. (platform.suno.com) |
| Self-hosted third-party wrapper | gcui-art project guide and wrapper API docs | Wrapper-specific setup and route inventory. Its online test is described as a demo bound to a test account, not a production service. (suno.gcui.ai) |
These are distinct integrations. Do not assume that a wrapper cookie works with Suno’s API account portal, or that a credential for Suno’s portal works with the wrapper.
Wrapper setup: configure credentials and run the smoke test
The steps below apply only to the gcui-art wrapper. Its project guide describes copying a session cookie from the browser’s Network tools and configuring it as SUNO_COOKIE. The older supplied guide says to visit app.suno.ai, refresh, find a request containing client?_clerk_js_version, and copy the Cookie value from the request headers. The project’s current GitHub README describes a different page and request keyword: suno.com/create and ?__clerk_api_version. Because these instructions differ, confirm the current project guidance and whether the procedure still works before relying on it. This is not official Suno API authentication. (suno.gcui.ai)
For a local install, the wrapper guide gives these commands:
git clone https://github.com/gcui-art/suno-api.git
cd suno-api
npm install
Add the wrapper setting to a local .env file:
SUNO_COOKIE=<your-cookie>
Then start the development server and visit the quota route:
npm run dev
http://localhost:3000/api/get_limit
The guide shows this sample response:
{
"credits_left": 50,
"period": "day",
"monthly_limit": 50,
"monthly_usage": 50
}
Those are example values, not a guaranteed quota. A response from /api/get_limit is a smoke test for that route; it does not demonstrate that music generation or audio retrieval works. The guide also describes setting SUNO_COOKIE in Vercel and testing /api/get_limit on the deployed domain. (suno.gcui.ai)
Wrapper routes: methods are listed, but generation flow remains incomplete
The wrapper’s API docs label these methods and routes: (suno.gcui.ai)
POST /api/generate— generate music.POST /v1/chat/completions— generate music using a format the project describes as compatible with OpenAI’s API.POST /api/custom_generate— Custom Mode generation.POST /api/generate_lyrics— generate lyrics.POST /api/extend_audio— extend audio.GET /api/get— retrieve audio information; the overview says IDs can be supplied to look up specific items.GET /api/get_limit— retrieve quota information.
The available documentation excerpts do not establish a complete, reproducible music-generation request and result flow. In particular, they do not establish the required generation fields and authentication headers for a working call, the response’s identifier fields, how to retrieve the completed audio, or the documented completion and error behavior. Do not treat the quota smoke test as a generation example or fill in these missing details by guesswork. The docs page offers further parameters and an online demo, but cautions that the demo uses a test account and should not be used frequently. (suno.gcui.ai)
What to verify before building for production
- Confirm the provider and its contract. For Suno’s own API, use the account portal and documentation available to your account; the public material reviewed here does not establish a runnable generation contract. For the wrapper, verify its current request fields, credentials, response, result retrieval, and failure behavior in the wrapper docs.
- Assess the wrapper separately. Its setup relies on a browser session cookie, and the reviewed material does not establish cookie expiry, rotation, revocation, or production security requirements. Its sample quota values are not a service commitment. (
suno.gcui.ai) - Check access conditions and costs. The reviewed portal and wrapper material does not establish API pricing, rate limits, reliability commitments, or commercial-use terms. Confirm these with the provider before estimating production costs or shipping a paid feature.
TokenForge relevance: Token Forge Cloud’s public product description lists production APIs for Qwen, DeepSeek, GLM, and Seedance; it does not identify a Suno or music-generation API. On the public documentation reviewed here, I cannot recommend Token Forge Cloud as the integration path for Suno music generation. That assessment could change if TokenForge documents a music-generation model, its access requirements, and a complete request-and-result contract. (tokenforgecloud.com)