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
The "Get Manifest" operation in the Manifests resource allows users to retrieve detailed information about a specific shipping manifest by providing its unique identifier. This node is useful in scenarios where you need to track, verify, or audit shipping manifests within your logistics or e-commerce workflows. For example, after creating a manifest for a batch of shipments, you can use this node to fetch its current status, contents, and related metadata.
Properties
| Name | Meaning |
|---|---|
| Manifest Id | The unique object ID of the manifest you want to retrieve. This is required to specify which manifest's details to fetch. |
| SHIPPO API VERSION | Optional header string to specify a non-default version of the Shippo API to use for this request. Useful for compatibility or testing different API versions. |
Output
The node outputs JSON data representing the full details of the requested manifest. This typically includes fields such as manifest status, creation date, associated shipments, and other metadata provided by the Shippo API. There is no binary output for this operation.
Dependencies
- Requires an active API key credential for authenticating with the Shippo API.
- The node sends requests to the Shippo API endpoint at
https://api.goshippo.com. - Optionally supports specifying the API version via a custom header.
Troubleshooting
- Manifest Id missing or invalid: Ensure that the Manifest Id property is provided and correctly matches an existing manifest in your Shippo account.
- Authentication errors: Verify that the API key credential is valid and has appropriate permissions.
- API version issues: If using the optional API version header, confirm that the specified version exists and is supported by Shippo.
- Network or API errors: Check network connectivity and Shippo service status if requests fail unexpectedly.