Fraud summary

.md

How many flags each view of the Review queue holds, and who is held back right now.

Scopesadmin:read
Permissionview_fraud
GET/v1/admin/fraud/summary

The numbers around the flags: how many each view holds with the filters given, so a segmented control can say what a tap shows, and the two numbers beside the title of the Review queue.

enabled is false while the firm has switched fraud detection off, in which case no new flag arrives. Switching it on is a part of the detectors.

Needs a firm. Our own staff name one with the Propper-Workspace header.

Request

Takes the filters of the flags (category, level, restricted and q) and counts with them. view and sort are not read here.

curl "https://api.proppertrading.com/v1/admin/fraud/summary" \
  -H "Authorization: Bearer ptat_9f2c1a44_3b8e7d2f5c9a1b4e6d8f0a2c4e6b8d1f" \
  -H "Propper-Workspace: acme"

Response

{ "data": { "object": "fraud_summary", "enabled": true, "counts": { "open": 52, "monitor": 5, "closed": 5, "all": 62 }, "restricted": 6, "suspended": 1 }, "meta": { "request_id": "req_01m50zcktdxddr7vbw48rna0zm" } }

FieldDescription
countsFlags per view with the filters given: open, monitor, closed and all
restrictedTraders under at least one restriction right now, whatever the filters
suspendedFlags whose status is auto_suspended, whatever the filters. It counts flags, not people

Errors

StatusCodeMeaning
400workspace_requiredAsked by our own staff without naming a firm
400validation_failedcategory, level or restricted is not one of its values, or q is not text
401invalid_tokenNot a token, or the secret does not match
401revoked_tokenSigned out here or from another device
401expired_tokenNinety days without use, or a set expiry passed
403admin_access_requiredThis account no longer helps run the environment
403insufficient_scopeThis device does not hold admin:read
403workspace_not_permittedThe Propper-Workspace header names an environment this account cannot act in
403forbiddenWithout view_fraud