---
title: "List fraud report logs"
method: GET
path: "/v1/fraud-report/{fraudReportId}/logs"
tags: ["Fraud report"]
---

# List fraud report logs

`GET /v1/fraud-report/{fraudReportId}/logs`

Retrieve a fraud report's logs. 

**Note:** This endpoint takes an account token - an access token encoded with a Pismo account ID. Tokens can expire quickly, which can result in a <b>401 Unauthorized</b> message.

## Path parameters

- `fraudReportId` number, required

## Response `200`

OK

- FraudReportGetLogs
  - `fraud_report_id` number — Pismo fraud report ID.
  - `org_id` string — Organization/tenant ID.
  - `logs` object[]
    - `fraud_report_log_id` number — Pismo fraud report log ID.
    - `action` 'CREATE' | 'UPDATE' — Fraud report action
    - `report` ReportVisa — Visa report
      - `fraud_type` '0' | '1' | '2' | '3' | '4' | '5' | '6' | 'A' | 'B' | 'C' | 'D', required — Visa fraud type:<br> `0` - Lost<br> `1` - Stolen<br> `2` - Card not received as issued (NRI)<br> `3` - Fraudulent application (cardholder never applied for the card)<br> `4` - Issuer-reported counterfeit<br> `5` - Miscellaneous<br> `6` - Fraudulent use of account number<br> `A` = Incorrect processing<br> `B` = Account or credentials takeover<br> `C` = Merchant misrepresentation<br> `D` = Manipulation of account holder<br>
      - `fraud_type_category` 'CARDTXN' | 'NRI', required — Visa fraud type category: <br> `CARDTXN` - Card transaction<br> `NRI` - Not received as issued<br>
      - `notification_cd` number, required — Notification code specifying action performed on the fraud report. Domain values:<br> `1`: Addition<br> `2`: Addition of dup<br> `3`: Change<br> `4`: Delete<br> `5`: Reactivate. No edits restricting values based on the value of existing report in case.
      - `close_fraud_case_ind` boolean, required — Should the case be closed on the Visa's side? Default is `false`.
    - `correlation_id` string — The Correlation IDentifier field links related API requests and events
    - `created_at` string, date-time — Datetime program calendar strategy was created. Format = YYYY-MM-DDTHH:MM:SS:MM.
    - `status` 'PENDING' | 'PROCESSING' | 'CANCELLED' | 'SETTLED' | 'PROCESSED' — PENDING: Charge is scheduled and waiting for the cycle to close. PROCESSING: Cycle closing process has started and is awaiting completion. CANCELLED: Charge canceled due to link cancellation. SETTLED: Amount is zero and/or `minimum_spend_to_charge` has not been reached. PROCESSED: Charge was posted on the statement."

## Other responses

- `400` — Bad request
- `401` — Unauthorized
- `404` — Not found
- `500` — Internal server error
- `504` — Gateway timeout

---

[API](https://skmtc.net/pismo/apis/platform-authentication.md) · [All operations](https://skmtc.net/pismo/apis/platform-authentication/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/pismo/platform-authentication/revisions/935b62e16de4/schema)