Order Risk Detail

🔒

Requires read_order access scope. More access scope

Order Risk Detail API

The Order Risk Detail API retrieves the details of a specific risk associated with an order, providing insights into flagged risks for better decision-making.

This API is especially useful for:

  1. Reviewing specific risks flagged for an order.
  2. Enhancing fraud detection and order management processes.
  3. Providing detailed explanations for flagged risks.

Request Parameters

Public Request Parameters

📘

Public Request Parameters

Path Parameters

ParameterTypeRequiredDescriptionExample
order_idstringYesThe unique ID of the order.633130-00000015
idstringYesThe unique ID of the risk.372997190468224746

Response Description

Public Response Fields

📘

Public Response Parameters

Success Response

FieldTypeDescriptionExample
risk.idstringThe unique ID of the risk.372997190468224746
risk.order_idstringThe unique ID of the associated order.633130-00000015
risk.levelstringRisk level for the order. Possible values: low, medium, high.low
risk.valuearray of stringsDetails explaining the reason for the risk.["wrong order price"]
properties.keystringKey for custom properties related to the risk.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 EntityID is invalid or empty"Invalid ID"
404Not FoundThe record provided is not found"Record not found"
Language
Credentials
Header
URL
Click Try It! to start a request and see the response here!