Shippo icon

Shippo

Interact with Shippo API

Actions68

Overview

This node interacts with the Shippo API to list customs items. It is useful for retrieving paginated lists of customs items that have been created or stored in a Shippo account. Typical use cases include managing international shipping documentation, automating customs data retrieval, and integrating customs item information into broader logistics workflows.

For example, a user might want to fetch all customs items page by page to display them in a dashboard or to process them further for shipment preparation.

Properties

Name Meaning
Page The page number of results to retrieve. Allows pagination through the list of customs items.
Results The number of customs items to return per page. Maximum allowed is 100.
SHIPPO API VERSION Optional header string to specify a non-default version of the Shippo API to use for this request.

Output

The node outputs JSON data representing the list of customs items retrieved from the Shippo API. This typically includes an array of customs item objects with their details such as description, quantity, value, weight, origin country, and other relevant customs information.

No binary data output is indicated by the source code or properties.

Dependencies

  • Requires an active Shippo API key credential configured in n8n.
  • Connects to the Shippo REST API at https://api.goshippo.com.
  • Supports optional API versioning via a custom header.

Troubleshooting

  • Invalid API Key or Authentication Errors: Ensure the Shippo API key credential is correctly set up and has sufficient permissions.
  • Pagination Issues: If requesting pages beyond available data, the API may return empty results. Adjust the "Page" and "Results" parameters accordingly.
  • API Version Header Misuse: Providing an incorrect or unsupported API version string may cause errors. Refer to Shippo's API versioning documentation to use valid versions.
  • Rate Limits: Shippo enforces rate limits; excessive requests may result in throttling errors. Implement retry logic or reduce request frequency if needed.

Links and References

Discussion