Skip to content
/
Create a new customs decl...

Shippo external API. (2018-02-08)

Use this API to integrate with the Shippo service

Download OpenAPI description
public-api.json
public-api.yaml
Overview
URL
https://goshippo.com/contact/
Languages
Servers
https://api.goshippo.com

Overview

First-time users and those looking for specific integration tutorials, see our full API documentation and guides.
Download the API Specification yaml file

API Resources

All API URLs listed in this documentation are relative to https://api.goshippo.com/.

For example, the /addresses/ resource is reachable at https://api.goshippo.com/addresses/.

Authentication

The API requires Shippo's token HTTP Authentication with your Shippo token (live or test).

In order to authenticate properly, please put Authorization: ShippoToken <token> in your header. You can find your token on the Shippo API settings page.

For more information about authentication and test mode, please visit our Authentication guide.

The API is available via Secure Socket Layer (SSL) only. All requests to the Shippo API must use TLS version 1.2 or higher.

Request & Response Data

Request data is passed to the API by POSTing JSON objects with the appropriate key/value-pairs to the respective resource. The documentation for each API resource contains more details on the values accepted by a given resource.

Response data also formatted as JSON object. You can specify how many results per page are to be returned. For instance, /rates/?results=25 will return up to 25 results.

REST & Disposable Objects

The Shippo API is built around REST principles. Use POST requests to create objects, GET requests to retrieve objects, and PUT requests to update objects.

Only the Carrier Accounts object can be updated via PUT requests. All other objects such as Addresses, Parcels, Shipments, Rates, Transactions, Refunds, Customs Items, and Customs Declarations are disposable. This means that once you have created an object, you cannot change it. Instead, create a new one with the desired values.

API Version

This reference guide supports the Shippo API version: 2018-02-08 .

To see reference guides for older API versions, see our legacy reference guide. For more information about Shippo API versions, see our API versions guide.

Addresses

Addresses are the locations a parcel is being shipped from and to. They represent company and residential places. Among other things, you can use address objects to create shipments, calculate shipping rates, and purchase shipping labels.

Schemas
Operations

Parcels

A parcel is an item you are shipping. The parcel object includes details about its physical make-up of the parcel. It includes dimensions and weight that Shippo uses to calculate rates.

Schemas
Operations

Carrier Parcel Templates

A carrier parcel template represents a package used for shipping that has preset dimensions defined by a carrier. Some examples of a carrier parcel template include USPS Flat Rate Box and Fedex Small Pak. When using a carrier parcel template, the rates returned may be limited to the carrier that provides the box. You can create user parcel templates using a carrier parcel template. Shippo takes the dimensions of the carrier parcel template but you must configure the weight.

Schemas
Operations

User Parcel Templates

A user parcel template represents a package used for shipping that has preset dimensions and attributes defined by you. They are useful for capturing attributes of parcel-types you frequently use for shipping, allowing them to be defined once and then used for many shipments. These parcel templates can also be used for live rates.

User parcel templates can also be created using a carrier parcel template, where the dimensions will be copied from the carrier presets, but the weight can be configured by you.

Schemas
Operations

Shipments

A shipment is the act of transporting goods. A shipment object contains to and from addresses, and the parcel details that you are shipping. You can use the shipment object to retrieve shipping rates and purchase a shipping label.

Schemas
Operations

Rates

A rate is the cost to ship a parcel from a carrier. The rate object details the service level including the cost and transit time.

Schemas
Operations

Transactions (shipping labels)

A transaction is the purchase of a shipping label from a shipping provider for a specific service. You can print purchased labels and used them to ship a parcel with a carrier, such as USPS or FedEx.

Schemas
Operations

Batches

A batch is a technique for creating multiple labels at once. Use the batch object to create and purchase many shipments in two API calls. After creating the batch, retrieve the batch to verify that all shipments are valid. You can add and remove shipments after you have created the batch. When all shipments are valid you can purchase the batch and retrieve all the shipping labels.

Schemas
Operations

Tracking Status


If you purchased your shipping label through Shippo, you can also get all the tracking details of your Shipment from the Transaction object.

A tracking status of a package is an indication of current location of a package in the supply chain. For example, sorting, warehousing, or out for delivery. Use the tracking status object to track the location of your shipments.

