CIECC (Saike Data) Claim Report

Use Cases

Deep verification before used car transaction: apply for a complete claim report before acquisition, replacement, and delivery.
High-risk vehicle review: initiate report applications for high-value, accident-clue, or customer-disputed vehicles.
Risk-control audit trail: retain order number, application status, and report result to form a traceable review record.
Customer delivery and after-sales explanation: use the report for condition disclosure, price communication, and dispute handling.

Endpoint

POST /api/v1/veh-claims/swb

See the cooperation email notification for the endpoint.

Request Parameters

Request headers: Authorization: Bearer <ACCESS_TOKEN>, Content-Type: application/json.

json

{
  "vin":"1HGBH41JXMN00****",
  "authName":"<AUTHORIZER_NAME>",
  "drivingPicUrl":"https://<YOUR_PUBLIC_HOST>/driving-license.jpg",
  "authPdfUrl":"https://<YOUR_PUBLIC_HOST>/authorization.pdf",
  "rightsType":"购买",
  "clientNotifyUrl":"https://<YOUR_PUBLIC_HOST>/callbacks/claim"
}

Field	Type	Required	Description
`vin`	string	Yes	17-character VIN; the service strips spaces and converts to uppercase.
`authName`	string	Yes	Authorizer name, 2 to 50 characters.
`drivingPicUrl`	string	Yes	Public HTTPS URL of the driving license image.
`authPdfUrl`	string	Yes	Public HTTPS URL of the authorization file.
`rightsType`	string	Yes	`购买` (purchase), `受赠` (gift), `继承` (inheritance), or `其他` (other).
`clientNotifyUrl`	string	No	Public HTTPS URL for receiving result notifications, without username, password, or fragment.

The image and PDF URLs must be reachable over public HTTPS and must not point to private networks, reserved addresses, or URLs with credentials. Claim ordering may incur supplier fees; only authorized test materials may be used.

Response Fields

Common Response Fields

Field	Type	Meaning
code	string	Business status code: `0000` accepted / querying, `4001` parameter or file URL error, `5001` service processing failure. Not used when the authentication layer rejects.
message	string	Business processing result description, returned by the service on success, no-data, or failure.
data	object/array/null	Business result. An object or array on success; usually null on no-data or business failure.
request_id	string	Request trace ID for troubleshooting; do not use it as a substitute for a key or token.

`data` Fields

Field	Type	Meaning
orderId	string	Claim report order number; used for subsequent queries and callbacks.
status	string	Order status. The current order response is fixed to `processing`.

Examples

Sample Input and curl

The input below follows the current Swagger defaults. Claim ordering may incur supplier fees and is not a free interface probe; only execute after confirming authorization and accepting the fee.

bash

curl -X POST \
  "https://<API_HOST>/api/v1/veh-claims/swb" \
  -H "Authorization: Bearer <ACCESS_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"vin":"1HGBH41JXMN00****",
  "authName":"水木思源（天津）科技有限公司",
  "drivingPicUrl":"https://<占位示意>.jpg",
  "authPdfUrl":"https://<占位示意>.pdf",
  "rightsType":"购买",
  "clientNotifyUrl":"https://<占位示意>"}'

Success Response

The following is the acceptance-response example based on the default test input; the order number is generated by the service, and the actual value is subject to the interface response.

json

{
  "code":"0000",
  "message":"成功",
  "data":{
    "orderId":"<ORDER_ID>",
    "status":"processing"
  },
  "request_id":"request-id"
}

Immediately and securely store orderId on the client server. Then retrieve the report with orderId using the claim-result retrieval endpoint.

Error Codes

Business Codes & Notes

0000 accepted, 4001 VIN, URL, file, or authorization parameter incorrect, 5001 service processing failure. Authentication-layer errors are handled as 401, 403, 429, 503. Do not automatically retry unknown responses or requests that may already have reached the supplier.

VIN Format Error (HTTP 400)

Request: {"vin":"INVALID","authName":"示例授权人","drivingPicUrl":"https://files.example/driving.jpg","authPdfUrl":"https://files.example/auth.pdf","rightsType":"购买"}

json

{"code":"4001","message":"VIN格式不正确","data":null,"request_id":"request-id"}

Image, Authorization File, or Callback URL Unavailable (HTTP 400)

json

{"code":"4001","message":"图片地址不可用","data":null,"request_id":"request-id"}

json

{"code":"4001","message":"授权文件不可用","data":null,"request_id":"request-id"}

json

{"code":"4001","message":"回调地址不可用","data":null,"request_id":"request-id"}

Service or Order File Unavailable (HTTP 503)

json

{"code":"5001","message":"订单服务暂不可用","data":null,"request_id":"request-id"}

json

{"code":"5001","message":"订单文件服务暂不可用","data":null,"request_id":"request-id"}

Unknown Supplier Response (HTTP 200)

When the request may already have been delivered but the response cannot be confirmed, the service retains the order and returns "querying"; do not automatically re-order:

json

{"code":"0000","message":"查询中","data":{"orderId":"<ORDER_ID>","status":"processing"},"request_id":"request-id"}

Authentication-layer errors are HTTP 401, 403, 429, 503 and do not use the above business codes.

Claim Result Retrieval Endpoint

GET /api/v1/veh-claims/swb/{orderId}

See the cooperation email notification for the endpoint.

When to Call

After receiving the callback notification at the callback URL or if no callback URL is provided, you may actively poll.

Request Parameters

This interface uses a client-level token, the same token-exchange flow as claim ordering. The current order response returns only orderId and status.

http

GET /api/v1/veh-claims/swb/<ORDER_ID>
Authorization: Bearer <ACCESS_TOKEN>
Accept: application/json

