# Error

> The scan ended with an error.

The `error` event happens as soon as the scan process reaches an end due to an error.

<ParamField path="status" type="integer">
  The current status of the scan. Possible values: 0 (Success), 1 (Error), 2 (CreditsChecked), 3 (Indexed)
</ParamField>
<ParamField path="error" type="object">
  <Expandable title="properties">
    <ParamField path="type" type="string">
      The error type (e.g., `authentication_error`, `payment_error`, `invalid_request_error`, `api_error`).
    </ParamField>
    <ParamField path="id" type="string">
      The machine-readable error identifier (e.g., `invalid_credentials`, `insufficient_credits`).
    </ParamField>
    <ParamField path="code" type="integer">
      Error code that represents the reason for failure. See below the full error table.
    </ParamField>
    <ParamField path="message" type="string">
      Human-readable error message that describes the reason for failure.
    </ParamField>
    <ParamField path="url" type="string">
      A URL to the documentation page for this error.
    </ParamField>
    <ParamField path="details" type="array">
      Additional details about specific parameters that caused the error.
      <Expandable title="properties">
        <ParamField path="param" type="string">
          The parameter name that caused the error.
        </ParamField>
        <ParamField path="message" type="string">
          A message describing the issue with this parameter.
        </ParamField>
      </Expandable>
    </ParamField>
  </Expandable>
</ParamField>
<ParamField path="developerPayload" type="string">
  The developer payload that was provided in the submit method.

      `<= 512` characters
</ParamField>
Copyleaks provides you with the specific error message describing the reason for the error. Some of the failures are related to incorrect configuration on your side. Others are related to Copyleaks server-side errors.

We are doing our best to successfully respond to all of your requests.

Still, sometimes we encounter an internal error. In that case, we will fix the problem as soon as possible. You will also get a unique ticket ID that will help identify the problem when contacting Copyleaks customer support.

For a complete reference of all the error codes and how to handle them, see [API Errors](/using-the-apis/api-errors).

## Example

```json
{
  "status": 1,
  "error": {
    "type": "invalid_request_error",
    "id": "missing_parameter",
    "code": 1,
    "message": "Bad request. One or several required parameters are missing or incorrect."
  },
  "developerPayload": "Custom developer payload"
}
```

## Next Steps

<CardGroup cols={2}>
  <Card title="Error Codes" icon="triangle-exclamation" href="/using-the-apis/api-errors">Complete reference of all API error codes and how to resolve them.</Card>
  <Card title="Webhooks Overview" icon="plug" href="/reference/data-types/authenticity/webhooks/overview/">Learn about the different types of webhooks and how to handle them.</Card>
  <Card title="Handling Failures" icon="triangle-exclamation" href="/concepts/performance/handling-failures/">Understand how to implement an exponential backoff strategy for retrying requests.</Card>
  <Card title="Scan Alerts" icon="bell" href="/reference/data-types/authenticity/scan-alerts/">Explore the full list of scan alerts and their meanings.</Card>
</CardGroup>