Common Error Codes

Reference for Clore.ai API error codes and how to handle them.

Response Code Structure

Every API response includes a code field:

{
  "code": 0,
  "data": {...}
}
{
  "code": 6,
  "error": "not_enough_balance"
}

Error Codes

Code
Meaning
HTTP Status

0

Success

200

1

Database error

500

2

Invalid input

400

3

Invalid/missing API key

401

4

Invalid endpoint

404

5

Rate limit exceeded

429

6

See error field

varies

Common Error Messages (Code 6)

Order Creation Errors

Error
Meaning
Solution

server-dont-exist

Server ID not found

Check marketplace for valid IDs

server-offline

Server is offline

Choose different server

server-already-rented

Server has active rental

Wait or choose another

not_enough_balance

Insufficient funds

Top up wallet

cant_rent_from_yourself

Can't rent own server

Use different account

too_low_price

Spot bid below minimum

Increase bid price

you_already_have_spot_order

Duplicate spot order

Cancel existing first

currency-not-allowed

Server doesn't accept currency

Use different currency

machine-is-on-gigaspot

Server in gigaspot mode

Use gigaspot API

Order Management Errors

Error
Meaning
Solution

you_dont_own_this_order

Order not yours

Check order ID

order_not_active

Order already ended

No action needed

issue_description_too_long

Issue text > 2048 chars

Shorten description

Spot Price Errors

Error
Meaning
Solution

order_dont_exist

Order not found

Verify order ID

amount_too_low

Price below minimum

Increase price

can_lower_every_600_seconds

Rate limited

Wait before lowering

exceeded_max_step

Price decrease too large

Use smaller decrement

Server Settings Errors

Error
Meaning
Solution

server_dont_exist

Server not found

Check server name

not_all_parameters_present

Missing required fields

Check documentation

invalid_mrl

Invalid max rental length

Use valid range

invalid_input

Parameter validation failed

Check parameter values

Handling Errors in Python

Rate Limit Handling

The API allows 1 request per second. Implement proper rate limiting:

Debugging Tips

  1. Check the error field - Code 6 always includes an error field with details

  2. Validate input - Code 2 means your request data is malformed

  3. Check API key - Code 3 means authentication failed

  4. Slow down - Code 5 means you're hitting rate limits

  5. Check server status - Some errors indicate server-side issues (try again later)

See Also

Last updated

Was this helpful?