When using your Test token for tracking, you need to use Shippo's predefined tokens for testing different tracking statuses. You can find more information in our Tracking tutorial on how to do this, and what the payloads look like.

Schemas
Operations

Webhooks

Webhooks are a way for Shippo to notify your application when a specific event occurs. For example, when a label is purchased or when a shipment tracking status has changed. You can use webhooks to trigger actions in your application, such as sending an email or updating a database.

Schemas
Operations

Customs Items

Customs declarations are relevant information, including one or multiple customs items, you need to provide for customs clearance for your international shipments.

Schemas
Operations

Customs Declarations

Customs declarations are relevant information, including one or multiple customs items, you need to provide for customs clearance for your international shipments.

Schemas
Operations

List all customs declarations

Request

Returns a list of all customs declaration objects

Security
APIKeyHeader
Query
pageinteger(int64)

The page number you want to select

Default 1
resultsinteger(int64)<= 100

The number of results to return per page (max 100, default 5)

Default 5
Headers
SHIPPO-API-VERSIONstring

Optional string used to pick a non-default API version to use. See our API version guide.

Example: 2018-02-08
curl https://api.goshippo.com/customs/declarations/ \
-H "Authorization: ShippoToken shippo_test_3a47d23c032ca626fce863c48d0f93d63a394396"

Responses

Bodyapplication/json
nextstring
Example: "baseurl?page=3&results=10"
previousstring
Example: "baseurl?page=1&results=10"
resultsArray of objects(Customs Declaration)
Response
application/json
{
  "next": "baseurl?page=3&results=10",
  "previous": "baseurl?page=1&results=10",
  "results": [
    { … }
  ]
}

Create a new customs declaration

Request

Creates a new customs declaration object

Security
APIKeyHeader
Headers
SHIPPO-API-VERSIONstring

Optional string used to pick a non-default API version to use. See our API version guide.

Example: 2018-02-08
Bodyapplication/jsonrequired

CustomsDeclaration details.

aes_itnstring

required if eel_pfc is AES_ITN
AES / ITN reference of the shipment.

b13a_filing_optionstring

B13A Option details are obtained by filing a B13A Canada Export Declaration via the Canadian Export Reporting System (CERS). More information on reporting commercial exports from Canada. Allowed values available here

Enum"FILED_ELECTRONICALLY""SUMMARY_REPORTING""NOT_REQUIRED"
Example: "FILED_ELECTRONICALLY"
b13a_numberstring

must be provided if and only if b13a_filing_option is provided
Represents:
the Proof of Report (POR) Number when b13a_filing_option is FILED_ELECTRONICALLY;
the Summary ID Number when b13a_filing_option is SUMMARY_REPORTING;
or the Exemption Number when b13a_filing_option is NOT_REQUIRED.

certificatestring

Certificate reference of the shipment.

certifybooleanrequired

Expresses that the certify_signer has provided all information of this customs declaration truthfully.

Example: true
certify_signerstringrequired

Name of the person who created the customs declaration and is responsible for the validity of all information provided.

Example: "Shawn Ippotle"
commercial_invoiceboolean
contents_explanationstring

required if contents_type is OTHER
Explanation of the type of goods of the shipment.

Example: "T-Shirt purchase"
disclaimerstring<= 1000 characters

Disclaimer for the shipment and customs information that have been provided.

Carrier-Specific Constraints:

CarrierConstraints
FedExMax 554 characters
duties_payorobject

Specifies who will pay the duties for the shipment. Only accepted for FedEx shipments.

exporter_identificationobject(CustomsExporterIdentification)

Additional exporter identification that may be required to ship in certain countries

exporter_referencestring

Exporter reference of an export shipment.

importer_referencestring

Importer reference of an import shipment.

is_vat_collectedboolean

Indicates whether the shipment's destination VAT has been collected. May be required for some destinations.

invoicestring<= 15 characters

Invoice reference of the shipment.

Example: "#123123"
licensestring

License reference of the shipment.

metadatastring

A string of up to 100 characters that can be filled with any additional information you want to attach to the object.

Example: "Order ID #123123"
notesstring

Additional notes to be included in the customs declaration.

address_importerobject(AddressImporter)

Object that represents the address of the importer

contents_typestring(CustomsDeclarationContentsTypeEnum)required

Type of goods of the shipment.
Allowed values available here

