# Download prevention alerts

The report offering detailed information on prevention alerts. It provides insights into each alert, including unique identifiers, alert types, amounts, outcomes, and the alert generation timeline.
The report unloads data based on the date range parameters that corresponds to the date the operation was executed.In a successful response, you will be redirected to S3 to download the file.

Endpoint: GET /prevention_alerts/report/{report_id}/download
Version: 1.0.0
Security: merchant, signature

## Security:

  - `merchant` (unknown)
    apiKey in header merchant

  - `signature` (unknown)
    apiKey in header signature

## Path parameters:

  - `report_id` (string, required)
    Unique report identifier for download.

<blockquote>
  <p>It follows the pattern [report_prefix] [date (yyMMdd)] [time (HHmmss)] [channel name].</p>
</blockquote>

## Header parameters:

  - `merchant` (string, required)

  - `signature` (string, required)

## Response 200:

  - `200` (unknown)
    `200` responses always indicate an error object. Successful downloads never return `200`. They redirect to S3 with `302` instead. Poll this endpoint and expect `204` until you receive the `302` redirect.

## Response 200 fields (application/json):

  - `error` (object, required)
    Error object.

  - `error.code` (string, required)
    Unauthorized access due to invalid credentials.
    Example: 1.01

  - `error.messages` (array, required)
    Array of error messages applied to the decline payment.

## Response 204:

  - `204` (unknown)
    Report is not ready

## Response 302:

  - `302` (unknown)
    Redirect to one-time S3 download report link

## Response 404:

  - `404` (unknown)
    Report not found

## Response 410:

  - `410` (unknown)
    Report unavailable (expired)

## Response 200 examples:

  - `Authentication failed` (unknown)

  - `Invalid data` (unknown)