Update Order Risk

🔒

Requires write_order access scope. More access scope

The Update Order Risk API allows merchants to modify the risk level and associated details of an order. This enables businesses to reassess risks dynamically and adjust mitigation strategies accordingly.

This API is especially useful for:

  1. Updating the risk assessment of an order after manual or automated review.
  2. Customizing risk management workflows for specific orders.
  3. Enhancing order security by adjusting risk details dynamically.

Request Parameters

Public Request Parameters

📘

Public Request Parameters

Path Parameters

ParameterTypeRequiredDescriptionExample
order_idstringYesThe unique ID of the order.19653511576161
idstringYesThe unique ID of the risk entry.54648070439338

Body Parameters

ParameterTypeRequiredDescriptionExample
risk.levelstringYesThe new risk level for the order. Possible values: low, medium, high.medium
risk.detailsarray of stringsYesA list of strings describing the updated risk details.["Incorrect shipping address", "High-value order"]
risk.properties.keystringOptionalCustom property key for additional context.key

Response Description

Public Response Fields

📘

Public Response Parameters

Success Response

FieldTypeDescriptionExample
risk.idstringThe unique ID of the created risk.372997190468224746
risk.order_idstringThe unique ID of the order associated with the risk.633130-00000015
risk.levelstringRisk level for the order. Possible values: low, medium, high.low
risk.valuearray of stringsList of reasons or details for the risk.["wrong order price"]
properties.keystringKey for the custom property.key
created_atstringTimestamp when the risk was created (ISO 8601 format).2024-04-25T06:37:40Z
updated_atstringTimestamp when the risk was last updated (ISO 8601 format).2024-04-25T06:37:40Z

Error Response

Error responses in the API can be represented using two different fields: errors and error. Both fields provide details about issues encountered during request processing. Below is an explanation of the fields with their respective examples and descriptions.

FieldTypeExampleDescription
errorsArray[ "file number error"]A list of errors encountered during the request processing.
FieldTypeExampleDescription
errorString "store is not active"Indicates an error encountered during the process

Error Detail

Status CodeMessagePossible ReasonExample Response
400Bad RequestInvalid input format or request structure (e.g., missing required fields or incorrect data types).Bad Request
UnauthorizedThe request is missing valid authentication credentials or the credentials provided are invalid.Unauthorized
422Unprocessable Entitymissing required field."Details is required"
missing required field."Level is required"
Language
Credentials
Header
URL
Click Try It! to start a request and see the response here!