Skip to content

Rippling: List device orders — response body — results item

List device orders: response body, field results / item. Complete fields and constraints for contract 2026-10-28.

API reference · Contract 2026-10-28

SDK schema: List device orders — response body — results item

FieldTypePresenceDescription and constraints
$objectRoot
cancel_requestedbooleanOptionalTrue when a cancellation has been requested but not yet completed.
completed_atstringOptionalWhen the order reached a terminal state (COMPLETED, FAILED, or CANCELED).
created_atstringRequired within parentRecord creation date
idstringRequired within parentIdentifier field
order_typestringOptionalThe type of hardware order, as reported by the underlying inventory order (for example: New Device Order, Warehouse Return, Warehouse Order, Add Existing Device, Assign Device, Empty Order, or Sell Device).
requested_by_idstringOptionalThe ID of the role that requested the order (often an IT admin). Null if system-created.
statusstringOptionalThe order lifecycle state (InventoryFlowState): CREATED, RUNNING, COMPLETED, FAILED, CANCELING, CANCELED.
updated_atstringRequired within parentRecord update date
warehouse_providerstringOptionalThe warehouse / vendor provider servicing the order (e.g. CDW, INGRAMMICRO, TD_SYNNEX, GROWRK).
workerModelOptionalExpand Retrieve a specific device order — response body — worker
worker_idstringOptionalThe ID of the worker the order is for (the recipient). Null if unassigned.

Referenced models: Retrieve a specific device order — response body — worker

Report an issue with this page

Necessary

Required for sign-in, security, authorization, and remembering your choices.

Always active

Analytics

Helps us understand which product and documentation features are useful.

Performance diagnostics

Uses performance tracing and privacy-masked session replay to diagnose problems.

You can change these choices at any time from Cookie settings.