Distru icon

Distru

Interact with the Distru Public API v1

Actions35

Orders → Get Many

AI-generated

Overview

This node interacts with the Distru Public API to retrieve multiple order records. It supports filtering and pagination, allowing users to fetch orders based on various criteria such as creation date, update date, order date, delivery date, and status. This is useful for scenarios where users need to analyze, report, or process batches of orders from Distru, such as syncing order data with other systems or generating order reports.

Use Case Examples

  1. Fetch all orders created within a specific date range for monthly sales analysis.
  2. Retrieve orders filtered by status (e.g., only 'Completed' or 'Delivered' orders) for fulfillment tracking.
  3. Paginate through large sets of orders to import them into a CRM or ERP system.

Properties

Name Meaning
Page Number Specifies the page number for paginated results, allowing navigation through multiple pages of orders.
Page Size Defines the number of order items to return per page, controlling the batch size of the retrieved data.
Inserted Datetime Filters orders by their creation datetime using a comma-separated range (e.g., '2024-01-01T00:00:00Z,2024-06-01T00:00:00Z').
Updated Datetime Filters orders by their last modified datetime using a comma-separated range.
Order Datetime Filters orders by the order datetime range.
Delivery Datetime Filters orders by the delivery datetime range.
Status Filters orders by their status. Multiple statuses can be selected to refine the search.

Output

JSON

  • data - The main array of order objects returned by the Distru API, each representing an individual order with its details.

Dependencies

  • Requires an API token credential for authenticating requests to the Distru Public API.

Troubleshooting

  • Error 'Distru API token is not set': Ensure the API token credential is configured correctly in the node settings.
  • Error 'Resource ID is required': This error does not apply to 'Get Many' operation but may appear if the node configuration is incorrect for other operations.
  • Missing or invalid filter parameters may result in empty responses or errors; verify the date formats and status values.
  • If binary data is expected but missing, check the binary property name configuration (not applicable for 'Get Many' orders).

Links

Discussion