Suspected fraud deletion

The suspected fraud deletion excludes a suspected fraud. This deletion does not remove the suspected fraud from database but this registry will not be used in future suspected fraud querys.

Suspected fraud delete

delete

Authorizations

Path parameters

tokenstring · uuidRequired

Responses

200

Suspected fraud delete occurred successfully.

application/json

400

Suspected fraud delete failed due to a bad request.

application/json

401

Unauthorized,

application/json

422

Suspected fraud delete failed, but the request was processed by the API, just not by the peer.

application/json

500

Suspected fraud delete failed due to an unexpected error in the API.

application/json

503

Suspected fraud delete failed due to an unexpected error in the Peer.

application/json

delete

HTTPcURLJavaScriptPython

DELETE /fraud/suspected-fraud/{token} HTTP/1.1
Host: api.prd.combateafraude.com
Authorization: Bearer JWT
Accept: */*

{
  "message": "text",
  "requestStatus": {
    "status": "SUCCESS",
    "token": "123e4567-e89b-12d3-a456-426614174000"
  }
}

Options

As demonstrated in the example request, in the URL a path parameter must be passed and DELETE HTTP method used. The token parameter must be a UUID that's identify a Suspected Fraud, this token can be retrieved on the Suspected Fraud Query passing query mode as LOCAL.