[AI33-4]Find-solution - Get Direction
Get the direction option results for technical solutions
1. Need to call the step 3 submit interface first
2. Status includes: SUCCEED (success), RUNNING (generating), FAILED (failed)
3. When status is SUCCEED, the directions field will contain direction option data
2. Status includes: SUCCEED (success), RUNNING (generating), FAILED (failed)
3. When status is SUCCEED, the directions field will contain direction option data
Request Parameters
List of parameters supported by this API endpoint
| Name | Type | Example | Description |
|---|---|---|---|
Required | string | 80d440b7-80a5-4233-a75f-ab72b0885c88 | Task id |
Response Schema
Structure of the API response data
| Field Name | Type | Example | Description |
|---|---|---|---|
data | object | - | response data |
status | string | SUCCEED | Return status value（SUCCEED,RUNNING,FAILED） |
directions | array | [
{
"reason": "通过高能量密度电极材料升级与电解液优化提升电池能量密度",
"ticked": true,
"approaches": [
"采用单晶高镍NCM811/NCA正极材料配合硅碳复合负极（5-10%硅含量），同时使用高电压添加剂改性电解液，在电池体积不变情况下提升能量密度。"
],
"source_type": "model",
"verification": "实现260Wh/kg能量密度目标，同时控制成本增幅在15%以内，保持电池安全性能。"
},
{
"reason": "通过结构优化与轻量化设计减少非活性材料质量占比",
"ticked": true,
"approaches": [
"优化锂电池极片结构设计，采用双面不等厚度涂布工艺和梯度密实度电极，配合超薄铜箔（6μm）和铝箔（12μm）集流体，减少非活性材料占比。"
],
"source_type": "model",
"verification": "在保持电池体积不变的情况下，提高活性材料占比，实现能量密度提升至260Wh/kg，且与现有产线兼容。"
}
] | Technical direction |
reason | string | 通过高能量密度电极材料升级与电解液优化提升电池能量密度 | Reason or rationale for the technical direction |
ticked | boolean | true | Whether it is selected or ticked |
approaches | array | [
"采用单晶高镍NCM811/NCA正极材料配合硅碳复合负极（5-10%硅含量），同时使用高电压添加剂改性电解液"
] | List of technical approaches or implementation paths |
source_type | string | model | Data source type(model/customize) |
verification | string | 实现260Wh/kg能量密度目标，同时控制成本增幅在15%以内，保持电池安全性能 | Verification description of the technical direction |
statusRequired | boolean | false | Status |
error_msg | string | The request parameter format is incorrect！ | Error Message |
error_codeRequired | integer | 0 | Error Code |
Success Response Example
Example of a successful API response
JSON
{
"data": {
"status": "SUCCEED",
"directions": [
{
"reason": "通过高能量密度电极材料升级与电解液优化提升电池能量密度",
"ticked": true,
"approaches": [
"采用单晶高镍NCM811/NCA正极材料配合硅碳复合负极（5-10%硅含量），同时使用高电压添加剂改性电解液"
],
"source_type": "model",
"verification": "实现260Wh/kg能量密度目标，同时控制成本增幅在15%以内，保持电池安全性能"
}
]
},
"status": true,
"error_code": 0
}Error Codes
List of possible error codes returned by this endpoint
Business Errors
| Error Code | Description |
|---|---|
68300004 | Invalid parameter! |
68300005 | Search api failure! |
68300006 | Analytic basic access error! |
68300007 | Bad request! |
68300008 | Service error, please try again later! |
68300010 | The file does not comply with upload specifications! |
Platform Errors
| Error Code | Description |
|---|---|
67200000 | API call exceeds the total limit set by the platform! |
67200001 | API call exceeds the total limit set by the platform! |
67200002 | The current call rate is too fast, exceeding the current configuration limit QPS! |
67200003 | The key and secret parameters for applying for the token are incorrect or the client has been disabled! |
67200004 | The requested api does not have permission. Please contact our support personnel! |
67200005 | Insufficient account balance/number of calls! |
67200006 | The client has exceeded the activation validity period! |
67200007 | The current call exceeds the configured usage limit of the day! |
67200008 | Please check if the required apikey in the query parameter has been transmitted! |
67200009 | The apikey does not match the passed bearerToken. Please check if a valid token is being used! |
67200012 | The request is illegal! |
67200100 | The current server status is busy, request response timeout! |
67200101 | The API requested currently does not exist. Please check the request path! |
HTTP Status Codes
| Status Code | Description |
|---|---|
0 | Success |
201 | Created |
401 | Unauthorized |
403 | Forbidden |
404 | Not Found |
Performance Metrics
Expected performance characteristics for this endpoint
Normal Response Time
5000 ms
Max Response Time
10000 ms