Actions35
- Adjustments Actions
- Assemblies Actions
- Batches Actions
- Companies Actions
- Contacts Actions
- Custom Fields Actions
- File Attachments Actions
- Inventory Actions
- Invoices Actions
- Locations Actions
- Orders Actions
- Packages Actions
- Payment Methods Actions
- Product POS Mappings Actions
- Products Actions
- Purchases Actions
- Strains Actions
- Test Results Actions
- Users Actions
Packages → Get Many
AI-generatedOverview
This node operation retrieves multiple package records from the Distru API. It supports pagination and filtering by creation and last modified datetime ranges, making it useful for scenarios where users need to fetch a list of packages with specific criteria or within certain timeframes. For example, a user can fetch all packages created between January and June 2024 or paginate through large sets of package data.
Use Case Examples
- Fetch all packages created between 2024-01-01 and 2024-06-01.
- Retrieve the second page of packages with 100 items per page.
Properties
| Name | Meaning |
|---|---|
| Page Number | Specifies the page number for paginated results, allowing users to navigate through multiple pages of package data. |
| Page Size | Defines the number of package items to retrieve per page, controlling the size of each paginated response. |
| Inserted Datetime | Filters packages by their creation datetime using a comma-separated range, e.g., "2024-01-01T00:00:00Z,2024-06-01T00:00:00Z". |
| Updated Datetime | Filters packages by their last modified datetime using a comma-separated range. |
Output
JSON
data- Array of package objects returned from the Distru API, each representing a package with its details.
Dependencies
- Requires an API token credential for the Distru API to authenticate requests.
Troubleshooting
- Ensure the API token credential is set correctly; missing or invalid tokens will cause authentication errors.
- Verify that the 'Resource ID' parameter is not required for this operation; if set incorrectly, it may cause errors.
- Check the format of datetime filters; they must be comma-separated ISO 8601 strings.
- If pagination parameters are set incorrectly (e.g., negative page number or size), the API may return errors or empty results.