Enum"DOCUMENTS""GIFT""SAMPLE""MERCHANDISE""HUMANITARIAN_DONATION""RETURN_MERCHANDISE""OTHER"
eel_pfcstring(CustomsDeclarationEelPfcEnum)

EEL / PFC type of the shipment. For most shipments from the US to CA, NOEEI_30_36 is applicable; for most other shipments from the US, NOEEI_30_37_a is applicable. Allowed values available here

Enum"NOEEI_30_37_a""NOEEI_30_37_h""NOEEI_30_37_f""NOEEI_30_36""AES_ITN"
incotermstring(CustomsDeclarationIncotermEnum)

The incoterm reference of the shipment. FCA is available for DHL Express and FedEx only. eDAP is available for DPD UK only. DAP is available for DHL Express, FedEx, and DPD UK. If expecting DAP for other carriers, please use DDU. Allowed values available here Carrier-specific restrictions are in the table below.

Carrier-Specific Constraints:

CarrierConstraints
FedExMust be one of DDP, DDU, FCA, DAP
Enum"DDP""DDU""FCA""DAP""eDAP"
itemsArray of objects(CustomsItemCreateRequest)required
non_delivery_optionstring(CustomsDeclarationNonDeliveryOptionEnum)required

Indicates how the carrier should proceed in case the shipment can't be delivered. Allowed values available here

Enum"ABANDON""RETURN"
testboolean
Example: true
curl https://api.goshippo.com/customs/declarations/ \
-H "Authorization: ShippoToken " \
-H "Content-Type: application/json"  \
-d '{          
      "contents_type": "MERCHANDISE",
      "non_delivery_option": "RETURN",
      "certify": true,
      "certify_signer": "Simon Kreuz",
      "incoterm": "DDU",
      "items": [{
                "description": "T-shirt",
                "quantity": 20,
                "net_weight": "5",
                "mass_unit": "lb",
                "value_amount": "200",
                "value_currency": "USD",
                "tariff_number": "",
                "origin_country": "US"
        }]
}'

Responses

Bodyapplication/json
aes_itnstring

required if eel_pfc is AES_ITN
AES / ITN reference of the shipment.

b13a_filing_optionstring

B13A Option details are obtained by filing a B13A Canada Export Declaration via the Canadian Export Reporting System (CERS). More information on reporting commercial exports from Canada. Allowed values available here

Example: "FILED_ELECTRONICALLY"
b13a_numberstring

must be provided if and only if b13a_filing_option is provided
Represents:
the Proof of Report (POR) Number when b13a_filing_option is FILED_ELECTRONICALLY;
the Summary ID Number when b13a_filing_option is SUMMARY_REPORTING;
or the Exemption Number when b13a_filing_option is NOT_REQUIRED.

certificatestring

Certificate reference of the shipment.

certifybooleanrequired

Expresses that the certify_signer has provided all information of this customs declaration truthfully.

Example: true
certify_signerstringrequired

Name of the person who created the customs declaration and is responsible for the validity of all information provided.

Example: "Shawn Ippotle"
commercial_invoiceboolean
contents_explanationstring

required if contents_type is OTHER
Explanation of the type of goods of the shipment.

Example: "T-Shirt purchase"
disclaimerstring<= 1000 characters

Disclaimer for the shipment and customs information that have been provided.

Carrier-Specific Constraints:

CarrierConstraints
FedExMax 554 characters
duties_payorobject

Specifies who will pay the duties for the shipment. Only accepted for FedEx shipments.

exporter_identificationobject(CustomsExporterIdentification)

Additional exporter identification that may be required to ship in certain countries

exporter_referencestring

Exporter reference of an export shipment.

importer_referencestring

Importer reference of an import shipment.

is_vat_collectedboolean

Indicates whether the shipment's destination VAT has been collected. May be required for some destinations.

invoicestring<= 15 characters

Invoice reference of the shipment.

Example: "#123123"
licensestring

License reference of the shipment.

metadatastring

A string of up to 100 characters that can be filled with any additional information you want to attach to the object.

Example: "Order ID #123123"
notesstring

Additional notes to be included in the customs declaration.

address_importerstring

Object ID of the Importer address.

Example: "257ba08436604d2aaf069caafe7acb2a"
contents_typestring(CustomsDeclarationContentsType)required

