Health Check

Verify that the API is reachable and fully operational before making conversion requests. No authentication required.

Request

GET/health

No body · No auth

curl https://api.fastpdfhq.com/health

200 Healthy

{
  "status": "healthy",
  "message": "All systems operational",
  "timestamp": "2026-04-05T10:30:00Z"
}

503 Unhealthy

{
  "status": "unhealthy",
  "message": "Service degraded",
  "timestamp": "2026-04-05T10:30:00Z"
}

status

healthy when all systems are operational. unhealthy when the API cannot process conversion requests.

message

Human-readable summary of the current service state.

timestamp

ISO 8601 UTC time of the health check. Useful for detecting stale cached responses.

1Uptime monitors. Point your monitoring service at /health to get alerted as soon as the API becomes unreachable, without consuming your conversion quota.
2Load balancer probes. Configure your load balancer health check to use GET /health. A 503 response automatically removes the node from rotation.
3CI / pre-flight checks. Verify the API is reachable at the start of your pipeline before running integration tests that depend on PDF conversion.

lightbulb

The health endpoint is public — no X-API-Key header is required. It does not count against your monthly conversion quota or rate limit.