Order Risk List

🔒

Requires read_order access scope. More access scope

The Order Risk List API provides a list of risks associated with a specific order. This helps merchants review all flagged risks for the given order in a paginated format.

This API is especially useful for:

  1. Fetching all risks flagged for an order.
  2. Facilitating review and risk management processes.
  3. Enabling data-driven decision-making regarding flagged risks.

Request Parameters

Public Request Parameters

📘

Public Request Parameters

Query Parameters

ParameterTypeRequiredDescriptionExample
pageint32NoPage number for pagination. Default is 1.1
per_pageint32NoLimit per page for pagination. Maximum is 100.10

Body Parameters

ParameterTypeRequiredDescriptionExample
riskobjectYesThe order risk object containing risk details.{...}
risk.levelstringYesRisk level for the order. Possible values: low, medium, high.low
risk.valuesarray of stringsNoList of risk details explaining the reason for the risk.["wrong order price"]
propertiesobjectNoCustom properties for the order risk.{ "key": "value" }
properties.keystringNoKey for the custom property.key

Response Description

Public Response Fields

📘

Public Response Parameters

Success Response

FieldTypeDescriptionExample
totalintTotal number of risks for the given order.4
risks[].idstringThe unique ID of the risk.372997190468224746
risks[].order_idstringThe unique ID of the associated order.633130-00000015
risks[].levelstringRisk level for the order. Possible values: low, medium, high.low
risks[].valuearray of stringsDetails explaining the reason for the risk.["wrong order price"]
risks[].properties.keystringKey for custom properties related to the risk.key
risks[].created_atstringTimestamp when the risk was created (ISO 8601 format).2024-04-25T06:37:40Z
risks[].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
404Not FoundUnable to find resourceUnable to find resource
Language
Credentials
Header
URL
Click Try It! to start a request and see the response here!