Actions68
- Parcels Actions
- Shipments Actions
- Rates Actions
- Transactions Actions
- Customs Items Actions
- Tracking Status Actions
- Batches Actions
- Orders Actions
- Pickups Actions
- Service Groups Actions
- Customs Declarations Actions
- Refunds Actions
- Manifests Actions
- Carrier Accounts Actions
- Webhooks Actions
- Carrier Parcel Templates Actions
- User Parcel Templates Actions
- Rates At Checkout Actions
- Shippo Accounts Actions
- Addresses Actions
Overview
This node interacts with the Shippo API to list refunds associated with shipments. It is useful for users who want to retrieve and manage refund data from their Shippo account, such as tracking refund statuses or auditing refund transactions. Practical examples include generating reports of all refunds issued within a certain period or integrating refund information into customer service workflows.
Properties
| Name | Meaning |
|---|---|
| SHIPPO API VERSION | Optional string to specify a non-default version of the Shippo API to use for the request. See Shippo's API versioning guide for details. |
Output
The node outputs JSON data representing a list of refunds retrieved from the Shippo API. Each item in the output typically contains details about an individual refund, such as refund ID, status, amount, currency, and related shipment information. The output does not include binary data.
Dependencies
- Requires an active Shippo API key credential configured in n8n.
- Connects to the Shippo API endpoint at
https://api.goshippo.com. - Optionally supports specifying the API version via a header if the user wants to target a specific Shippo API version.
Troubleshooting
Common issues:
- Invalid or missing API key will cause authentication errors.
- Using an unsupported or incorrect API version string may result in API errors or unexpected responses.
- Network connectivity problems can prevent successful API calls.
Error messages and resolutions:
- 401 Unauthorized: Check that the API key credential is correctly set up and has proper permissions.
- 400 Bad Request: Verify that the API version string (if provided) is valid according to Shippo's documentation.
- Timeout or network errors: Ensure stable internet connection and that the Shippo API endpoint is reachable.