
GET
Verify that the API is operational and identify which server region is handling your requests. This is the only /healthGET endpoint — no request body is needed.
Quick Start
Response
| Field | Type | Description |
|---|---|---|
status | string | Current service status. See Status Values below |
version | string | API version (SemVer format) |
region | string | Server region handling the request. See Regions below |
timestamp | number | Server timestamp in milliseconds (Unix epoch) |
Status Values
| Status | Description |
|---|---|
operational | All systems functioning normally |
degraded | Service partially affected — requests may be slower or fail intermittently |
maintenance | Scheduled maintenance in progress — requests may be rejected |
Regions
The API runs across multiple regions. The response tells you which server handled your request.| Code | Location |
|---|---|
ams | Amsterdam |
fra | Frankfurt |
ewr | New York |
lax | Los Angeles |
nrt | Tokyo |
sin | Singapore |
Your region matters when using Initialize Wallets. Initialization is region-specific — if your region changes, re-initialize your wallets.
Use Cases
| Scenario | What to check |
|---|---|
| Pre-flight check | Confirm status is operational before sending transactions |
| Uptime monitoring | Poll periodically and alert when status changes |
| Region verification | Check region to ensure requests hit the expected server |
| Debug & support | Include version and region when reporting issues |
Errors
| Code | Message | Cause |
|---|---|---|
UNAUTHORIZED | Invalid or missing API key | API key is missing or invalid |
SERVICE_UNAVAILABLE | Service temporarily unavailable | The API is down or unreachable |
Notes
- This is the only
GETendpoint — no request body is needed - No fees are charged for health check requests
What’s Next?
Token Info
List token accounts and check balances
Initialize Wallets
Prepare wallets for optimal trading speed
Best Practices
Tips for reliable API integration
Check Balance
Verify SOL and token balances