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
Purchases → Get Many
AI-generatedOverview
This node interacts with the Distru Public API to retrieve multiple purchase records. It supports filtering and pagination, allowing users to specify page number, page size, and filter purchases by creation datetime, last modified datetime, or supplier company ID. This is useful for scenarios where users need to fetch and process bulk purchase data from Distru, such as for reporting, analytics, or integration with other systems.
Use Case Examples
- Fetch all purchases created within a specific date range for a particular supplier company.
- Retrieve the first 5000 purchase records for processing in a workflow.
Properties
| Name | Meaning |
|---|---|
| Additional Fields | Optional filters and pagination settings for retrieving purchases, including page number, page size, inserted datetime range, updated datetime range, and company ID. |
Output
JSON
json- Each item represents a purchase record retrieved from the Distru API.
Dependencies
- Requires an API token credential for the Distru API.
Troubleshooting
- Error 'Distru API token is not set' indicates missing or invalid API credentials; ensure the API token is configured correctly.
- Missing Resource ID error does not apply here since this operation does not require a resource ID.
- If the API returns an error, check the filter parameters for correct formatting, especially datetime ranges.
- Ensure pagination parameters are within valid ranges to avoid empty or partial results.