Type of goods of the shipment.
Allowed values available here

eel_pfcstring(CustomsDeclarationEelPfc)

EEL / PFC type of the shipment. For most shipments from the US to CA, NOEEI_30_36 is applicable; for most other shipments from the US, NOEEI_30_37_a is applicable. Allowed values available here

incotermstring(CustomsDeclarationIncoterm)

The incoterm reference of the shipment. FCA is available for DHL Express and FedEx only. eDAP is available for DPD UK only. DAP is available for DHL Express, FedEx, and DPD UK. If expecting DAP for other carriers, please use DDU. Allowed values available here Carrier-specific restrictions are in the table below.

Carrier-Specific Constraints:

CarrierConstraints
FedExMust be one of DDP, DDU, FCA, DAP
invoiced_chargesobject(CustomsInvoicedCharges)

Additional invoiced charges to be shown on the Customs Declaration Commercial Invoice.

itemsArray of stringsrequired

Distinct Parcel content items as Customs Items object_ids.

Example: ["5087f181d1dc4b14b73fdbf636498886"]
non_delivery_optionstring(CustomsDeclarationNonDeliveryOption)required

Indicates how the carrier should proceed in case the shipment can't be delivered. Allowed values available here

object_createdstring(date-time)

Date and time of object creation.

Example: "2014-07-17T01:01:08.306Z"
object_idstring

Unique identifier of the given object.

Example: "e2197a54da9d470480f4f8796cc419cb"
object_ownerstring

Username of the user who created the object.

Example: "shippotle@shippo.com"
object_statestring(ObjectStateEnum)

Indicates the validity of the enclosing object

Enum"VALID""INVALID"
object_updatedstring(date-time)

Date and time of last object update.

Example: "2014-07-17T01:01:08.306Z"
testboolean

Indicates whether the object has been created in test mode.

Example: true
Response
application/json
{
  "aes_itn": "string",
  "b13a_filing_option": "FILED_ELECTRONICALLY",
  "b13a_number": "string",
  "certificate": "string",
  "certify": true,
  "certify_signer": "Shawn Ippotle",
  "commercial_invoice": true,
  "contents_explanation": "T-Shirt purchase",
  "disclaimer": "string",
  "duties_payor": {
    "account": "2323434543",
    "type": "THIRD_PARTY",
    "address": { … }
  },
  "exporter_identification": {
    "eori_number": "PL123456790ABCDE",
    "tax_id": { … }
  },
  "exporter_reference": "string",
  "importer_reference": "string",
  "is_vat_collected": true,
  "invoice": "#123123",
  "license": "string",
  "metadata": "Order ID #123123",
  "notes": "string",
  "address_importer": "257ba08436604d2aaf069caafe7acb2a",
  "contents_type": "MERCHANDISE",
  "eel_pfc": "NOEEI_30_37_a",
  "incoterm": "DDP",
  "invoiced_charges": {
    "currency": "string",
    "total_shipping": "string",
    "total_taxes": "string",
    "total_duties": "string",
    "other_fees": "string"
  },
  "items": [
    "5087f181d1dc4b14b73fdbf636498886"
  ],
  "non_delivery_option": "RETURN",
  "object_created": "2014-07-17T01:01:08.306Z",
  "object_id": "e2197a54da9d470480f4f8796cc419cb",
  "object_owner": "shippotle@shippo.com",
  "object_state": "VALID",
  "object_updated": "2014-07-17T01:01:08.306Z",
  "test": true
}

Retrieve a customs declaration

Request

Returns an existing customs declaration using an object ID

Security
APIKeyHeader
Path
CustomsDeclarationIdstringrequired

Object ID of the customs declaration

Query
pageinteger(int64)

The page number you want to select

Default 1
Headers
SHIPPO-API-VERSIONstring

Optional string used to pick a non-default API version to use. See our API version guide.

Example: 2018-02-08
curl https://api.goshippo.com/customs/declarations/e2197a54da9d470480f4f8796cc419cb \
-H "Authorization: ShippoToken shippo_test_3a47d23c032ca626fce863c48d0f93d63a394396"

Responses

Bodyapplication/json
aes_itnstring

required if eel_pfc is AES_ITN
AES / ITN reference of the shipment.

b13a_filing_optionstring

