Health Check
Core Endpoints
Health Check
Check the API status and network availability
GET
Health Check
Overview
V2 Available: An enhanced version is available at
/{network}/v2/healthcheck with metadata and API version tracking. See Health Check V2 and the V2 Migration Guide.Supported Networks
- Base
- HyperEVM
- Citrea
- Monad
- Starknet
Response
number
HTTP status code (200 = healthy)
string
Health status message indicating the API is operational
Example Request
Example Response
Use Cases
Monitoring
Monitor API availability in your application dashboard
Fallback Logic
Implement fallback to alternative networks if one is down
Load Balancing
Route traffic based on network latency
Debugging
Verify API connectivity when troubleshooting
Implementation Example
Status Page
For real-time status updates and historical uptime data, visit our status page: https://status.fibrous.financeBest Practices
-
Periodic Checks
- Check health before critical operations
- Implement periodic health checks (every 30-60 seconds)
- Cache health status with appropriate TTL
-
Timeout Handling
- Set reasonable timeout for health checks (2-5 seconds)
- Treat timeouts as unhealthy status
- Implement exponential backoff for retries
-
Graceful Degradation
- Have fallback networks configured
- Show user-friendly messages during downtime
- Queue operations when possible
-
Monitoring Integration
Related Resources
- API Status Page
- Rate Limits
- Support
- Health Check V2 - Enhanced health check with metadata
- V2 Migration Guide - Migrate to V2 API