Documentation Index
Fetch the complete documentation index at: https://docs.apikley.ru/llms.txt
Use this file to discover all available pages before exploring further.
Boost Music Style
This is an exclusive capability of V4_5. The style functionality of V4_5 has been significantly enhanced, as stated on the official website:
One of the many advantages of the new 4.5 model is its ability to accommodate more detailed style instructions. In previous models, it was necessary to prioritize specific genre and style details, but now instructions can incorporate a more conversational prompt.
Previously, optimal results might have been achieved with a prompt like: ‘deep house, emotional, melodic.’
Now, you can provide a prompt such as: ‘Create a melodic, emotional deep house song featuring organic textures and hypnotic rhythms. Begin with soft ambient layers, natural sounds, and a deep, steady groove. Gradually build with flowing melodic synths, warm basslines, and intricate, subtle percussion.’
The ‘Boost Your Style’ feature will significantly enhance users’ ability to describe and control style. It is recommended for use.
Parameter Description
- content: Required, string type. Style description is required.
Rate limits and quotas are enforced by Apikley and may differ from upstream providers.
OpenAPI
suno-api/suno-api.json post /api/v1/style/generate
openapi: 3.0.0
info:
title: Suno API
description: Apikley Suno API Documentation
version: 1.0.0
contact:
name: Technical Support
email: support@apikley.ru
servers:
- url: https://api.apikley.ru
description: API Server
security:
- BearerAuth: []
paths:
/api/v1/style/generate:
post:
summary: Boost Music Style
operationId: boost-music-style
requestBody:
required: true
content:
application/json:
schema:
type: object
required:
- content
properties:
content:
type: string
description: >-
Style description. Please describe in concise and clear
language the music style you expect to generate. Example:
'Pop, Mysterious'
example: Pop, Mysterious
responses:
'200':
description: Request successful
content:
application/json:
schema:
allOf:
- type: object
properties:
code:
type: integer
enum:
- 200
- 401
- 402
- 404
- 409
- 422
- 429
- 451
- 455
- 500
description: >-
Response status code
- **200**: Success - Request has been processed
successfully
- **401**: Unauthorized - Authentication credentials
are missing or invalid
- **402**: Insufficient Credits - Account does not
have enough credits to perform the operation
- **404**: Not Found - The requested resource or
endpoint does not exist
- **409**: Conflict - WAV record already exists
- **422**: Validation Error - The request parameters
failed validation checks
- **429**: Rate Limited - Request limit has been
exceeded for this resource
- **451**: Unauthorized - Failed to fetch the image.
Kindly verify any access limits set by you or your
service provider.
- **455**: Service Unavailable - System is currently
undergoing maintenance
- **500**: Server Error - An unexpected error occurred
while processing the request
msg:
type: string
description: Error message when code != 200
example: success
- type: object
properties:
data:
type: object
properties:
taskId:
type: string
description: Task ID
param:
type: string
description: Request parameters
result:
type: string
description: The final generated music style text result.
creditsConsumed:
type: number
description: >-
Credits consumed, up to 5 digits, up to 2 decimal
places
creditsRemaining:
type: number
description: Credits remaining after this task
successFlag:
type: string
description: 'Execution result: 0-pending, 1-success, 2-failed'
errorCode:
type: integer
format: int32
description: >-
Error code
- **400**: Validation Error - Failed, The request
parameters failed validation checks.
enum:
- 400
errorMessage:
type: string
description: Error message
example: ''
createTime:
type: string
description: Creation time
'500':
$ref: '#/components/responses/Error'
components:
responses:
Error:
description: Server Error
securitySchemes:
BearerAuth:
type: http
scheme: bearer
bearerFormat: API Key
description: >-
All APIs require authentication via Bearer Token.
Get API Key:
1. Visit [API Key Management Page](https://app.apikley.ru/keys) to get your
API Key
Usage:
Add to request header:
Authorization: Bearer APIKLEY_API_KEY
Note:
- Keep your API Key secure and do not share it with others
- If you suspect your API Key has been compromised, reset it immediately
in the management page
To find navigation and other pages in this documentation, fetch the llms.txt file at: https://docs.apikley.ru/llms.txt
