Check a saved proxy
Check a saved proxy accessible to the current user and team. Supports custom, api, integ, and syt modes, and updates the proxy status and checked_at fields. Concurrent checks of the same proxy share one task. For API proxies, the current endpoint is first checked using auth_type. If it fails, the extraction URL is requested again; a new endpoint is saved if needed before retrying the check. Connection and extraction failures are both returned as normal check results with status=unavailable.
Request parameters
Authorization Bearer Token
Include your API Key as a Bearer token in the Authorization request header.
Authorization: Bearer <api-key>Path parameters
1"proxy_01JABCDEF1234567890"minLength: 1Request code examples
JavaScript / TypeScript: Node.js 18+ with fetch; PHP: cURL extension; Go: 1.16+; Java: JDK 11+. Replace the token and example parameter values before running.
curl -X POST -H 'Authorization: Bearer <TOKEN>' 'http://local.zhongyibrowser.com:39025/api/v1/proxies/proxy_01JABCDEF1234567890/check'Responses
Success: code = 0. Failure: code > 0. Select a status to view its fields and example. Expand objects to inspect nested fields. Optional fields may be omitted.
Saved proxy check result
Body
application/jsonProxySavedCheckSuccessResponseobjectrequiredEndpoint business dataAdditional fields are not allowed.
Additional fields are not allowed.
Generated from the schema; not a live response.
{
"code": 0,
"message": "success",
"data": {
"proxy_id": "proxy_01JABCDEF1234567890",
"mode": "custom",
"status": "available",
"endpoint": {
"protocol": "http",
"ip_protocol": "ipv4",
"host": "string",
"port": 0
},
"checked_at": "2024-01-15T09:30:00Z",
"latency_ms": 0
}
}