QuickNode now provides Logs for your RPC endpoints. Easily identify and resolve issues by viewing detailed error information directly from your dashboard.
HTTP Error Codes
Let's look at the common HTTP errors you can encounter, what they mean and what you can do to prevent them.
400
Bad Request
Incorrect HTTP Request type (e.g. using GET instead of POST) or Invalid Characters
401
Unauthorized
This can happen when one or multiple security requirements are not met such as incorrect Token Auth, IP not in the whitelist, invalid JWT, etc.
403
Forbidden
Endpoint Disabled (One of the reasons for this could be a past due payment)
403
Forbidden - custom trace not found
Custom trace code not whitelisted (Submit a ticket to go through the approval process)
404
Not Found
Incorrect URL or Incorrect method
413
Content Too Large
Body of the request is too large
413
Request Entity Too Large
eth_getLogs and eth_newFilter are limited to a 10,000 blocks range. We enforce a limit of 10,000 block ranges when requesting logs and events.
429
Too Many Requests
The requests per second (RPS) of your requests are higher than your plan allows. Learn more about the 429 errors in our support documentation.
500
Internal Server Error
Submit a ticket for the support team to take a look at the errors asap
503
Service Unavailable
Submit a ticket for the support team to take a look at the errors asap
HTTP Error Code Example
The code snippet below is an example of Error Code 429.
{
"jsonrpc": "2.0",
"error": {
"code": 429,
"message": "The requests per second (RPS) of your requests are higher than your plan allows."
},
"id": 1
}
Starknet RPC Error Codes
When working with Starknet, understanding its API error codes is essential for effective troubleshooting and smooth application operation.
1
Failed to receive transaction
Sequencer rejected the transaction during validation. Verify transaction format and required fields
10
No trace available
Trace data not available for the transaction. Verify the transaction hash is correct and exists on the network
20
Contract not found
The specified contract address does not exist on the network
21
Invalid message selector
Function selector does not exist in the contract ABI
22
Invalid call data
Calldata is malformed or contains invalid parameters. Verify parameter types and encoding
24
Block not found
The requested block does not exist. Check block number/hash or wait for sync
26
Invalid block hash
Block hash format is invalid. Ensure it's a valid hexadecimal string with correct length
27
Invalid transaction index
Transaction index is out of range for this block
28
Class hash not found
The specified class hash has not been declared on the network
29
Transaction hash not found
No transaction found with the provided hash
31
Page size too big
Page size exceeds the maximum allowed limit.
32
No blocks
No blocks available in the specified range
33
Invalid continuation token
The continuation token is invalid or has expired
34
Too many keys in filter
Filter contains more keys than the maximum allowed
40
Contract error
An error occurred during contract execution
41
Transaction execution error
Transaction failed to execute. Check contract logic and resource limits
51
Class already declared
Class already exists on the network. Duplicate declarations are not allowed
52
Invalid transaction nonce
Invalid nonce for the account. Use the correct sequential nonce value
53
Insufficient max fee
Max fee too low. Increase the fee to cover transaction costs
54
Insufficient account balance
Account balance too low. Ensure sufficient funds to cover the transaction fee
55
Validation failure
Account validation failed. Check your signature and account contract logic
56
Compilation failed
Contract compilation failed. Fix Cairo code syntax and compilation errors
57
Contract class size is too large
Contract class too large. Reduce the contract size to fit within network limits
58
Non account
Sender is not an account contract. Only account contracts can send transactions
59
Duplicate transaction
Transaction already exists in mempool. Avoid submitting duplicate transactions
60
Compiled class hash mismatch
The compiled class hash does not match the declared hash
61
Unsupported transaction version
Transaction version not supported. Use a compatible transaction version
62
Unsupported contract class version
Contract class version not supported. Use a compatible Cairo compiler version
63
Unexpected error
Unexpected server error occurred. Submit a ticket if the issue persists
Starknet RPC Error Code Example
The code snippet below is an example of Error Code 20.
{
"error": {
"code": 20,
"message": "Contract not found"
},
"id": 1,
"jsonrpc": "2.0"
}
If you're experiencing other error codes, please let us know by submitting a ticket. We're more than happy to assist