manyframeSunoAPI Lyrics.
Develop lyrics as text through the wrapper's dedicated task. Keep the lyrics action separate from music generation and selectable Studio voices.
API access and settings depend on the configured provider. Check the route and billing before submitting.
The route.
The right inputs.
Start from the creative job, then choose the model and settings that fit it.
Model ID suno_lyrics
- Output
- Generated lyrics text
- Task action
- Lyrics, separate from the music action
- Interface boundary
- API task; not a selectable Studio voice
- Access and rights
- Unofficial wrapper; current entitlement and paid-use permissions remain unverified
This page describes the implemented API connector. Confirm your configured provider, account access and request settings before submitting a lyrics task.
Write the intention behind the words.
Give the brief a theme, a point of view and the type of wording the piece needs. Review the returned text for repeated phrases, unintended claims and references that do not belong to your project.
The lyrics action produces text, while the music action requests audio. This route is exposed through the task/API boundary rather than as a Studio voice choice. Confirm account access and the applicable rights before using the text commercially.
Explore the brand-aware writing desk ↗Good questions. Clear answers.
Still curious? Browse all FAQs
Will the lyrics task create a sung audio track?
The lyrics action returns text. Music generation is a separate wrapper task.
Does the wrapper establish official Suno access or commercial permission?
No. The connector is unofficial, and entitlement and paid-use permissions need their own verification.
Keep the text task and its scope clear.
Inspect the developer boundary and verify access before use.