Skip to main content
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)────────┘
StatusMeaningActivity syncs
HEALTHYAll recent probes succeededRunning normally
DEGRADEDSome recent probes failed — monitoring closelyStill running
DOWNConsecutive failure threshold exceededPaused — 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"
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:
FieldTypeDescription
statusHEALTHY | DEGRADED | DOWNCurrent state
last_probe_atdateWhen the last probe ran
last_success_atdateWhen the last successful probe ran
consecutive_failuresintegerRolling count of failed probes
degraded_sincedateWhen the integration entered DEGRADED
down_sincedateWhen the integration entered DOWN

​
Troubleshooting

If your integration enters DEGRADED or DOWN:
  1. Check that base_url is reachable from the internet (not just localhost or VPN)
  2. Verify auth_key is still valid and hasn’t expired
  3. Ensure GET {base_url}/products returns a 200 — probe failures on any non-200 response
  4. 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" }'