Skip to content

Insurance Region (VIN) Query ​

Use Cases ​

  • Used car valuation and condition verification: judge vehicle usage years and information consistency by combining first registration date and insurance time.
  • Insurance underwriting and renewal: assess underwriting, renewal, and client-reach opportunities based on insured region and latest insurance month.
  • Vehicle regional risk analysis: analyze vehicle distribution, accident risk, and insurance demand across provinces, cities, and districts.
  • Owner operations and marketing: conduct reminders, quoting, and value-added service recommendations for clients nearing renewal.
  • Vehicle finance and risk-control review: assist in confirming base vehicle information and insurance coverage continuity.
  • Sales flow analysis: OEM sales flow analysis.

Endpoint ​

POST /api/v1/getVehInsuranceRegion

See the cooperation email notification for the endpoint.

Request Parameters ​

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

json
{"vin":"1HGBH41JXMN000001"}

The request body only allows vin, which must be a 17-character VIN; do not mix in a license plate or other fields.

Response Fields ​

Common Response Fields ​

FieldTypeMeaning
codestringBusiness status code: 0000 success, 0001 no data, 4001 parameter format error, 5001 service processing failure, 5002 supplier token acquisition failure. Not used when the authentication layer rejects.
messagestringBusiness processing result description, returned by the service on success, no-data, or failure.
dataobject/array/nullBusiness result. An object or array on success; usually null on no-data or business failure.
request_idstringRequest trace ID for troubleshooting; do not use it as a substitute for a key or token.

data[] Fields ​

FieldTypeMeaning
provincestring/nullProvince of the insurance.
citystring/nullCity of the insurance.
countystring/nullDistrict/county of the insurance.
insuranceMonthstring/nullLatest insurance year-month; usually YYYY-MM, subject to the actual value.
vinstring/nullVIN of the associated vehicle.
registerDatestring/nullVehicle registration / first registration date; format from upstream.

data is an array; it is null when there is no matching data. Missing business fields in a single record return null; the response does not include the license plate.

Examples ​

Free Test Case ​

Uses the current Swagger default input: vin=1HGBH41JXMN000001.

bash
curl -X POST \
  "https://<API_HOST>/api/v1/getVehInsuranceRegion" \
  -H "Authorization: Bearer <ACCESS_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"vin":"1HGBH41JXMN000001"}'

Success Response ​

The following is the field-structure example based on the default test input; region, month, and date are for illustration only, and the actual result is subject to the interface response.

json
{
  "code":"0000",
  "message":"成功",
  "data":[{
    "province":"江苏省",
    "city":"南京市",
    "county":"鼓楼区",
    "insuranceMonth":"2026-06",
    "vin":"1HGBH41JXMN00****",
    "registerDate":"2020-01-01"
  }],
  "request_id":"request-id"
}

Fields may be null.

Error Codes ​

VIN Format Error (HTTP 400) ​

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

No Data (HTTP 200) ​

json
{"code":"0001","message":"查无数据","data":null,"request_id":"request-id"}

Supplier Format Error or Vehicle Mismatch (HTTP 200) ​

json
{"code":"5001","message":"供应商返回格式不正确","data":null,"request_id":"request-id"}
json
{"code":"5001","message":"供应商返回车辆与查询条件不匹配","data":null,"request_id":"request-id"}

Token or Service Failure (HTTP 200) ​

json
{"code":"5002","message":"供应商Token获取失败","data":null,"request_id":"request-id"}
json
{"code":"5001","message":"供应商接口调用失败","data":null,"request_id":"request-id"}

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