Health Monitoring

Seyaha periodically probes your OCTO endpoint to verify connectivity and authentication. The result is stored in the integration’s health object.

Health states

HEALTHY ──(failures start)──▶ DEGRADED ──(threshold reached)──▶ DOWN
   ▲                               │                                │
   └───────────(recovers)──────────┘◀──────(probe succeeds)────────┘

Status	Meaning	Activity syncs
`HEALTHY`	All recent probes succeeded	Running normally
`DEGRADED`	Some recent probes failed — monitoring closely	Still running
`DOWN`	Consecutive failure threshold exceeded	Paused — activities marked inactive

When an integration recovers from DOWN to HEALTHY, Seyaha automatically triggers a full sync and restores all affected activities to active status.

Checking health status

Partners can query their own integration; admins can query any:

curl "https://api.seyaha.net/api/v1/partner-integrations/$INTEGRATION_ID/health" \
  -H "Authorization: Bearer $PARTNER_JWT"

const res = await fetch(
  `https://api.seyaha.net/api/v1/partner-integrations/${integrationId}/health`,
  { headers: { 'Authorization': `Bearer ${partnerJwt}` } }
);
const { data } = await res.json();
console.log(data.status, data.last_probe_at);

Response:

{
  "success": 1,
  "data": {
    "status": "HEALTHY",
    "last_probe_at": "2026-06-23T08:00:00.000Z"
  }
}

Full health fields (via sync-log or admin list)

The full health object (returned in the complete integration document) includes:

Field	Type	Description
`status`	`HEALTHY \| DEGRADED \| DOWN`	Current state
`last_probe_at`	date	When the last probe ran
`last_success_at`	date	When the last successful probe ran
`consecutive_failures`	integer	Rolling count of failed probes
`degraded_since`	date	When the integration entered DEGRADED
`down_since`	date	When the integration entered DOWN

Troubleshooting

If your integration enters DEGRADED or DOWN:

Check that base_url is reachable from the internet (not just localhost or VPN)
Verify auth_key is still valid and hasn’t expired
Ensure GET {base_url}/products returns a 200 — probe failures on any non-200 response
Call POST /me/test-connection for an on-demand diagnostic

If you update auth_key after a rotation, call PATCH /me to push the new credential:

cURL

curl -X PATCH https://api.seyaha.net/api/v1/partner-integrations/me \
  -H "Authorization: Bearer $PARTNER_JWT" \
  -H "Content-Type: application/json" \
  -d '{ "auth_key": "new_rotated_key" }'

Dashboard Guide

Developer Integration

API Reference

Health Monitoring

Health states

Checking health status

Full health fields (via sync-log or admin list)

Troubleshooting

​Health states

​Checking health status

​Full health fields (via sync-log or admin list)

​Troubleshooting

Health states

Checking health status

Full health fields (via sync-log or admin list)

Troubleshooting