Feedback Update

X-API-Version

Specifies the API version used for the request. If omitted, the default version is used. Socure recommends pinning a version to avoid unexpected behavioral changes when new versions are released.

id

required

The customer-side identifier (id) provided during the original evaluation request.

workflow

required

The environment-specific Workflow identifier that the ID is associated with.

Note: The workflow name must be unique within your RiskOS™ environment. It is not scoped by use case and must identify a single active workflow for each Evaluation API request.

fraud_label

required

The fraud label for an application. Accepted values are fraud and non-fraud.

fraud_type

The fraud typology or category that best describes the nature of the fraud.

notes

Optional notes or additional information to be added to the case.

recorded_at

The date when the event was recorded. Use the YYYY-MM-DD format as defined by the RFC 3339 full-date standard. If omitted, defaults to the current date.

recorded_by

The name or identifier of the person who recorded the fraud. If omitted, defaults to the authenticated user.

tags

Tags to categorize or label the fraud case. Useful for filtering, reporting, or internal tracking. Tags are validated against the namespace's configured tag definitions. If any tag is invalid, the request returns a 400 error.

CURL Example

curl --request PUT \
     --url https://riskos.socure.com/api/feedback \
     --header 'accept: application/json' \
     --header 'content-type: application/json' \
     --data '{
  "id": "9876543",
  "workflow": "consumer_onboarding",
  "fraud_label": "fraud",
  "fraud_type": "synthetic",
  "notes": "This is a synthetic fraud case",
  "recorded_at": "2022-05-19",
  "recorded_by": "John Doe",
  "tags": ["tag1","tag2"]
}'

Response Example

{
  "message": "Fraud feedback updated successfully : id=123456, fraud_label=fraud"
}