Synca Superpharm icon

Synca Superpharm

Comprehensive Superpharm Marketplace API integration for Orders, Offers, Products, Inventory, Messages, Shipping, and more

Actions37

Orders → Get Orders

AI-generated

Overview

This node integrates with the Superpharm Marketplace API to retrieve multiple orders based on various filtering and query options. It is useful for scenarios where users need to fetch order data for processing, reporting, or synchronization with other systems. For example, a user can retrieve orders filtered by date range, order state, payment workflow, or specific order IDs, with pagination and sorting capabilities.

Use Case Examples

  1. Retrieve the latest 10 orders sorted by creation date in ascending order.
  2. Fetch orders with specific state codes like SHIPPING or SHIPPED for monitoring shipment status.
  3. Get orders filtered by a specific shop ID and locale for multi-shop and internationalized data handling.

Properties

Name Meaning
Credentials Select the Superpharm API credentials to use for authentication.
Query Options Options to control pagination, sorting, and localization of the orders retrieved, including limit, offset, page token, sort field, order direction, shop ID, and locale.
Filters Filters to narrow down the orders retrieved, such as order state codes, order IDs, date range, payment workflow, channel codes, and incident presence.
Advanced Options Additional options to control the API request behavior, including whether to return the full API response, handle rate limiting automatically, and set request timeout in seconds.

Output

JSON

  • json - The main JSON output containing the retrieved orders data or a message if no orders are found.

Dependencies

  • Superpharm API credentials for authentication

Troubleshooting

  • Common issues include authentication failures due to invalid or missing credentials. Ensure correct API credentials are selected.
  • Rate limiting errors (HTTP 429) may occur; enabling automatic retry in advanced options can help mitigate this.
  • Timeout errors can happen if the API response is slow; adjust the request timeout in advanced options accordingly.
  • If no orders are found, the node returns a message indicating no data, which is not an error but a valid response.

Links

Discussion