API Health Check

Monitor Solverify API availability and server uptime with the API Health Check endpoint. The lightweight GET / request confirms that the API server is responding and returns uptime in both human-readable and numeric formats.

Use this endpoint for uptime monitoring, automated availability checks, deployment verification, load-balancer probes, and operational dashboards.

The health check does not require a request body or API key.

Request

GET / HTTP/1.1
Host: solver.solverify.net

Success Response

When the Solverify API server is available, the endpoint returns:

{
  "status": "ok",
  "uptime": "2h30m15s",
  "uptime_seconds": 9015
}

Response Fields

Use status for a simple health assertion and uptime_seconds when your monitoring system needs a numeric value.

Health Check Code Examples

These examples request the Solverify health endpoint and verify that the returned status is ok.

curl --fail --silent --show-error \
  https://solver.solverify.net/

Monitoring Recommendations

For reliable API availability monitoring:

• Set a request timeout so unavailable checks fail quickly.
• Treat connection errors, timeouts, non-success HTTP responses, invalid JSON, or a status other than ok as failed checks.
• Require multiple consecutive failures before alerting to reduce noise from temporary network issues.
• Record uptime_seconds if you need to identify API process restarts.
• Continue handling task-level API errors separately from server availability.

The health check confirms that the API server is responding. It does not create a CAPTCHA task or verify that a specific task can be solved.

For public operational metrics, queue depth, node load, and recent solve activity, visit the Solverify API Status page.

Frequently Asked Questions

Does the API Health Check require authentication?

No. Send a GET request to https://solver.solverify.net/ without a request body or clientKey.

What does status: ok mean?

It means the API server responded successfully to the health request. Task creation and result requests should still implement their own error handling.

What is the difference between uptime and uptime_seconds?

uptime is formatted for people, such as 2h30m15s. uptime_seconds provides the same duration as a number for monitoring and automation.

Does a lower uptime value mean the API is unhealthy?

Not necessarily. A lower value can indicate that the API process restarted. Evaluate it together with the current status and your monitoring history.

Can I use this endpoint with an uptime monitoring service?

Yes. Configure the service to send a GET request, expect a successful HTTP response, and verify that the JSON body contains "status": "ok".