- Print
- PDF
CLOVA Studio overview
- Print
- PDF
The latest service changes have not yet been reflected in this content. We will update the content as soon as possible. Please refer to the Korean version for information on the latest updates.
Available in Classic and VPC
This is a service from NAVER Cloud Platform using HyperCLOVA language model, which is a hyperscale AI technology, to output a phrase created through AI technology in accordance with the input of a user.
Operation
Within CLOVA Studio, the operations available are as follows:
API | Description |
---|---|
Chat Completions | Create conversational sentences utilizing HyperCLOVA X model |
Completions | Create sentences |
Generate training | Generate training using user's dataset |
View training | View information on a single generated training |
View training list | View a list of generated trainings |
Training model chat completions | Create conversational sentences using the training model |
Generate skill set answers | Generate answers through skill set API call |
Specifications related to the explorer related API provided by CLOVA Studio can be viewed on CLOVA Studio website.
Common settings
Describes formats and settings that are commonly used in CLOVA Studio API.
Create test app
Creating a test app enables the use of the API.
Requests
Describes the common request format used in CLOVA Studio API.
API URL
The request API URL is as follows:
https://clovastudio.apigw.ntruss.com/
If you wish to use streaming responses in Chat competition, a separate API URL is required. Please refer to the following information:
Responses
Describes the common response format used by CLOVA Studio API and provides syntax examples.
Body
The following describes the body.
Field | Type | Required | Description |
---|---|---|---|
status | object | N | Response status |
status.code | string | N | Response status code |
status.message | string | N | Response message |
result | any | Y | Response result |
Response status code
Describes response status code.
HTTP status code | Code | Messages | Description |
---|---|---|---|
200 | 20000 | OK | Request handling successful |
204 | 20400 | No content | Request processed successfully, no content returned |
400 | 40000 | Bad request | Invalid request |
400 | 40001 | Invalid parameter | Invalid request parameters |
400 | 40003 | Text to long | Requests made with text that is too long |
400 | 40004 | Text empty | Requests made with empty content |
400 | 40005 | Unavailable output 1 | Requests with unavailable output |
400 | 40006 | Unavailable output 2 | Requests with unavailable output |
400 | 40009 | Unsupported function | Requests for a function that is not supported |
400 | 40010 | input_text_empty | Skill: request parameters for query, thought, action, actionInput, and observe with empty content |
400 | 40020 | missing_input_value | Skill: some of the input values are missing |
400 | 40030 | invalid Action | Skill: enter undefined action |
400 | 40040 | invalid Action Input | Skill: incorrect input for actionInput |
400 | 40050 | internal parsing error | Skill: issue while parsing internally |
400 | 40080 | model not found | Could not locate the model |
401 | 40100 | Unauthorized | Authentication failed |
401 | 40101 | Invalid signature | Invalid request signature |
401 | 40102 | Invalid access token | Access token expired |
401 | 40103 | Access token expired | The task was refused by the server |
401 | 40104 | Invalid key | Invalid authentication key |
401 | 40170 | No subscription request history found. Please request a subscription to use | Cannot find any record of subscription to CLOVA Studio |
403 | 40300 | Forbidden | The task was refused by the server |
403 | 40301 | No ownership | No ownership |
404 | 40400 | Not found | The requested resource not found |
406 | 40600 | Not Acceptable | Media type not acceptable |
408 | 40800 | Request timeout | Request processing timeout |
415 | 41500 | MediaType error | Media type not supported |
415 | 41501 | No multipart boundary Content-Type | Request lacks the required format for multipart usage |
429 | 42900 | Too many requests | Too many requests |
500 | 50000 | Internal server error | Internal server error |
500 | 50010 | no final answer | Skill: missing final_answer when calling API |
500 | 51010 | There is no tool available for planning. | Skill: no tool available for planning |
500 | 51020 | An unknown error occurred during planning. {reason} | Skill: unknown error occurred during planning |
500 | 51030 | Planning is not possible for the given query. The reason is as follows: {reason} | Skill: planning task rejected |
500 | 52020 | Error in creating json. Unable to respond. | Skill: error in json parsing when LLM determines the result in the discriminator |
500 | 52030 | Incorrect creation of skillSet. Unable to respond. | Skill: when the skillSet created by the discriminator does not exist in the entered skillSet |
500 | 53010 | Failed in parsing the search API. | Skill: error occurred during preprocessing of search API results |
500 | 53020 | Unable to summarize due to short original text length. | Skill: error occurs when the original text is less than 100 characters based on char_size |
500 | 60000 | HyperCLOVA API Error url:{url} | Skill: HyperCLOVA related error |
500 | 64000 | {HyperCLOVA error message} | Skill: HyperCLOVA input-related error (text too long, etc.) |
500 | 64240 | {HyperCLOVA error message} | Skill: HyperCLOVA creation-related error (lora url issues, etc.) |
500 | 64290 | {HyperCLOVA error message} | Skill: HyperCLOVA too many requests error |
500 | 65000 | {HyperCLOVA error message} | Skill: HyperCLOVA internal server error |
501 | 50100 | Not yet implemented | Call for an unimplemented API |
504 | 50400 | Gateway timeout | Gateway processing timeout |
For status codes not listed above, see NAVER integration API provided by NAVER Cloud Platform.
Syntax
These are examples of common response syntax.
- Succeeded
{ "status": { "code": "20000", "message": "OK" }, "result": {} }
- Failed (client error)
{ "status": { "code": "40102", "message": "Invalid access token" } }
- Failed (server error)
{ "status": { "code": "50000", "message": "Internal Server Error" } }