Fraud LensFraud ReportList fraud reports GET
GET
/api/v1/fraud/reports/

Retrieve a list of fraud reports with optional global or organization-specific view.

Scope Options:

  • global (default): View all approved fraud reports from all organizations in the fraud bank
  • organisation: View reports submitted by your organization only

Filtering:

  • Status (pending, under_review, approved, declined)
  • Fraud category (bank, ecommerce, telecom, digital, insurance, online, others)
  • Search (by report ID, name, fraud type)

Returns reports ordered by creation date (most recent first).

Authorization

ApiKeyAuth
X-API-Key<token>

In: header

Query Parameters

fraud_category?string

Filter by fraud category

Value in

  • "bank"
  • "digital"
  • "ecommerce"
  • "insurance"
  • "online"
  • "others"
  • "telecom"
page?integer

Page number (default: 1)

page_size?integer

Number of records per page (default: 20, max: 100)

scope?string

View scope: 'global' (default) for all approved reports, 'organisation' for your org's reports only

Value in

  • "global"
  • "organisation"
search?string

Search by report ID, suspect name, or fraud type

status?string

Filter by report status

Value in

  • "approved"
  • "declined"
  • "pending"
  • "under_review"

Response Body

application/json

curl -X GET "https://example.com/api/v1/fraud/reports/"
{  "data": {    "success": true,    "message": "Fraud reports retrieved successfully",    "data": {      "reports": [        {          "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",          "report_id": "Fraud-4190",          "full_name": "John Doe",          "fraud_category": "bank",          "fraud_type": "Account Takeover",          "status": "pending",          "status_display": "Pending Review",          "date_of_fraud": "2019-08-24",          "created_at": "2019-08-24T14:15:22Z"        }      ],      "pagination": {        "page": 1,        "page_size": 20,        "total_pages": 8,        "total_records": 156,        "has_next": true,        "has_previous": false      },      "filters": {        "status": "string",        "category": "string",        "search": "string"      }    }  },  "status": true,  "message": "Request successful.",  "errors": {},  "meta": {    "timestamp": "2019-08-24T14:15:22Z",    "version": "v1",    "request_id": "string"  },  "pagination": {    "page": 0,    "page_size": 0,    "total_pages": 0,    "total_items": 0  }}
Response Codes & Statuses: Prembly API responses include custom response_code values (e.g., 00 Success, 01 Not Found, 02 Unavailable).
View Response Codes Guide
Prembly Slack Community

Join our developer Slack channel for real-time integration support, engineering updates, and direct Q&A with the Prembly team.

Join Slack Channel