Skip to main content
POST
/
dispositioning
/
assess
Assess Dispositions
curl --request POST \
  --url https://api.loopreturns.com/api/v1/dispositioning/assess \
  --header 'Content-Type: application/json' \
  --header 'X-Authorization: <api-key>' \
  --data '
{
  "items": [
    {
      "line_item_id": 1,
      "disposition_outcome": "back_to_stock",
      "return_processor": "warehouse-operator@example.com",
      "note": "This item will be returned to stock after bagging and tagging.",
      "inspected_at": "2024-03-31 23:59:59"
    }
  ]
}
'
[
  {
    "line_item_id": 1,
    "disposition_outcome": "back_to_stock",
    "return_processor": "warehouse-operator@example.com",
    "note": "This item will be returned to stock after bagging and tagging.",
    "inspected_at": "2024-03-31 23:59:59"
  }
]

Documentation Index

Fetch the complete documentation index at: https://docs.loopreturns.com/llms.txt

Use this file to discover all available pages before exploring further.

Authorizations

​
X-Authorization
string
header
required

Body

application/json
​
items
object[]
required

An array of items to be dispositioned.

Maximum array length: 30

Response

Success

Maximum array length: 30
​
line_item_id
integer
required

The unique identifier associated with the line item.

Example:

1

​
disposition_outcome
enum<string>
required

The final state of the returned item.

Available options:
back_to_stock,
resale_hold,
recycle,
donate,
missing
​
return_processor
string

The email address of the warehouse partner used to process returns.

Maximum string length: 100
Example:

"warehouse-operator@example.com"

​
note
string

Any additional notes on the item's final state.

Maximum string length: 65535
Example:

"This item will be returned to stock after bagging and tagging."

​
inspected_at
string<date-time>

The date and time at which the item was inspected, using the ISO 8601 date format.

Example:

"2024-03-31 23:59:59"