B13A Option details are obtained by filing a B13A Canada Export Declaration via the Canadian Export Reporting System (CERS). More information on reporting commercial exports from Canada. Allowed values available here

Example: "FILED_ELECTRONICALLY"
b13a_numberstring

must be provided if and only if b13a_filing_option is provided
Represents:
the Proof of Report (POR) Number when b13a_filing_option is FILED_ELECTRONICALLY;
the Summary ID Number when b13a_filing_option is SUMMARY_REPORTING;
or the Exemption Number when b13a_filing_option is NOT_REQUIRED.

certificatestring

Certificate reference of the shipment.

certifybooleanrequired

Expresses that the certify_signer has provided all information of this customs declaration truthfully.

Example: true
certify_signerstringrequired

Name of the person who created the customs declaration and is responsible for the validity of all information provided.

Example: "Shawn Ippotle"
commercial_invoiceboolean
contents_explanationstring

required if contents_type is OTHER
Explanation of the type of goods of the shipment.

Example: "T-Shirt purchase"
disclaimerstring<= 1000 characters

Disclaimer for the shipment and customs information that have been provided.

Carrier-Specific Constraints:

CarrierConstraints
FedExMax 554 characters
duties_payorobject

Specifies who will pay the duties for the shipment. Only accepted for FedEx shipments.

exporter_identificationobject(CustomsExporterIdentification)

Additional exporter identification that may be required to ship in certain countries

exporter_referencestring

Exporter reference of an export shipment.

importer_referencestring

Importer reference of an import shipment.

is_vat_collectedboolean

Indicates whether the shipment's destination VAT has been collected. May be required for some destinations.

invoicestring<= 15 characters

Invoice reference of the shipment.

Example: "#123123"
licensestring

License reference of the shipment.

metadatastring

A string of up to 100 characters that can be filled with any additional information you want to attach to the object.

Example: "Order ID #123123"
notesstring

Additional notes to be included in the customs declaration.

address_importerstring

Object ID of the Importer address.

Example: "257ba08436604d2aaf069caafe7acb2a"
contents_typestring(CustomsDeclarationContentsType)required

Type of goods of the shipment.
Allowed values available here

eel_pfcstring(CustomsDeclarationEelPfc)

EEL / PFC type of the shipment. For most shipments from the US to CA, NOEEI_30_36 is applicable; for most other shipments from the US, NOEEI_30_37_a is applicable. Allowed values available here

incotermstring(CustomsDeclarationIncoterm)

The incoterm reference of the shipment. FCA is available for DHL Express and FedEx only. eDAP is available for DPD UK only. DAP is available for DHL Express, FedEx, and DPD UK. If expecting DAP for other carriers, please use DDU. Allowed values available here Carrier-specific restrictions are in the table below.

Carrier-Specific Constraints:

CarrierConstraints
FedExMust be one of DDP, DDU, FCA, DAP
invoiced_chargesobject(CustomsInvoicedCharges)

Additional invoiced charges to be shown on the Customs Declaration Commercial Invoice.

itemsArray of stringsrequired

Distinct Parcel content items as Customs Items object_ids.

Example: ["5087f181d1dc4b14b73fdbf636498886"]
non_delivery_optionstring(CustomsDeclarationNonDeliveryOption)required

Indicates how the carrier should proceed in case the shipment can't be delivered. Allowed values available here

object_createdstring(date-time)

Date and time of object creation.

Example: "2014-07-17T01:01:08.306Z"
object_idstring

Unique identifier of the given object.

Example: "e2197a54da9d470480f4f8796cc419cb"
object_ownerstring

Username of the user who created the object.

Example: "shippotle@shippo.com"
object_statestring(ObjectStateEnum)

Indicates the validity of the enclosing object

Enum"VALID""INVALID"
object_updatedstring(date-time)

Date and time of last object update.

Example: "2014-07-17T01:01:08.306Z"
testboolean

Indicates whether the object has been created in test mode.

