Skip to main content

​
Telemetry and Health

NexaLayer does more than return a proxy address. It accepts execution outcomes from your automation so it can score session health and recommend when to rotate or pause.

​
Report an event

curl -X POST "https://api.nexalayer.net/v1/sessions/$SID/report-event" \
  -H "Content-Type: application/json" \
  -H "X-API-Key: $NEXALAYER_API_KEY" \
  -d '{
    "event_type": "http_error",
    "status_code": 403,
    "target_host": "example.com",
    "latency_ms": 1800
  }'

​
event_type

TypeMeaning
successRequest or page task succeeded
http_errorHTTP error
captchaCAPTCHA encountered
timeoutRequest or page load timed out
blockClear anti-bot or access block
rate_limit429 or rate limit
customApplication-specific event

​
Read health

curl "https://api.nexalayer.net/v1/sessions/$SID/health" \
  -H "X-API-Key: $NEXALAYER_API_KEY"
Response fields:
FieldMeaning
health_score0-100 score
risk_levellow, medium, or high
success_rateSuccess ratio
consecutive_failuresConsecutive failure count
recommendationok, consider_rotate, rotate_now, or pause
timeout, captcha, and block are not neutral noise. They should influence risk and recovery decisions.