The client-level token must belong to the AppKey that created the order, and that AppKey must have the exact-path authorization for /api/v1/veh-claims/swb/{orderId}. The GET request has no JSON body; do not put tokens into URLs, logs, or frontend pages.

Response Fields

Common Response Fields

Field	Type	Meaning
code	string	Business status code: `0000` query success, `4001` request or order number error, `5001` order/service processing failure. Not used when the authentication layer rejects.
message	string	Business processing result description, returned by the service on success, no-data, or failure.
data	object/array/null	Business result. An object or array on success; usually null on no-data or business failure.
request_id	string	Request trace ID for troubleshooting; do not use it as a substitute for a key or token.

`data` Fields

Field	Type	Meaning
orderId	string	Claim report order number.
status	string	Order status: `processing`, `completed`, `failed`.
html	string/null	Report HTML body; may be null while processing or on failure.
htmlurl	string/null	Signed HTTPS link to the report HTML; may be null before completion or on failure.
picUrl	string/null	Signed HTTPS link to the report image; may be null before completion or on failure.

status is an explicitly bounded enum; when it is failed, empty links must not be interpreted as success.

Examples

Sample Input and curl

The query example requires an orderId returned from a successfully placed order; it does not auto-create an order, so it incurs no ordering fee.

bash

curl -X GET \
  "https://<API_HOST>/api/v1/veh-claims/swb/{orderId}" \
  -H "Authorization: Bearer <ACCESS_TOKEN>" \
  -H "Accept: application/json"

Success Response

The following is a status example based on an order number from a successfully placed order; the order number, report body, and links are placeholder values, and the actual result is subject to the interface response.

Processing:

json

{
  "code":"0000",
  "message":"处理中",
  "data":{"orderId":"<ORDER_ID>","status":"processing"},
  "request_id":"request-id"
}

Completed:

json

{
  "code":"0000",
  "message":"完成",
  "data":{
    "orderId":"<ORDER_ID>",
    "status":"completed",
    "html":"<REPORT_HTML_OR_NULL>",
    "htmlurl":"https://<SIGNED_REPORT_URL>",
    "picUrl":"https://<SIGNED_IMAGE_URL>"
  },
  "request_id":"request-id"
}

htmlurl and picUrl are HTTPS signed links valid for about 31 days. When status=failed, treat as failure and do not treat empty links as success.

Error Codes

Business Codes & Notes

0000 means the request succeeded and returned the current status, 4001 means the order number or request is incorrect, 5001 means service processing failure. Missing, expired, or order-unrelated tokens usually return 401 or 403; non-existent or inaccessible orders may also use a generalized error response. When troubleshooting, provide request_id, not the order token.

Order Failed (HTTP 200)

json

{"code":"5001","message":"订单提交失败","data":{"orderId":"<ORDER_ID>","status":"failed","html":null,"htmlurl":null,"picUrl":null},"request_id":"request-id"}

Order Does Not Exist or Does Not Belong to Current Client (HTTP 401)

json

{"code":"authentication_rejected","message":"authentication rejected","request_id":"request-id"}

The service does not leak whether an order exists through error messages; a wrong order number, an order belonging to another client, or a missing/expired token may all present as authentication failure.

Order Service Temporarily Unavailable (HTTP 503)

json

{"code":"service_unavailable","message":"service unavailable","request_id":"request-id"}

Report Still Processing (HTTP 200)

json

{"code":"0000","message":"查询中","data":{"orderId":"<ORDER_ID>","status":"processing","html":null,"htmlurl":null,"picUrl":null},"request_id":"request-id"}

No path permission, rate limiting, and unavailable authentication dependencies are HTTP 403, 429, 503, respectively; the query interface continues to use the client-level token of the order-creating client.

CIECC (Saike Data) Claim Report ​

Use Cases ​

Endpoint ​

Request Parameters ​

Response Fields ​

Common Response Fields ​

data Fields ​

Examples ​

Sample Input and curl ​

Success Response ​

Error Codes ​

Business Codes & Notes ​

VIN Format Error (HTTP 400) ​

Image, Authorization File, or Callback URL Unavailable (HTTP 400) ​

Service or Order File Unavailable (HTTP 503) ​

Unknown Supplier Response (HTTP 200) ​

Claim Result Retrieval Endpoint ​

When to Call ​

Request Parameters ​

Response Fields ​

Common Response Fields ​

data Fields ​

Examples ​

Sample Input and curl ​

Success Response ​

Error Codes ​

Business Codes & Notes ​

Order Failed (HTTP 200) ​

Order Does Not Exist or Does Not Belong to Current Client (HTTP 401) ​

Order Service Temporarily Unavailable (HTTP 503) ​

Report Still Processing (HTTP 200) ​

CIECC (Saike Data) Claim Report

Use Cases

Endpoint

Request Parameters

Response Fields

Common Response Fields

`data` Fields

Examples

Sample Input and curl

Success Response

Error Codes

Business Codes & Notes

VIN Format Error (HTTP 400)

Image, Authorization File, or Callback URL Unavailable (HTTP 400)

Service or Order File Unavailable (HTTP 503)

Unknown Supplier Response (HTTP 200)

Claim Result Retrieval Endpoint

When to Call

Request Parameters

Response Fields

Common Response Fields

`data` Fields

Examples

Sample Input and curl

Success Response

Error Codes

Business Codes & Notes

Order Failed (HTTP 200)

Order Does Not Exist or Does Not Belong to Current Client (HTTP 401)

Order Service Temporarily Unavailable (HTTP 503)

Report Still Processing (HTTP 200)