Example: true
Response
application/json
{
  "aes_itn": "string",
  "b13a_filing_option": "FILED_ELECTRONICALLY",
  "b13a_number": "string",
  "certificate": "string",
  "certify": true,
  "certify_signer": "Shawn Ippotle",
  "commercial_invoice": true,
  "contents_explanation": "T-Shirt purchase",
  "disclaimer": "string",
  "duties_payor": {
    "account": "2323434543",
    "type": "THIRD_PARTY",
    "address": { … }
  },
  "exporter_identification": {
    "eori_number": "PL123456790ABCDE",
    "tax_id": { … }
  },
  "exporter_reference": "string",
  "importer_reference": "string",
  "is_vat_collected": true,
  "invoice": "#123123",
  "license": "string",
  "metadata": "Order ID #123123",
  "notes": "string",
  "address_importer": "257ba08436604d2aaf069caafe7acb2a",
  "contents_type": "MERCHANDISE",
  "eel_pfc": "NOEEI_30_37_a",
  "incoterm": "DDP",
  "invoiced_charges": {
    "currency": "string",
    "total_shipping": "string",
    "total_taxes": "string",
    "total_duties": "string",
    "other_fees": "string"
  },
  "items": [
    "5087f181d1dc4b14b73fdbf636498886"
  ],
  "non_delivery_option": "RETURN",
  "object_created": "2014-07-17T01:01:08.306Z",
  "object_id": "e2197a54da9d470480f4f8796cc419cb",
  "object_owner": "shippotle@shippo.com",
  "object_state": "VALID",
  "object_updated": "2014-07-17T01:01:08.306Z",
  "test": true
}

Carrier Accounts

Carriers are the companies who deliver your package. Shippo uses Carrier account objects as credentials to retrieve shipping rates and purchase labels from shipping Carriers.

Schemas
Operations

Manifests

A manifest is a single-page document with a barcode that carriers can scan to accept all packages into transit without the need to scan each item individually. They are close-outs of shipping labels of a certain day. Some carriers require manifests to process the shipments.

Schemas
Operations

Pickups

A pickup is when you schedule a carrier to collect a package for delivery. Use Shippo’s pickups endpoint to schedule pickups with USPS and DHL Express for eligible shipments that you have already created.

Schemas
Operations

Orders (beta)

An order is a request from a customer to purchase goods from a merchant. Use the orders object to load orders from your system to the Shippo dashboard. You can use the orders object to create, retrieve, list, and manage orders programmatically. You can also retrieve shipping rates, purchase labels, and track shipments for each order.

Schemas
Operations

Refunds

Refunds are reimbursements for successfully created but unused shipping labels or other charges.

Schemas
Operations

Service Groups

A service group is a set of service levels grouped together. Rates at checkout uses services groups to present available shipping options to customers in their shopping basket.

Schemas
Operations

Rates at Checkout

Rates at checkout is a tool for merchants to display up-to-date shipping estimates based on what's in their customers cart and where they’re shipping to. Merchants set up curated shipping options for customers in the checkout flow based on data in the shopping cart. The request must include the to address and item information. Optional fields are the from address and package information. If the optional fields are not included, the service will use the default address and/or package configured for rates at checkout. The response is a list of shipping options based on the Service Group configuration. (see Service Group configuration for details).

Schemas
Operations

Shippo Accounts

Shippo Accounts are used by Shippo Platform Accounts to create and manage Managed Shippo Accounts. Managed Shippo Accounts are headless accounts that represent your customers. They are opaque to your end customers, meaning customers do not need to create their own Shippo login or have a billing relationship with Shippo. They can be used by marketplaces, e-commerce platforms, and third-party logistics providers who want to offer, seamless, built-in shipping functionality to their customers. See our guide for more details.

Schemas
Operations

Carriers

TokenCarrier name
airterraAirterra
apc_postalAPC Postal
apgAPG
aramexAramex
asendia_usAsendia US
australia_postAustralia Post (also used for Startrack)
axlehireJitsu
better_trucksBetterTrucks
borderguruBorderGuru
boxberryBoxberry
bringBring (also used for Posten Norge)
canada_postCanada Post
cdlCDL
chronopostChronopost
collect_plusCollectPlus
correios_brCorreiosBR
correos_espanaCorreos España
colissimoColissimo
deutsche_postDeutsche Post
dhl_beneluxDHL Benelux
dhl_ecommerceDHL eCommerce
dhl_expressDHL Express
dhl_germany_c2cDHL Germany C2C
dhl_germanyDHL Germany
dpd_deDPD GERMANY
dpd_ukDPD UK
estafetaEstafeta
fastway_australiaAramex
fedexFedEx
globegisticsGlobegistics (now Asendia)
gls_usGLS US
gophrGophr
gsoGSO
hermes_germany_b2cHermes Germany B2C
hermes_ukEvri UK
hongkong_postHongkong Post
lasershipLaserShip
lsoLSO
mondial_relayMondial Relay
new_zealand_postNew Zealand Post (also used for Pace and CourierPost)
nippon_expressNippon Express
ontracOnTrac
parcelforceParcelforce
passportPassport
pcfPCF
poste_italianePoste Italiane
postiPosti
purolatorPurolator
royal_mailRoyal Mail
royal_mail_sfRoyal Mail Storefeeder
rr_donnelleyePost Global
russian_postRussian Post
skypostalSkyPostal
stuartStuart
swyftSwyft
udsUDS (United Delivery Service)
upsUPS
uspsUSPS
vehoVeho

