# Common Error Messages

An API call that encounters an error :warning: will return 0 as its `status code` and display the cause of the error under the `result` field.

```json
{
   "status":"0",
   "message":"NOTOK",
   "result":"Max rate limit reached, please use API Key for higher rate limit"
}
```

## Max rate limit <a href="#max-rate-limit" id="max-rate-limit"></a>

> "Max rate limit reached, please use API Key for higher rate limit"

This error occurs when you **exceed the rate limit** assigned to your specific API key.

To resolve, adhere to the [**rate limits**](https://docs.blocksscan.io/support/rate-limits) of your available plan by waiting for a certain amount of time before each request. If you are using a script or application, **apply throttling** to limit the frequency of calls.

## Missing or invalid action <a href="#missing-or-invalid-action" id="missing-or-invalid-action"></a>

> "Error! Missing Or invalid Action name"

This error occurs when you **do not specify**, or specify an **invalid** `module` and `action` name.

To resolve, **double check** your API query to use a valid module and action name.

If you require some help getting started, try copying the sample queries provided in the [**API Endpoints**](https://docs.blocksscan.io/getting-started/endpoint-urls) and pasting them into your browser.

## Endpoint-specific errors <a href="#endpoint-specific-errors" id="endpoint-specific-errors"></a>

> "Error! Block number already pass"
>
> "Error! Invalid address format"
>
> "Contract source code not verified"

These error messages returned are specific to certain endpoints and their **related parameters.**

To resolve, kindly refer to the specific endpoint's documentation, and check for the **correct format** or **values** to be specified as **parameters.**

## **Query Timeout** <a href="#query-timeout" id="query-timeout"></a>

> "Query Timeout occured. Please select a smaller result dataset"

This error occurs when you have sent a particularly large query that did not manage to be completed in time.

To resolve, consider selecting a smaller date/block range, though you may [**ping us**](https://docs.blocksscan.io/support/getting-help) if you think the issue may be performance related.