[AI39-1] Enhanced design infringement risk search-Submit Full FTO Workflow Task
Submit a target image and trigger the full FTO workflow. At least one of url or target_image_base64 must be provided; if both are provided, url takes precedence. task_id is generated automatically by the server and cannot be passed in externally.
Request Parameters
List of parameters supported by this API endpoint
| Name | Type | Example | Description |
|---|---|---|---|
| string | user_123456 | User ID, optional; if not provided, the server will use the context user or generate an anonymous MCP user |
| string | https://example.com/target-image.jpg | Target image URL; at least one of url or target_image_base64 must be provided, url takes precedence when both are given |
| string | iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAQAAAC1HAwCAAAAC0lEQVR42mNkYAAAAAYAAjCB0C8AAAAASUVORK5CYII= | Target image base64 encoding; at least one of url or target_image_base64 must be provided, url takes precedence when both are given |
| string | FTO 图像检索任务-2026-05-22 | Task title |
| array | [
"CN",
"US",
"EU"
] | Country/region code list, e.g. CN, US, JP, KR, AU, EU |
| array | [
{
"id": "09-01",
"desc": "包装容器"
}
] | LOC classification item list |
Required | string | 09-01 | LOC classification code, e.g. 09-01 |
| string | 包装容器 | LOC classification description |
| string | 20200101 | Application start date, format YYYYMMDD |
| string | 20260522 | Application end date, format YYYYMMDD |
| string | 1,2 | Simple legal status filter, comma-separated. 0=Inactive, 1=Active, 2=Pending. Default 1,2; pass 0,1,2 to include inactive patents |
Response Schema
Structure of the API response data
| Field Name | Type | Example | Description |
|---|---|---|---|
messageRequired | string | 任务提交成功 | Submission result message |
successRequired | boolean | true | Whether submission succeeded |
task_id | string | 8f3c1b2a-9d4e-4a7b-bc5e-12345678abcd | Task ID generated automatically by the server; may be empty when submission fails |
Success Response Example
Example of a successful API response
JSON
{
"status": true,
"message": "任务提交成功",
"success": true,
"task_id": "8f3c1b2a-9d4e-4a7b-bc5e-12345678abcd",
"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 |
422 | Validation Error |
Performance Metrics
Expected performance characteristics for this endpoint
Normal Response Time
5000 ms
Max Response Time
10000 ms