Service Levels

Service levels represent the shipping service type for each carrier. Use the tokens below when creating shipments.

Parcel Templates

A predefined package used by one or multiple carriers. When a template is given, the parcel dimensions do not have to be sent - the dimensions below will instead be used. The parcel weight is not affected by the use of a template.

Address Validation Source

Source of the address validation message.

Allowed values:

  • Shippo Address Validator
  • UPS

Address Validation Codes

Validation result codes returned by the address validation service.

Allowed values:

  • verification_error
  • unknown_street
  • component_mismatch_error
  • multiple_match
  • sub_premise_number_invalid
  • sub_premise_number_missing
  • premise_number_invalid
  • premise_number_missing
  • box_number_invalid
  • box_number_missing
  • pmb_number_missing
  • postal_code_change
  • administrative_area_change
  • locality_change
  • dependent_locality_change
  • street_name_change
  • street_type_change
  • street_directional_change
  • sub_premise_type_change
  • sub_premise_number_change
  • double_dependent_locality_change
  • subadministrative_area_change
  • subnational_area_change
  • po_box_change
  • premise_type_change
  • house_number_change
  • organization_change
  • extraneous_information
  • usps_door_inaccessible
  • administrative_area_partial
  • city_partial
  • street_partial
  • building_partial
  • subpremise_partial
  • administrative_area_full
  • city_full
  • thoroughfare_full
  • premises_full
  • subpremise_full
  • geocoded_street
  • geocoded_neighborhood
  • geocoded_community
  • geocoded_state
  • geocoded_rooftop
  • geocoded_interpolated_rooftop
  • invalid_postal_code
  • postal_code_not_found
  • empty_request
  • service_error
  • street_detail_missing
  • Invalid City/State/Zip
  • Default Match
  • Unknown Street
  • Address Not Found
  • Non-Deliverable ZIP4
  • Multiple Responses
  • Invalid Dual Address
  • Invalid State
  • Invalid City
  • Ambiguous Address

Customs Declaration B13A Filing Option

B13A Option details are obtained by filing a B13A Canada Export Declaration via the Canadian Export Reporting System (CERS). More information on reporting commercial exports from Canada.

Allowed values:

  • FILED_ELECTRONICALLY
  • SUMMARY_REPORTING
  • NOT_REQUIRED

Customs Declaration Contents Type

Type of goods of the shipment.

Allowed values:

  • DOCUMENTS
  • GIFT
  • SAMPLE
  • MERCHANDISE
  • HUMANITARIAN_DONATION
  • RETURN_MERCHANDISE
  • OTHER

Customs Declaration EEL/PFC

EEL / PFC type of the shipment. For most shipments from the US to CA, NOEEI_30_36 is applicable; for most other shipments from the US, NOEEI_30_37_a is applicable.

Allowed values:

  • NOEEI_30_37_a
  • NOEEI_30_37_h
  • NOEEI_30_37_f
  • NOEEI_30_36
  • AES_ITN

Customs Declaration Incoterm

The incoterm reference of the shipment. FCA is available for DHL Express and FedEx only. eDAP is available for DPD UK only. DAP is available for DHL Express and DPD UK. If expecting DAP for other carriers, please use DDU.

Allowed values:

  • DDP
  • DDU
  • FCA
  • DAP
  • eDAP

Customs Declaration Non Delivery Option

Indicates how the carrier should proceed in case the shipment can't be delivered.

Allowed values:

  • ABANDON
  • RETURN