PUT
/v1/admin/fraud/flags/{flag}Decide a flag the way the Review queue does: one tap, with no note and no reason.
resolved: it was fraud and it has been dealt with.dismissed: a false alarm. The same situation is not raised again for 30 days.open: put a decided flag back in the queue.
Resolving or dismissing lifts every restriction the flag placed. Neither gives a
suspended trader their login back: that is done on the trader. Reopening lifts
nothing back on, and a flag that suspended somebody comes back open, not
auto_suspended.
Needs a firm. Our own staff name one with the Propper-Workspace header.
Request
| Field | Description |
|---|---|
status | resolved, dismissed or open |
curl -X PUT "https://api.proppertrading.com/v1/admin/fraud/flags/fflag_yhkjqnd8h67ggtbf" \
-H "Authorization: Bearer ptat_9f2c1a44_3b8e7d2f5c9a1b4e6d8f0a2c4e6b8d1f" \
-H "Propper-Workspace: acme" \
-H "Content-Type: application/json" \
-d '{"status": "resolved"}'
Response
The flag as it is now.
Errors
| Status | Code | Meaning |
|---|---|---|
| 400 | workspace_required | Asked by our own staff without naming a firm |
| 401 | invalid_token | Not a token, or the secret does not match |
| 401 | revoked_token | Signed out here or from another device |
| 401 | expired_token | Ninety days without use, or a set expiry passed |
| 403 | admin_access_required | This account no longer helps run the environment |
| 403 | insufficient_scope | This device does not hold admin:write |
| 403 | workspace_not_permitted | The Propper-Workspace header names an environment this account cannot act in |
| 403 | forbidden | Without manage_fraud |
| 404 | resource_not_found | No flag with that id in this firm |
| 422 | validation_failed | status is missing or not one of the three |