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 operation deletes a specific user parcel template from the Shippo service. It is useful when you want to remove outdated or incorrect parcel templates associated with a user account in Shippo, helping keep your shipping configurations clean and up-to-date.
Practical examples include:
- Removing a parcel template that is no longer used for shipping.
- Cleaning up templates after changes in packaging options.
- Automating the management of parcel templates by deleting those that meet certain criteria.
Properties
| Name | Meaning |
|---|---|
| User Parcel Template Object Id | The unique identifier (Object ID) of the user parcel template you want to delete. This is required. |
| SHIPPO API VERSION | Optional header to specify a non-default version of the Shippo API to use for this request. See Shippo's API versioning guide for details. |
Output
The output will contain JSON data representing the result of the delete operation. Typically, this includes confirmation of deletion or an error message if the deletion failed.
No binary data is expected from 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 a custom API version via a header.
Troubleshooting
- Invalid Object ID: If the provided User Parcel Template Object Id does not exist or is malformed, the API will return an error. Verify the ID before attempting deletion.
- Authentication Errors: Ensure the API key credential is valid and has sufficient permissions.
- API Version Issues: Using an unsupported or incorrect API version string may cause errors. Refer to Shippo’s API versioning documentation.
- Network Issues: Connectivity problems can prevent successful API calls; check network settings and retry.