Suspected Fraud Deletion

Authentication Requirements:

• Regular endpoints use OAuth2 authentication with base URL: https://api.us.prd.caf.io
• For enhanced security, some endpoints may also support mTLS authentication with base URL: https://mtls.us.prd.caf.io
• For information on implementing mTLS, access Using mTLS

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 queries.

Suspected Fraud Delete

delete

https://api.us.prd.caf.io/v1/rs6https://mtls.us.prd.caf.io/v1/rs6https://api.us.stg.caf.io/v1/rs6https://mtls.us.stg.caf.io/v1/rs6

/suspected-fraud/{token}

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 queries.

Permission required: Delete RS6

Authorizations

bearerAuth

AuthorizationstringRequired

JWT Authorization header using the Bearer scheme.

Path parameters

tokenstring · uuidRequired

UUID that identifies a Suspected Fraud. This token can be retrieved on the Suspected Fraud Query passing query mode as LOCAL or DELETED.

Header parameters

AuthorizationstringRequired

Your access token. See more in the 'Authentication' topic of this section.

Example: Bearer YOUR_TOKEN

Responses

200

Suspected fraud delete occurred successfully.

application/json

messagestringRequired

Human readable message informing about the operation.

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/suspected-fraud/{token}

HTTPcURLJavaScriptPython

DELETE /v1/rs6/suspected-fraud/{token} HTTP/1.1
Host: api.us.prd.caf.io
Authorization: text
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 identifies a Suspected Fraud, this token can be retrieved on the Suspected Fraud Query passing query mode as LOCAL.