eHub

API Reference

API Versioning

Authentication

Accounts

Test

A successful pong will indicate that eHub is up and running

Ping

Rates

Quickly retrieve rates for your connected carrier accounts. You can filter based on service or carrier. Include as much information as possible for the most accurate results.

Rate Request

Create, update, retrieve, and cancel shipments.

Shipments

Guides for eHub's Shipment Functionality

Create a shipment in the system and ship it all at once. You will buy and get a label from this endpoint.

Create and Ship a Shipment

Create multiple shipments in the system and ship them all at once. This endpoint will buy and return labels. Maximum number of shipments in the request body is 10.

Create and Ship Multiple Shipments

Retrieve a Shipment

Cancel a shipment that has been created. This will void the label. If the label is still received by the carrier and scanned, your account will still be charged. Since USPS is prepay they will hold funds for 30 days to confirm the label was not used before issuing a refund. If you need to cancel a shipment that has already been shipped, you will need to contact the carrier directly.

Cancel a Shipment

Search for a list of shipments based on the provided filters.

List Shipments

Validate an address

GDE shipments can have long periods of time between label creation and being inducted into the USPS postal stream. To keep your customers informed, this endpoint will allow you to create tracking events for the shipment to show package movement to your customer.\n\n Only tracking events for USPS tracking codes 80, 81, and 82 are supported.

Create Tracking Events for a Shipment

GDE shipments can have long periods of time between label creation and being inducted into the USPS postal stream. To keep your customers informed, this endpoint will allow you to create tracking events for multiple shipments to show package movement to your customer.\n\n Only tracking events for USPS tracking codes 80, 81, and 82 are supported.

Create Tracking Events for Multiple Shipments

Manage batches, manifests, and end of day scan forms.

Batches and Manifests

List Shipment Batches

Use this endpoint to generate a daily manifest or scan form. Some carriers have up to a 15 minute delay generating the physical file. If a pdf isn't returned in the response but it was successful, wait a few minutes and try a GET. Only include shipment_ids for a single carrier at a time.

Create a Shipments Batch

Creates a separate batch for each shipping service provider that supports daily batches. Shipments that are already part of a batch are not included.

Create Batches for a Specific Date

Retrieve a Batch

Pickups

List Pickups

Check Pickup Availability for Location

Request a New Pickup

Retrieve a Scheduled Pickup

Cancel a Pickup

Retrieve orders, order updates, and mark orders shipped in their eCommerce system.

Order Stores

Use this endpoint to list of all the order stores connected to your eHub account.

List Order Stores

Retrieve a list of orders for a specific order store. The status filter allows you to filter by the order's shipment_status.

List Orders From an Order Store

Retrieve a single order for an order store. You must provide the order_number.

Retrieve an Order From an Order Store

Marks the order as shipped/fulfilled. Some integrations allow us to mark the order fulfilled in the e-commerce system and send across shipment information. Check the order store in the eHub portal to see if this functionality is supported.

Ship an Order

Marks the order shipment as not shipped/fulfilled. Some integrations allow us to mark the order unfulfilled in the e-commerce system. Check the order store in the eHub portal to see if this functionality is supported.

Cancel an Order's Shipment

This endpoint allows you to create orders saved to eHub's database. This is only allowed with "Custom" order stores.

Create Custom Orders

This endpoint allows you to update an order saved to eHub's database. This is only allowed with "Custom" order stores created with the POST endpoint. You must provide the order_number

Update a Custom Order

See what services your account has access to.

Services

Get a list of services and their IDs. service_id is a required field when trying to create a shipping label.

Retrieve Services

Find out zone information for a USPS service when you provide the to and from postal codes.

Find Zone

Check the status of connected carrier APIs.

Status

See the status of connected carrier services.

Service Statuses

Get reports about meter transactions and shipment adjustments.

Reports

When the Post Office finds discrepancies from the information reported to them when generating the label and the physical package they will create adjustments to refund or charge your meter. This report will show you the adjustments the USPS has reported for your shipments.

Shipment Adjustments

Meter Transactions

Subscribe to webhooks to receive notifications about tracking events or payment statuses.

Webhook Subscriptions

List Subscriptions

### Tracking event payload example
```
{
  "subscription_type": "shipment_tracking",
  "status": "active",
  "payload": [
    {
      "shipment_id": 115,
      "tracking_number": "9400109205328003425036",
      "tracking_event_id": 539,
      "parcel_id": 115,
      "code": "01",
      "secondary_code": "01",
      "description": "Delivered, In/At Mailbox",
      "event_timestamp": "2018-11-13T00:00:00.000Z",
      "city": "New Oceane",
      "state": "CA",
      "postal_code": "34668-2801",
      "country": "US"
    },
    {
      "shipment_id": 115,
      "tracking_number": "9400109205328003425036",
      "tracking_event_id": 540,
      "parcel_id": 115,
      "code": "OF",
      "secondary_code": null,
      "description": "Out for Delivery",
      "event_timestamp": "2018-11-12T19:00:24.000Z",
      "city": "Lake Jett",
      "state": "LA",
      "postal_code": "91251-7728",
      "country": "US"
    }
  ]
}
```

**code** and **secondary_code** vary by carrier. For USPS the codes are documented in Publication 199, Appendix G-4 (https://postalpro.usps.com/impbimplementationguide).


### Payment status event payload example
```
{
  "subscription_type": "payment_status",
  "payload": [
    {
      "payment_method_id": 0,
      "payment_transaction_id": 0,
      "gateway_txn_reference": "string",
      "transaction_time": "2020-05-14T15:56:58.550Z",
      "amount": 0,
      "type": "string",
      "status": "string"
    }
  ]
}
```


Create a Subscription

Update a Subscription

Retrieve a Subscription

Delete a Subscription

Payment Methods

List Payment Methods

Create a New Payment Method

Update a Payment Method

Retrieve a Payment Method

Customers

List Customers

Retrieve a Customer

Orchestrate

Create Order, Rate Shop and Ship

Rate Shop and Ship an existing Order

Rate Shop and Ship a Shipment

Default

eHub API

Token

Production

Sandbox

<h3 class="slate-h3 " >Introduction</h3><p class="slate-p " >eHub is built to help systems optimize order fulfillment with powerful API functionality. Key features include checking shipping rates, purchasing labels, generating manifests, and consolidating orders from multiple ecommerce platforms.</p><div class="slate-hr"><hr contenteditable="false" class="slate-HrElement-hr"/></div><p class="slate-p " ></p><h3 class="slate-h3 " >API Overview</h3><p class="slate-p " >The eHub API follows REST principles, making it accessible and easy to use through standard HTTP methods. This guide will walk you through available endpoints, request and response formats, and best practices to help you get the most out of the API.</p><h3 class="slate-h3 " ></h3><h3 class="slate-h3 " >Supported Request Body Content Types</h3><p class="slate-p " >The eHub API supports multiple content types for request bodies, ensuring flexibility and compatibility with different data formats. Ensure the Content-Type header in your requests matches the format of your request body.</p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">Accepted Content Types:</div><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative"><code class="slate-code">application/json</code></div></li><li class="slate-li " ><div style="position:relative"><code class="slate-code">application/xml</code></div></li><li class="slate-li " ><div style="position:relative"><code class="slate-code">application/x-www-form-urlencoded</code></div></li></ul></li></ul><p class="slate-p " >Depending on the endpoint, the required content type may vary.  Check the corresponding endpoint documentation for correct usage.</p><p class="slate-p " ></p><h3 class="slate-h3 " >Rate Limiting and Throttling</h3><p class="slate-p " >The eHub API is optimized to handle high volumes of requests with minimal rate limiting or throttling. </p><p class="slate-p " >While no strict caps are enforced, for optimal performance, it&apos;s recommended to limit parallel requests to a maximum of 10 per API token. Following this guideline helps ensure efficient operation and system reliability.</p><div class="slate-hr"><hr contenteditable="false" class="slate-HrElement-hr"/></div><p class="slate-p " >By following these guidelines, you can ensure the best performance and reliability when using the eHub API.</p><p class="slate-p " ></p><p class="slate-p " ></p>

eHub is built to help systems optimize order fulfillment with powerful API functionality. Key features include checking shipping rates, purchasing labels, generating manifests, and consolidating orders from multiple ecommerce platforms.

The eHub API follows REST principles, making it accessible and easy to use through standard HTTP methods. This guide will walk you through available endpoints, request and response formats, and best practices to help you get the most out of the API.

The eHub API supports multiple content types for request bodies, ensuring flexibility and compatibility with different data formats. Ensure the Content-Type header in your requests matches the format of your request body.

Depending on the endpoint, the required content type may vary.  Check the corresponding endpoint documentation for correct usage.

The eHub API is optimized to handle high volumes of requests with minimal rate limiting or throttling. 

While no strict caps are enforced, for optimal performance, it's recommended to limit parallel requests to a maximum of 10 per API token. Following this guideline helps ensure efficient operation and system reliability.

By following these guidelines, you can ensure the best performance and reliability when using the eHub API.

<p class="slate-p " >The eHub API uses versioning to maintain backward compatibility, allowing new features and updates to be introduced without disrupting existing integrations. Each version is embedded within the URL path, enabling developers to target specific API versions for their applications. </p><div class="slate-hr"><hr contenteditable="false" class="slate-HrElement-hr"/></div><p class="slate-p " ></p><h3 class="slate-h3 " >Current Version</h3><p class="slate-p " >The latest available version is <strong class="slate-bold">v2</strong>. You can access this version by appending the following path to the base URL:</p><div class="code-block-wrapper"  style="width:100%" ><div class="code-block-header">Plain text</div><pre class="slate-CodeBlockElement slate-code_block"><textarea id="publishedPageCodeblock" style="display:none !important; visibility: hidden; opacity: 0; width: 1px; height: 1px;" type="hidden"> </textarea><code class="language- keep-markup drop-tokens"><div class="slate-code_line">/api/v2/</div></code></pre></div><p class="slate-p " >For example, API request URL would look something like this:</p><p class="slate-p " ><code class="slate-code">https://api.ehub.com/api/v2/{specific_endpoint}</code></p><p class="slate-p " ></p><h3 class="slate-h3 " >Versioning Strategy</h3><p class="slate-p " >When a new version is released, the previous version remains available to ensure the continuity of your current integration. This approach allows flexibility to upgrade to the latest version when you&apos;re ready, allowing you to leverage new features and improvements without disrupting your existing processes. </p><p class="slate-p " ></p>

The eHub API uses versioning to maintain backward compatibility, allowing new features and updates to be introduced without disrupting existing integrations. Each version is embedded within the URL path, enabling developers to target specific API versions for their applications. 

. You can access this version by appending the following path to the base URL:

For example, API request URL would look something like this:

https://api.ehub.com/api/v2/{specific_endpoint}

When a new version is released, the previous version remains available to ensure the continuity of your current integration. This approach allows flexibility to upgrade to the latest version when you're ready, allowing you to leverage new features and improvements without disrupting your existing processes. 

All requests to the eHub API require authentication via Bearer Token, referred to as an API key in this documentation. each user receives a unique API key, ensuring individual access. If multiple users have API access within the same account, each user will have their own API key.

To be assigned an API key, your user account must have the 

. To view the API keys for other users within the eHub account, your account must have the 

You can copy the API key with one click using the copy button to the right of the key.

Once you have obtained your API key, include it in the 

 header of your HTTP requests. The token must be prefixed with the word 

 followed by a space, formatted like this:

<p class="slate-p " ></p><p class="slate-p " >eHub offers a flexible <strong class="slate-bold">parent-child account structure</strong> that enables users with the appropriate permissions on a parent account to make API requests on behalf of child accounts. This is particularly advantageous for businesses such as 3PLs that manage multiple customers, each with its own shipping carriers and eCommerce platform integrations.</p><p class="slate-p " ></p><h2 class="slate-h2 " ><strong class="slate-bold">API Request Using Parent-Child Relationship</strong></h2><p class="slate-p " ></p><p class="slate-p " >By leveraging the parent-child relationship, the parent account can make API requests on behalf of the child account using <strong class="slate-bold">the parent account&apos;s API key</strong>, but targeting the <strong class="slate-bold">child account&apos;s unique ID</strong>. This avoids the hassle of managing multiple API keys for each child account. </p><p class="slate-p " ></p><h2 class="slate-h2 " ><strong class="slate-bold">Benefits of the Parent-Child Structure</strong></h2><p class="slate-p " ></p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Separation of Data</strong>: Each child account maintains its own set of connections and data, keeping customer-specific data isolated.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Centralized Management</strong>: The parent account can easily manage all child accounts using a single API key.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Simplified API Requests</strong>: You can execute API requests for child accounts by simply specifying the child account&apos;s ID.</div></li></ul><p class="slate-p " ></p><h2 class="slate-h2 " ><strong class="slate-bold">Endpoints Available for Parent-Child API Requests</strong></h2><p class="slate-p " ></p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative"><a href="66a7c81ff9d1d947f54084fd" target="">Rates</a></div></li><li class="slate-li " ><div style="position:relative"><a href="66a7c81ff9d1d947f54084cf" target="">Shipments</a></div></li><li class="slate-li " ><div style="position:relative"><a href="66a7c81ff9d1d947f5408531" target="">Order Stores</a></div></li></ul><p class="slate-p " ></p><h2 class="slate-h2 " ><strong class="slate-bold">Use Case Example</strong></h2><p class="slate-p " ></p><p class="slate-p " >For instance, if your customer &quot;Child Company A&quot; uses <strong class="slate-bold">WooCommerce</strong> and has its own <strong class="slate-bold">UPS</strong> shipping account, you can set up a child account in eHub specifically for that customer. This ensures that <strong class="slate-bold">all of the data and integrations remain exclusive</strong> to that child account, creating a clean separation between different customer setups.</p><p class="slate-p " ></p><p class="slate-p " >If the child account&apos;s customer ID is <strong class="slate-bold">452</strong>, then the parent would make their API request like this: </p><div class="code-block-wrapper"  style="width:60%" ><div class="code-block-header">CURL</div><pre class="slate-CodeBlockElement slate-code_block"><textarea id="publishedPageCodeblock" style="display:none !important; visibility: hidden; opacity: 0; width: 1px; height: 1px;" type="hidden"> </textarea><code class="language-shell keep-markup drop-tokens"><div class="slate-code_line">curl --request GET \</div><div class="slate-code_line">	--url https://api.ehub.com/api/v2/cusotmers/452/order_stores \</div></code></pre></div><p class="slate-p " >The response to this request will show all eCommerce integration connections for child customer 452.</p>

 that enables users with the appropriate permissions on a parent account to make API requests on behalf of child accounts. This is particularly advantageous for businesses such as 3PLs that manage multiple customers, each with its own shipping carriers and eCommerce platform integrations.

API Request Using Parent-Child Relationship

By leveraging the parent-child relationship, the parent account can make API requests on behalf of the child account using 

. This avoids the hassle of managing multiple API keys for each child account. 

Endpoints Available for Parent-Child API Requests

For instance, if your customer "Child Company A" uses 

 shipping account, you can set up a child account in eHub specifically for that customer. This ensures that 

all of the data and integrations remain exclusive

 to that child account, creating a clean separation between different customer setups.

, then the parent would make their API request like this: 

The response to this request will show all eCommerce integration connections for child customer 452.

<p class="slate-p " ></p><h3 class="slate-h3 " >Ping-Pong Test</h3><p class="slate-p " ></p><p class="slate-p " >The Ping Pong Test is a straightforward method used to check the health and availability of an API or system. By sending a &quot;ping&quot; request, the client asks the server if it&apos;s operational. If the server is functioning properly, it responds with a &quot;pong.&quot; This lightweight request-response mechanism allows for quick diagnostics to confirm that the API is up and running.</p><p class="slate-p " ></p><h3 class="slate-h3 " >Benefits of the Ping Pong Test:</h3><p class="slate-p " ></p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">System Health Checks</strong>: Ensures the API is operational.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Connectivity Tests</strong>: Verifies successful communication between the client and server.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Troubleshooting</strong>: Quickly identifies whether an issue is related to system downtime or connectivity problems.</div></li></ul><p class="slate-p " ></p><div class="slate-hr"><hr contenteditable="false" class="slate-HrElement-hr"/></div><p class="slate-p " ></p><p class="slate-p " >For eHub, the Ping Pong Test helps users ensure the API is online and responsive before moving forward with more complex API calls.</p><p class="slate-p " ></p><p class="slate-p " ></p><p class="slate-p " ></p>

The Ping Pong Test is a straightforward method used to check the health and availability of an API or system. By sending a "ping" request, the client asks the server if it's operational. If the server is functioning properly, it responds with a "pong." This lightweight request-response mechanism allows for quick diagnostics to confirm that the API is up and running.

For eHub, the Ping Pong Test helps users ensure the API is online and responsive before moving forward with more complex API calls.

<p class="slate-p " ></p><p class="slate-p " >To successfully retrieve rates, you must provide key details. While the shipament object can include additional parameters, the following example highlights the minimum information required to generate accurate rates. The more specific your shipment details are, the more precise your rate results will be. For more information, please refer to the <a href="rates/rate-request" target="_self"><strong class="slate-bold">Rate Request</strong></a> page for more details and parameters.</p><p class="slate-p " ></p><h3 class="slate-h3 " ><strong class="slate-bold">Minimum Shipment Details (JSON Example)</strong></h3><div class="code-block-wrapper"  style="width:60%" ><div class="code-block-header">Plain text</div><pre class="slate-CodeBlockElement slate-code_block"><textarea id="publishedPageCodeblock" style="display:none !important; visibility: hidden; opacity: 0; width: 1px; height: 1px;" type="hidden"> </textarea><code class="language-json keep-markup drop-tokens"><div class="slate-code_line">{</div><div class="slate-code_line">   &quot;shipment&quot;:{</div><div class="slate-code_line">      &quot;to_location&quot;:{</div><div class="slate-code_line">         &quot;first_name&quot;:&quot;string&quot;, // or company</div><div class="slate-code_line">         &quot;address1&quot;:&quot;string&quot;,</div><div class="slate-code_line">         &quot;city&quot;:&quot;string&quot;,</div><div class="slate-code_line">         &quot;state&quot;:&quot;string&quot;, // for a US state use the two-digit state code</div><div class="slate-code_line">         &quot;country&quot;:&quot;string&quot;, // two-digit country code</div><div class="slate-code_line">         &quot;postal_code&quot;:&quot;string&quot;,</div><div class="slate-code_line">         &quot;phone&quot;:&quot;string&quot;</div><div class="slate-code_line">      },      </div><div class="slate-code_line">      &quot;from_location&quot;:{</div><div class="slate-code_line">         &quot;company&quot;:&quot;Test Test&quot;, // or first_name</div><div class="slate-code_line">         &quot;address1&quot;:&quot;string&quot;,</div><div class="slate-code_line">         &quot;city&quot;:&quot;string&quot;,</div><div class="slate-code_line">         &quot;state&quot;:&quot;string&quot;,</div><div class="slate-code_line">         &quot;country&quot;:&quot;string&quot;,</div><div class="slate-code_line">         &quot;postal_code&quot;:&quot;string&quot;,</div><div class="slate-code_line">         &quot;phone&quot;:&quot;string&quot;</div><div class="slate-code_line">      },</div><div class="slate-code_line">      &quot;parcels&quot;:[</div><div class="slate-code_line">         {</div><div class="slate-code_line">            &quot;length&quot;:6.0, // inches</div><div class="slate-code_line">            &quot;width&quot;:2.0, // inches</div><div class="slate-code_line">            &quot;height&quot;:2.0, // inches</div><div class="slate-code_line">            &quot;weight&quot;:36.0, // ounces</div><div class="slate-code_line">            &quot;package_type&quot;:&quot;string&quot;,</div><div class="slate-code_line">         }</div><div class="slate-code_line">      ]</div><div class="slate-code_line">   }</div><div class="slate-code_line">}</div></code></pre></div><p class="slate-p " >A request containing only this data will return rates for all enabled services your account qualifies for.  For example, FedEx Ground and FedEx Home Delivery will not return for the same shipment since they are mutually exclusive depending on whether the destination (to_location) is residential or commercial.</p><p class="slate-p " >If you wish to narrow the results, you can include one of the following parameters within the shipment object.</p><p class="slate-p " ></p><p class="slate-p " ></p><h2 class="slate-h2 " >Service Filters</h2><p class="slate-p " >You can specify desired services using the <code class="slate-code">include_services</code> field, an array containing service IDs. The service IDs can be either an integer or a string that represents the ID of the service you want to retrieve rates for.</p><p class="slate-p " ></p><h3 class="slate-h3 " ><strong class="slate-bold">Service Filter Example (JSON)</strong></h3><div class="code-block-wrapper"  style="width:60%" ><div class="code-block-header">Plain text</div><pre class="slate-CodeBlockElement slate-code_block"><textarea id="publishedPageCodeblock" style="display:none !important; visibility: hidden; opacity: 0; width: 1px; height: 1px;" type="hidden"> </textarea><code class="language-json keep-markup drop-tokens"><div class="slate-code_line">{</div><div class="slate-code_line">	&quot;include_services&quot;: [</div><div class="slate-code_line">		1172, // USPS Ground Advantage</div><div class="slate-code_line">		&quot;686&quot; // USPS Parcel Select</div><div class="slate-code_line">	]</div><div class="slate-code_line">}</div></code></pre></div><p class="slate-p " >Including this array in your request will limit the response to rates for USPS Ground Advantage and USPS Parcel Select only.</p><p class="slate-p " ></p><p class="slate-p " ></p><h2 class="slate-h2 " >Carrier Filters</h2><p class="slate-p " >To include services from specific carriers only, use the <code class="slate-code">include_carriers</code> field:</p><p class="slate-p " ></p><h3 class="slate-h3 " ><strong class="slate-bold">Carrier Filter Example (JSON)</strong></h3><div class="code-block-wrapper"  style="width:60%" ><div class="code-block-header">Plain text</div><pre class="slate-CodeBlockElement slate-code_block"><textarea id="publishedPageCodeblock" style="display:none !important; visibility: hidden; opacity: 0; width: 1px; height: 1px;" type="hidden"> </textarea><code class="language-json keep-markup drop-tokens"><div class="slate-code_line">{
  &quot;include_carriers&quot;: [
    &quot;usps&quot;,
    &quot;fed_ex&quot;,
    &quot;dhl_ecommerce&quot;
  ]
}</div></code></pre></div><p class="slate-p " >To exclude services from specific carriers, use the <code class="slate-code">exclude_carriers</code> field:</p><p class="slate-p " ></p><h3 class="slate-h3 " ><strong class="slate-bold">Exclude Carrier Example (JSON)</strong></h3><div class="code-block-wrapper"  style="width:60%" ><div class="code-block-header">Plain text</div><pre class="slate-CodeBlockElement slate-code_block"><textarea id="publishedPageCodeblock" style="display:none !important; visibility: hidden; opacity: 0; width: 1px; height: 1px;" type="hidden"> </textarea><code class="language-json keep-markup drop-tokens"><div class="slate-code_line">{
  &quot;exclude_carriers&quot;: [
    &quot;ups&quot;,
    &quot;dhl_express&quot;
  ]
}</div></code></pre></div><p class="slate-p " >If you omit filtering parameters, all available services will be available for the given shipment, as no specific services or carriers are excluded.</p><p class="slate-p " ></p><h2 class="slate-h2 " >Warnings</h2><p class="slate-p " >If there are any issues retrieving rates, warnings or error messages from the carrier&apos;s API will be relayed back and stored in the <code class="slate-code">warnings</code>  array of the response body. This allows for a successful response even if one carrier encounters an issue while others return rates successfully.</p><p class="slate-p " ></p><h3 class="slate-h3 " ><strong class="slate-bold">Warning Example (JSON)</strong></h3><div class="code-block-wrapper"  style="width:60%" ><div class="code-block-header">Plain text</div><pre class="slate-CodeBlockElement slate-code_block"><textarea id="publishedPageCodeblock" style="display:none !important; visibility: hidden; opacity: 0; width: 1px; height: 1px;" type="hidden"> </textarea><code class="language-json keep-markup drop-tokens"><div class="slate-code_line">{
  &quot;warnings&quot;: [
    &quot;FedEx returned error: Destination postal code missing or invalid&quot;
  ]
}</div></code></pre></div><p class="slate-p " ></p><h2 class="slate-h2 " >How to Get FedEx OneRate Rates</h2><p class="slate-p " ></p><p class="slate-p " >To receive FedEx OneRate rates, you need to specify both the eligible package type and service based on the contract in the rating or shipment request. Follow these steps:</p><ol class="slate-ol " ><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Make a</strong> <code class="slate-code">GET /services</code> <strong class="slate-bold">Call</strong></div></li></ol><p class="slate-p " >In the response, find the service object relevant to the FedEx service that qualifies for FedEx OneRate under the OneRate contract. The service is usually FedEx 2Day but may vary depending on the contract. </p><p class="slate-p " ></p><h3 class="slate-h3 " ><strong class="slate-bold">Example</strong> <code class="slate-code">GET /services</code> <strong class="slate-bold">Response:</strong></h3><div class="code-block-wrapper"  style="width:60%" ><div class="code-block-header">Plain text</div><pre class="slate-CodeBlockElement slate-code_block"><textarea id="publishedPageCodeblock" style="display:none !important; visibility: hidden; opacity: 0; width: 1px; height: 1px;" type="hidden"> </textarea><code class="language-json keep-markup drop-tokens"><div class="slate-code_line">{</div><div class="slate-code_line">   &quot;services&quot;: [</div><div class="slate-code_line">      ...</div><div class="slate-code_line">      {</div><div class="slate-code_line">         &quot;service_id&quot;: 393, // &lt;------</div><div class="slate-code_line">         &quot;service&quot;: &quot;FEDEX_2_DAY&quot;,</div><div class="slate-code_line">         &quot;service_code&quot;: &quot;fedex_2day&quot;,</div><div class="slate-code_line">         &quot;carrier_code&quot;: &quot;fed_ex&quot;,</div><div class="slate-code_line">         &quot;category&quot;: &quot;shipping&quot;,</div><div class="slate-code_line">         &quot;package_types&quot;: [</div><div class="slate-code_line">            {</div><div class="slate-code_line">               &quot;type&quot;: &quot;fedex_pak&quot;, // &lt;------</div><div class="slate-code_line">               &quot;name&quot;: &quot;FedEx Pak&quot;</div><div class="slate-code_line">            }</div><div class="slate-code_line">         ],</div><div class="slate-code_line">         &quot;sort_order&quot;: null</div><div class="slate-code_line">      }</div><div class="slate-code_line">      ...</div><div class="slate-code_line">   ]</div><div class="slate-code_line">}</div></code></pre></div><p class="slate-p " >In the service object, check the <code class="slate-code">package_types</code> array to find the package type specific to the FedEx OneRate contract. Note the <code class="slate-code">services[i].package_types[i].type</code>, as it will be needed later.</p><div class="slate-code_line"></div><p class="slate-p " ><strong class="slate-bold">2. Use the</strong> <code class="slate-code">service_id</code> <strong class="slate-bold">and</strong> <code class="slate-code">package_type</code> <strong class="slate-bold">in the Rating Request</strong></p><p class="slate-p " >The <code class="slate-code">shipments.parcels[i].package_type</code> should be set to the package type agreed upon in the FedEx OneRate contract, such as <code class="slate-code">fedex_pak</code></p><p class="slate-p " ></p><h3 class="slate-h3 " ><strong class="slate-bold">Example Rating Request:</strong></h3><div class="code-block-wrapper"  style="width:60%" ><div class="code-block-header">Plain text</div><pre class="slate-CodeBlockElement slate-code_block"><textarea id="publishedPageCodeblock" style="display:none !important; visibility: hidden; opacity: 0; width: 1px; height: 1px;" type="hidden"> </textarea><code class="language-json keep-markup drop-tokens"><div class="slate-code_line">{</div><div class="slate-code_line">   &quot;shipment&quot;: {</div><div class="slate-code_line">      &quot;to_location&quot;: {...},</div><div class="slate-code_line">      &quot;return_location&quot;: {...},</div><div class="slate-code_line">      &quot;from_location&quot;: {...},</div><div class="slate-code_line">      &quot;parcels&quot;: [</div><div class="slate-code_line">         {</div><div class="slate-code_line">            &quot;length&quot;: 2.0,</div><div class="slate-code_line">            &quot;width&quot;: 2.0,</div><div class="slate-code_line">            &quot;height&quot;: 2.0,</div><div class="slate-code_line">            &quot;weight&quot;: 3.0,</div><div class="slate-code_line">            &quot;package_type&quot;: &quot;fedex_pak&quot;, // &lt;------</div><div class="slate-code_line">            &quot;parcel_items&quot;: [...]</div><div class="slate-code_line">         }</div><div class="slate-code_line">      ],</div><div class="slate-code_line">      &quot;include_services&quot;: [393] // &lt;------ fedex_2day</div><div class="slate-code_line">   }</div><div class="slate-code_line">}</div></code></pre></div><p class="slate-p " ></p><p class="slate-p " ></p>

To successfully retrieve rates, you must provide key details. While the shipament object can include additional parameters, the following example highlights the minimum information required to generate accurate rates. The more specific your shipment details are, the more precise your rate results will be. For more information, please refer to the 

A request containing only this data will return rates for all enabled services your account qualifies for.  For example, FedEx Ground and FedEx Home Delivery will not return for the same shipment since they are mutually exclusive depending on whether the destination (to_location) is residential or commercial.

If you wish to narrow the results, you can include one of the following parameters within the shipment object.

You can specify desired services using the 

 field, an array containing service IDs. The service IDs can be either an integer or a string that represents the ID of the service you want to retrieve rates for.

Including this array in your request will limit the response to rates for USPS Ground Advantage and USPS Parcel Select only.

To include services from specific carriers only, use the 

To exclude services from specific carriers, use the 

If you omit filtering parameters, all available services will be available for the given shipment, as no specific services or carriers are excluded.

If there are any issues retrieving rates, warnings or error messages from the carrier's API will be relayed back and stored in the 

  array of the response body. This allows for a successful response even if one carrier encounters an issue while others return rates successfully.

To receive FedEx OneRate rates, you need to specify both the eligible package type and service based on the contract in the rating or shipment request. Follow these steps:

In the response, find the service object relevant to the FedEx service that qualifies for FedEx OneRate under the OneRate contract. The service is usually FedEx 2Day but may vary depending on the contract. 

 array to find the package type specific to the FedEx OneRate contract. Note the 

 should be set to the package type agreed upon in the FedEx OneRate contract, such as 

<p class="slate-p " >Fill here with a summary of what can be done with eHub Shipment functionality.</p><p class="slate-p " ></p><div class="slate-hr"><hr contenteditable="false" class="slate-HrElement-hr"/></div><p class="slate-p " ></p><h3 class="slate-h3 " >Guides for eHub&apos;s Shipment Functionality</h3><p class="slate-p " ></p><h3 class="slate-h3 " ><a href="66a7c81ff9d1d947f54084cf/66d22453e0afc0ab4a75c81a/66d22460e0afc0ab4a75c86b" target=""><strong class="slate-bold">Domestic Shipping</strong></a></h3><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Create a Shipment</strong>: Initiates a new domestic shipment by providing the destination, origin, parcel details, and selecting a shipping service.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Multi-Parcel Shipments</strong>: Supports splitting a shipment into multiple parcels. Multiple labels will be returned, each with different tracking numbers.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Label Customization</strong>: Customize the label format (jpeg, png, zpl, etc.), size (4x6, 8.5x11, etc.), and add custom text or images.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Cancel a Shipment</strong>: Cancel the shipment and void the label before it’s manifested by the carrier. If successful, the status will return as <code class="slate-code">cancel_pending</code>.</div></li></ul><p class="slate-p " ></p><h3 class="slate-h3 " ><a href="66a7c81ff9d1d947f54084cf/66d22453e0afc0ab4a75c81a/66d22469e0afc0ab4a75c8c0" target=""><strong class="slate-bold">International Shipping</strong></a></h3><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Customs Information</strong>: When shipping internationally, you must include HS codes, EEL/PFC codes, and detailed customs data to comply with regulations.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Retrieve Customs PDF</strong>: Retrieve a customs document in PDF format, supported by certain carriers. Check for carrier availability of this feature.</div></li></ul><p class="slate-p " ></p><h3 class="slate-h3 " ><a href="66a7c81ff9d1d947f54084cf/66d22453e0afc0ab4a75c81a/66d2247ce0afc0ab4a75c923" target=""><strong class="slate-bold">Additional Tips</strong></a></h3><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Dangerous Goods</strong>: Specify hazmat codes in the parcel object to handle hazardous materials. Each parcel can contain only one type of hazardous material.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Advanced Labeling Features</strong>: Create custom tracking events for GDE shipments to show package movement even with long periods between label creation and USPS induction.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Rates Overview</strong>: Retrieve simplified and organized rates for created shipments, with options to filter by carrier and service level.</div></li></ul><p class="slate-p " ></p><h3 class="slate-h3 " ><a href="66a7c81ff9d1d947f54084cf/66d22453e0afc0ab4a75c81a/66d22484e0afc0ab4a75c980" target=""><strong class="slate-bold">Tracking</strong></a></h3><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Track Shipments</strong>: Retrieve tracking information manually via GET requests or set up a webhook for real-time updates.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Tracking Events</strong>: Create tracking events for GDE shipments to reflect package progress.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Retrieve Shipment Status</strong>: Check the status of shipments using eHub’s shipment ID.</div></li></ul><p class="slate-p " >Endorsements</p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">For USPS shipments ONLY.</div></li><li class="slate-li " ><div style="position:relative">Direct the driver on what to do if the package is undeliverable.</div></li><li class="slate-li " ><div style="position:relative">Enum Values:</div></li></ul><ol class="slate-ol " ><li class="slate-li " ><div style="position:relative">ADDRESS_CORRECTION - Package is returned to sender with the recipient&apos;s correct address. </div></li><li class="slate-li " ><div style="position:relative">CARRIER_LEAVE_IF_NO_RESPONSE - Package is left at the doorstep if the door is not answered. (does not require signature or recipient presence)</div></li><li class="slate-li " ><div style="position:relative">CHANGE_SERVICE - Sender is notified of an address change for the recipient.</div></li><li class="slate-li " ><div style="position:relative">FORWARDING_SERVICE - Redirect the package with a recipient&apos;s mail forwarding order if one has been filed.</div></li><li class="slate-li " ><div style="position:relative">RETURN_SERVICE - Return the package to the sender with the reason why the package couldn&apos;t be delivered.</div></li></ol><p class="slate-p " ></p><div class="slate-hr"><hr contenteditable="false" class="slate-HrElement-hr"/></div><p class="slate-p " ></p><h3 class="slate-h3 " ><strong class="slate-bold">Shipment Features</strong></h3><p class="slate-p " ></p><p class="slate-p " >eHub&apos;s Shipment API provides a powerful and flexible platform for managing all aspects of your shipping operations. With this functionality, you can:</p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative"><a href="66a7c81ff9d1d947f54084cf/66a7c81ff9d1d947f54084d3" target=""><strong class="slate-bold">Create and Ship Shipments</strong>:</a> Seamlessly create and process shipments by providing key details like addresses, parcel dimensions, and service levels. Easily generate shipping labels and track each shipment’s progress.</div></li><li class="slate-li " ><div style="position:relative"><a href="66a7c81ff9d1d947f54084cf/66a7c81ff9d1d947f54084d1" target=""><strong class="slate-bold">Create and Ship Multiple Shipments</strong>:</a> Efficiently manage high-volume shipping with the ability to create and ship multiple parcels at once, streamlining your workflow and reducing manual effort.</div></li><li class="slate-li " ><div style="position:relative"><a href="66a7c81ff9d1d947f54084cf/66a7c81ff9d1d947f54084e3" target=""><strong class="slate-bold">Retrieve a Shipment</strong>: </a>Access detailed information on any shipment with the shipment ID, providing visibility into shipping status and tracking events.</div></li><li class="slate-li " ><div style="position:relative"><a href="shipments/cancel-a-shipment" target="_self"><strong class="slate-bold">Cancel a Shipment</strong>:</a> Cancel shipments before they are processed by the carrier and void labels to avoid unnecessary charges. For USPS, manage refunds based on prepay conditions.</div></li><li class="slate-li " ><div style="position:relative"><a href="66a7c81ff9d1d947f54084cf/66a7c81ff9d1d947f54084d7" target="">Create a Shipment:</a> Create a shipment</div></li><li class="slate-li " ><div style="position:relative"><a href="66a7c81ff9d1d947f54084cf/66a7c81ff9d1d947f54084d5" target=""><strong class="slate-bold">List Shipments:</strong></a><strong class="slate-bold"> </strong>Discover how to retrieve a list of shipments using filters, making it easy to track, audit, and manage high-volume shipping operations.</div></li><li class="slate-li " ><div style="position:relative"><a href="66a7c81ff9d1d947f54084cf/66a7c81ff9d1d947f54084e5" target=""><strong class="slate-bold">Validate an Address</strong>:</a> Ensure addresses are accurate with address validation, preventing delivery issues and reducing the risk of returns or failed shipments.</div></li><li class="slate-li " ><div style="position:relative"><a href="66a7c81ff9d1d947f54084cf/66a7c81ff9d1d947f54084e1" target=""><strong class="slate-bold">Customs and International Shipping</strong>:</a> Simplify international shipping with support for customs data, including HS codes and customs PDF document retrieval for select service providers.</div></li><li class="slate-li " ><div style="position:relative"><a href="66a7c81ff9d1d947f54084cf/66a7c81ff9d1d947f54084d9" target=""><strong class="slate-bold">Track Shipments and Create Tracking Events</strong>:</a> Keep your customers informed with real-time tracking updates through GET requests or webhooks. Create custom tracking events for specific shipments like GDE, ensuring transparency even during long postal induction periods.</div></li><li class="slate-li " ><div style="position:relative"><a href="66a7c81ff9d1d947f54084cf/66a7c81ff9d1d947f54084db" target=""><strong class="slate-bold">Rate Management</strong>:</a> Retrieve and compare simplified shipping rates from various carriers, helping you make cost-effective decisions for each shipment.</div></li></ul><p class="slate-p " ></p><div class="slate-hr"><hr contenteditable="false" class="slate-HrElement-hr"/></div><p class="slate-p " ></p><p class="slate-p " >eHub’s Shipment functionality empowers businesses to streamline their shipping operations, manage high-volume orders, and ensure a smooth customer experience across domestic and international shipments.</p><p class="slate-p " ></p><p class="slate-p " ></p><p class="slate-p " ></p><p class="slate-p " ></p>

Fill here with a summary of what can be done with eHub Shipment functionality.

eHub's Shipment API provides a powerful and flexible platform for managing all aspects of your shipping operations. With this functionality, you can:

eHub’s Shipment functionality empowers businesses to streamline their shipping operations, manage high-volume orders, and ensure a smooth customer experience across domestic and international shipments.

<p class="slate-p " ></p><h3 class="slate-h3 " >Domestic Shipping</h3><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">Key requirements for creating a domestic shipment:</div><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">Vital details like destination and origin addresses.</div></li><li class="slate-li " ><div style="position:relative">Parcel dimensions and service ID selection.</div></li><li class="slate-li " ><div style="position:relative">Tips for retrieving rates when service ID is unknown.</div></li></ul></li></ul><p class="slate-p " ></p><h3 class="slate-h3 " >International Shipping</h3><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">Extra steps required for international shipments:</div><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">Importance of HS Codes and EEL/PFC codes.</div></li><li class="slate-li " ><div style="position:relative">Providing accurate customs data for compliance with regulations.</div></li><li class="slate-li " ><div style="position:relative">How to calculate declared value and handle shipments to U.S. territories and military locations.</div></li></ul></li></ul><p class="slate-p " ></p><h3 class="slate-h3 " >Additional Tips</h3><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">Advanced features and best practices:</div><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">Handling hazardous materials with hazmat codes.</div></li><li class="slate-li " ><div style="position:relative">Customizing labels with formats, sizes, text, and images.</div></li><li class="slate-li " ><div style="position:relative">Managing multi-parcel shipments and creating USPS test labels.</div></li></ul></li></ul><p class="slate-p " ></p><h3 class="slate-h3 " >Tracking</h3><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">How to track shipments using the API:</div><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">Manual tracking through GET requests.</div></li><li class="slate-li " ><div style="position:relative">Automated tracking through webhooks for real-time updates.</div></li><li class="slate-li " ><div style="position:relative">Examples of tracking event arrays.</div></li></ul></li></ul><p class="slate-p " ></p><div class="slate-hr"><hr contenteditable="false" class="slate-HrElement-hr"/></div><p class="slate-p " ></p><h3 class="slate-h3 " >Conclusion</h3><p class="slate-p " >eHub’s Shipment API makes shipping simple, whether you're sending domestic or international packages. With advanced features like label customization, hazmat handling, and real-time tracking, you can streamline your entire shipping process. Whether you're just starting out or handling complex shipments, these guides give you everything you need to succeed.</p><p class="slate-p " ></p>

eHub’s Shipment API makes shipping simple, whether you're sending domestic or international packages. With advanced features like label customization, hazmat handling, and real-time tracking, you can streamline your entire shipping process. Whether you're just starting out or handling complex shipments, these guides give you everything you need to succeed.

<p class="slate-p " ></p><p class="slate-p " >To successfully create and process a domestic shipment, you must provide the following essential details. While many additional parameters can be added to the shipment object, this example demonstrates the minimum information required to generate a label for a domestic shipment.</p><p class="slate-p " ></p><div class="code-block-wrapper"  style="width:60%" ><div class="code-block-header">Plain text</div><pre class="slate-CodeBlockElement slate-code_block" data-content=''><code class="language-json keep-markup drop-tokens"><div class="slate-code_line">{</div><div class="slate-code_line">   "shipment":{</div><div class="slate-code_line">      "to_location":{</div><div class="slate-code_line">         "first_name":"string", // or company</div><div class="slate-code_line">         "address1":"string",</div><div class="slate-code_line">         "city":"string",</div><div class="slate-code_line">         "state":"string", // for a US state use the two-digit state code</div><div class="slate-code_line">         "country":"string", // two-digit country code</div><div class="slate-code_line">         "postal_code":"string",</div><div class="slate-code_line">         "phone":"string"</div><div class="slate-code_line">      },      </div><div class="slate-code_line">      "from_location":{</div><div class="slate-code_line">         "company":"Test Test", // or first_name</div><div class="slate-code_line">         "address1":"string",</div><div class="slate-code_line">         "city":"string",</div><div class="slate-code_line">         "state":"string",</div><div class="slate-code_line">         "country":"string",</div><div class="slate-code_line">         "postal_code":"string",</div><div class="slate-code_line">         "phone":"string"</div><div class="slate-code_line">      },</div><div class="slate-code_line">      "parcels":[</div><div class="slate-code_line">         {</div><div class="slate-code_line">            "length":17.0,</div><div class="slate-code_line">            "width":20.0,</div><div class="slate-code_line">            "height":11.0,</div><div class="slate-code_line">            "weight":240.0,</div><div class="slate-code_line">            "package_type":"string"</div><div class="slate-code_line">         }</div><div class="slate-code_line">      ],</div><div class="slate-code_line">      "service_id":1172</div><div class="slate-code_line">   }</div><div class="slate-code_line">}</div></code></pre></div><p class="slate-p " ></p><h3 class="slate-h3 " >Shipment Object Breakdown</h3><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Shipment Object: </strong>The primary container for all shipment-related details.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">to_location / from_location:</strong> The <code class="slate-code">to_location</code> and <code class="slate-code">from_location</code> objects are required to define the destination and origin addresses.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">parcels:</strong> The <code class="slate-code">parcels</code> array is necessary to specify the package’s dimensions using the fields <code class="slate-code">length</code>, <code class="slate-code">width</code>, <code class="slate-code">height</code>, <code class="slate-code">weight</code>, and <code class="slate-code">package_type.</code></div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">service_id:</strong> The <code class="slate-code">service_id</code> identifies the shipping service used (e.g., USPS Priority Mail, UPS Ground, or FedEx 2Day).</div><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">If you're unsure of the correct <code class="slate-code">service_id</code> needed, use the Rates endpoint to retrieve available rates and service IDs.</div></li></ul></li></ul><p class="slate-p " ></p><h3 class="slate-h3 " >Errors and Warnings</h3><p class="slate-p " >If any of the required fields are omitted, the system will return an error. For example, if the <code class="slate-code">parcel</code> object is missing, you'll see an error message like this:</p><p class="slate-p " ><strong class="slate-bold">Example Error:</strong> <strong class="slate-bold">Status:</strong><em class="slate-italic"><strong class="slate-bold"> </strong></em><em class="slate-italic">500 - Internal Server Error</em></p><p class="slate-p " ></p><div class="code-block-wrapper"  style="width:60%" ><div class="code-block-header">Plain text</div><pre class="slate-CodeBlockElement slate-code_block" data-content=''><code class="language-json keep-markup drop-tokens"><div class="slate-code_line">{</div><div class="slate-code_line">    "status": "error",</div><div class="slate-code_line">    "error_code": "parcel.missing_parcels",</div><div class="slate-code_line">    "error_message": "Missing parcels for request. At least one parcel is required."</div><div class="slate-code_line"></div><div class="slate-code_line">}</div></code></pre></div><h3 class="slate-h3 " >
US Territories and Military Shipments</h3><p class="slate-p " >Shipping to a U.S. territory or military destination (APO/FPO) requires using a domestic service with USPS. However, the shipment object also needs additional information such as an HS Tariff Code or EEL/PFC code. Refer to the <a href="shipments/guides-1/international-shipping" target="_self">International Shipments</a> section for more details.</p><p class="slate-p " ></p><p class="slate-p " ></p>

To successfully create and process a domestic shipment, you must provide the following essential details. While many additional parameters can be added to the shipment object, this example demonstrates the minimum information required to generate a label for a domestic shipment.

If any of the required fields are omitted, the system will return an error. For example, if the 

 object is missing, you'll see an error message like this:

Shipping to a U.S. territory or military destination (APO/FPO) requires using a domestic service with USPS. However, the shipment object also needs additional information such as an HS Tariff Code or EEL/PFC code. Refer to the 

Domestic Shipping

<p class="slate-p " ></p><p class="slate-p " >When shipping internationally, it's critical to provide comprehensive information about your product in your shipment request. Incomplete data can lead to customs rejection, product loss, unhappy customers, and wasted postage due to destination country regulations. For any questions about international shipping, feel free to contact your sales representative or reach out to support at <a href="" target="_blank">support@ehub.com</a>.</p><p class="slate-p " ></p><h3 class="slate-h3 " >HS Codes</h3><p class="slate-p " >Harmonized System Codes (HS Codes), also known as Tariff Codes, are required details on customs forms. These codes are mandatory for most USPS customs forms and are also necessary for certain FedEx, UPS, DHL, and other carrier forms. For further details, please refer to <a href="https://www.trade.gov/harmonized-system-hs-codes" target="_new">Harmonized System (HS) Codes</a>.</p><p class="slate-p " ></p><h3 class="slate-h3 " >EEL Codes vs PFC Codes</h3><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">If the package value exceeds $2,500.00, a PFC code is required instead of an EEL code.</div><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">Each object within the <code class="slate-code">parcel_items</code> array must include the <code class="slate-code">eel_pfc</code> field in its <code class="slate-code">customs_data</code> object.</div></li><li class="slate-li " ><div style="position:relative">The ITN will be formatted similarly to "AES X20120502123456". To acquire an ITN, visit the AESDirect website.</div></li></ul></li></ul><p class="slate-p " ></p><h3 class="slate-h3 " >Parcel Items and Customs Data</h3><p class="slate-p " >Customs information for international shipments is included in the <code class="slate-code">parcel_items</code> array, with each <code class="slate-code">parcel_item</code> object containing a nested <code class="slate-code">customs_data</code> object. Refer to the example below:</p><p class="slate-p " ></p><div class="code-block-wrapper"  style="width:60%" ><div class="code-block-header">Plain text</div><pre class="slate-CodeBlockElement slate-code_block" data-content=''><code class="language-json keep-markup drop-tokens"><div class="slate-code_line">"parcel_items": [</div><div class="slate-code_line">  {</div><div class="slate-code_line">    "name": "string",</div><div class="slate-code_line">    "description": "string",</div><div class="slate-code_line">    "weight": 0.0,</div><div class="slate-code_line">    "quantity": 0.0,</div><div class="slate-code_line">    "price": 0.0,</div><div class="slate-code_line">    "cost": 0.0,</div><div class="slate-code_line">    "customs_data": {</div><div class="slate-code_line">      "content_type": "string",</div><div class="slate-code_line">      "no_delivery": "string",</div><div class="slate-code_line">      "hs_tariff_code": "string",</div><div class="slate-code_line">      "value": 0.0,</div><div class="slate-code_line">      "eel_pfc": "string"</div><div class="slate-code_line">    }</div><div class="slate-code_line">  }</div><div class="slate-code_line">]</div></code></pre></div><p class="slate-p " >Depending on the destination country, label creation may fail if the <code class="slate-code">hs_code</code> or <code class="slate-code">eel_pfc</code> is missing. Even if the destination country doesn’t require these codes, it’s recommended to include them along with an accurate description to prevent delays or errors with customs agencies.</p><h3 class="slate-h3 " >

Declared Value</h3><p class="slate-p " >eHub calculates the declared value of your goods based on the following logic:</p><div class="code-block-wrapper"  style="width:60%" ><div class="code-block-header">Plain text</div><pre class="slate-CodeBlockElement slate-code_block" data-content=''><code class="language-javascript keep-markup drop-tokens"><div class="slate-code_line">let declared_value;</div><div class="slate-code_line">if (parcel_item.price) {</div><div class="slate-code_line">    declared_value = parcel_item.price * parcel_item.quantity;</div><div class="slate-code_line">} else {</div><div class="slate-code_line">    declared_value = parcel_item.customs_data.value * parcel_item.quantity;</div><div class="slate-code_line">}</div></code></pre></div><h3 class="slate-h3 " >Example Scenario:</h3><p class="slate-p " >The <code class="slate-code">parcel_item.customs_data.value = 159.00</code> and the <code class="slate-code">parcel_item.quantity = 50.0</code>, the declared value of the parcel is $7,950.00</p><p class="slate-p " ></p><p class="slate-p " ></p>

When shipping internationally, it's critical to provide comprehensive information about your product in your shipment request. Incomplete data can lead to customs rejection, product loss, unhappy customers, and wasted postage due to destination country regulations. For any questions about international shipping, feel free to contact your sales representative or reach out to support at 

Harmonized System Codes (HS Codes), also known as Tariff Codes, are required details on customs forms. These codes are mandatory for most USPS customs forms and are also necessary for certain FedEx, UPS, DHL, and other carrier forms. For further details, please refer to 

Customs information for international shipments is included in the 

Depending on the destination country, label creation may fail if the 

 is missing. Even if the destination country doesn’t require these codes, it’s recommended to include them along with an accurate description to prevent delays or errors with customs agencies.

eHub calculates the declared value of your goods based on the following logic:

, the declared value of the parcel is $7,950.00

International Shipping

<p class="slate-p " ></p><h3 class="slate-h3 " >Dangerous Goods</h3><p class="slate-p " >To indicate that a parcel contains hazardous materials in a Shipment Creation request (POST <code class="slate-code">/shipments/ship</code>), include the following parameters in the <code class="slate-code">parcel</code> object of the shipment:</p><div class="code-block-wrapper"  style="width:60%" ><div class="code-block-header">Plain text</div><pre class="slate-CodeBlockElement slate-code_block" data-content=''><code class="language-json keep-markup drop-tokens"><div class="slate-code_line">"service_options": {</div><div class="slate-code_line">  "dangerous_goods": {</div><div class="slate-code_line">    "details": {</div><div class="slate-code_line">      "type": "CLASS_9_NEW_LITHIUM_DEVICE"</div><div class="slate-code_line">    }</div><div class="slate-code_line">  }</div><div class="slate-code_line">}</div></code></pre></div><p class="slate-p " >The hazmat code must be specified at <code class="slate-code">shipment.parcels[i].service_options.dangerous_goods.details.type</code>. Since each parcel can only contain one type of hazardous material, a multi-parcel shipment can be used to handle various hazmat materials and specify the appropriate hazmat code for each parcel.</p><p class="slate-p " ></p><h3 class="slate-h3 " >Shipping Label Customizations</h3><p class="slate-p " >Please note that although many customization options are generally available, they are dependent on the carrier's specifications and requirements. </p><p class="slate-p " >Each of these options is located in the main shipment body and should not be nested within any other object of the shipment request.</p><p class="slate-p " ></p><h3 class="slate-h3 " >Label Format</h3><p class="slate-p " >eHub can generate labels of different format types. <code class="slate-code">jpeg</code>, <code class="slate-code">png</code>, <code class="slate-code">pdf</code>, <code class="slate-code">zpl</code>, <code class="slate-code">epl2</code>, <code class="slate-code">gif</code>, and <code class="slate-code">tiff</code></p><p class="slate-p " >For best label quality, we recommend using the <code class="slate-code">zpl</code> format with a ZPL-compatible printer.</p><div class="code-block-wrapper"  style="width:60%" ><div class="code-block-header">Plain text</div><pre class="slate-CodeBlockElement slate-code_block" data-content=''><code class="language-json keep-markup drop-tokens"><div class="slate-code_line">"label_format": "zpl"</div></code></pre></div><p class="slate-p " ></p><h3 class="slate-h3 " >Label Size</h3><p class="slate-p " >Typically 4"x6" labels are used but eHub can generate labels with the following sizes. <code class="slate-code">'4x6'</code>, <code class="slate-code">'4x8'</code>, <code class="slate-code">'8x11'</code>, <code class="slate-code">'8.5x11'</code>, <code class="slate-code">'2 5/16x4'</code>, and <code class="slate-code">'3 7/16x5 3/16'</code></p><div class="code-block-wrapper"  style="width:60%" ><div class="code-block-header">Plain text</div><pre class="slate-CodeBlockElement slate-code_block" data-content=''><code class="language-json keep-markup drop-tokens"><div class="slate-code_line">"label_size": "4x6"</div></code></pre></div><p class="slate-p " ></p><h3 class="slate-h3 " >Label Text and Contents</h3><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative"><code class="slate-code">label_text1</code> /  <code class="slate-code">label_text2</code> - Custom text able to be printed on the label</div></li><li class="slate-li " ><div style="position:relative"><code class="slate-code">label_contents</code> This object allows for custom text or even an image to be added to the label.</div></li></ul><p class="slate-p " ><strong class="slate-bold">WARNING: </strong>Each carrier has strict guidelines regarding their shipping labels. Please reach out to support@ehub.com before attempting to utilize this feature.</p><div class="code-block-wrapper"  style="width:60%" ><div class="code-block-header">Plain text</div><pre class="slate-CodeBlockElement slate-code_block" data-content=''><code class="language-json keep-markup drop-tokens"><div class="slate-code_line">"label_contents": [
  {
    "label_content": {
      "type": "string",
      "text": "string",
      "base64_image": "string",
      "location": [
        0, 0 // X and Y coordinates
      ],
      "width": 0,
      "height": 0
    }
  }
]</div></code></pre></div><p class="slate-p " ></p><h2 class="slate-h2 " >Multi Parcel Shipments</h2><p class="slate-p " >Some carriers allow you to split a shipment into multiple parcels by passing several parcel objects within the <code class="slate-code">parcels</code> array. If supported, you will receive multiple labels with different tracking numbers. </p><p class="slate-p " >For any questions, contact <a href="" target="_blank">support@ehub.com</a>.</p><div class="code-block-wrapper"  style="width:60%" ><div class="code-block-header">Plain text</div><pre class="slate-CodeBlockElement slate-code_block" data-content=''><code class="language-json keep-markup drop-tokens"><div class="slate-code_line">"parcels":[</div><div class="slate-code_line">  {</div><div class="slate-code_line">    "name": "string",</div><div class="slate-code_line">    "length": 0.0,</div><div class="slate-code_line">    "width": 0.0,</div><div class="slate-code_line">    "height": 0.0,</div><div class="slate-code_line">    "weight": 0.0,</div><div class="slate-code_line">    ...</div><div class="slate-code_line">  },</div><div class="slate-code_line">  {</div><div class="slate-code_line">    "name": "string",</div><div class="slate-code_line">    "length": 0.0,</div><div class="slate-code_line">    "width": 0.0,</div><div class="slate-code_line">    "height": 0.0,</div><div class="slate-code_line">    "weight": 0.0,</div><div class="slate-code_line">    ...</div><div class="slate-code_line">  },</div><div class="slate-code_line">  {</div><div class="slate-code_line">    "name": "string",</div><div class="slate-code_line">    "length": 0.0,</div><div class="slate-code_line">    "width": 0.0,</div><div class="slate-code_line">    "height": 0.0,</div><div class="slate-code_line">    "weight": 0.0,</div><div class="slate-code_line">    ...</div><div class="slate-code_line">  },</div><div class="slate-code_line">]</div></code></pre></div><p class="slate-p " ></p><h2 class="slate-h2 " >USPS Test Labels</h2><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">All USPS test labels will have "VOID" printed all across the barcode</div></li><li class="slate-li " ><div style="position:relative">The top postage payment area will specify that it is a test label.</div></li><li class="slate-li " ><div style="position:relative">Test labels are not associated with a real Mailer ID or payment account (EPS) and cannot be accepted by the post office.</div></li><li class="slate-li " ><div style="position:relative">Attempting to cancel or void a test label typically results in an error due to USPS limitations. </div><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">While it’s recommended to develop functionality using test labels, ensure you test the cancellation process with a production label before going live.</div></li></ul></li></ul><p class="slate-p " ></p><h2 class="slate-h2 " ><strong class="slate-bold">
</strong>How to Create FedEx OneRate Labels</h2><p class="slate-p " ></p><p class="slate-p " >To create FedEx OneRate shipments, you must specify both the eligible package type and the service in the shipment request body, based on the applicable contract</p><ol class="slate-ol " ><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Specify the Package Type and Service</strong></div></li></ol><p class="slate-p " >Ensure the <code class="slate-code">package_type</code> corresponds to the FedEx OneRate contract, such as <code class="slate-code">fedex_pak</code>, and the <code class="slate-code">service_id</code> is based on the relevant service (usually <code class="slate-code">fedex_2day</code>).</p><p class="slate-p " ><strong class="slate-bold">2. Create the Shipment Request</strong></p><p class="slate-p " >Use both the corresponding FedEx OneRate <code class="slate-code">package_type</code> and <code class="slate-code">service_id</code> to create a valid shipment request for a FedEx OneRate shipment:</p><p class="slate-p " ></p><h3 class="slate-h3 " ><strong class="slate-bold">Shipment Request Example:</strong></h3><div class="code-block-wrapper"  style="width:60%" ><div class="code-block-header">Plain text</div><pre class="slate-CodeBlockElement slate-code_block" data-content=''><code class="language-json keep-markup drop-tokens"><div class="slate-code_line">{</div><div class="slate-code_line">   "shipment": {</div><div class="slate-code_line">      "to_location": {...},</div><div class="slate-code_line">      "return_location": {...},</div><div class="slate-code_line">      "from_location": {...},</div><div class="slate-code_line">      "parcels": [</div><div class="slate-code_line">         {</div><div class="slate-code_line">            "length": 2.0,</div><div class="slate-code_line">            "width": 2.0,</div><div class="slate-code_line">            "height": 2.0,</div><div class="slate-code_line">            "weight": 3.0,</div><div class="slate-code_line">            "package_type": "fedex_pak", // <------ Specified package type</div><div class="slate-code_line">            "parcel_items": [...]</div><div class="slate-code_line">         }</div><div class="slate-code_line">      ],</div><div class="slate-code_line">      "service_id": 393 // <------ FedEx service, e.g., fedex_2day</div><div class="slate-code_line">   }</div><div class="slate-code_line">}</div></code></pre></div><p class="slate-p " ></p><p class="slate-p " ></p>

To indicate that a parcel contains hazardous materials in a Shipment Creation request (POST 

), include the following parameters in the 

shipment.parcels[i].service_options.dangerous_goods.details.type

. Since each parcel can only contain one type of hazardous material, a multi-parcel shipment can be used to handle various hazmat materials and specify the appropriate hazmat code for each parcel.

Please note that although many customization options are generally available, they are dependent on the carrier's specifications and requirements. 

Each of these options is located in the main shipment body and should not be nested within any other object of the shipment request.

eHub can generate labels of different format types. 

For best label quality, we recommend using the 

Typically 4"x6" labels are used but eHub can generate labels with the following sizes. 

Each carrier has strict guidelines regarding their shipping labels. Please reach out to support@ehub.com before attempting to utilize this feature.

Some carriers allow you to split a shipment into multiple parcels by passing several parcel objects within the 

 array. If supported, you will receive multiple labels with different tracking numbers. 

To create FedEx OneRate shipments, you must specify both the eligible package type and the service in the shipment request body, based on the applicable contract

 corresponds to the FedEx OneRate contract, such as 

 is based on the relevant service (usually 

Use both the corresponding FedEx OneRate 

 to create a valid shipment request for a FedEx OneRate shipment:

Additional Tips

<p class="slate-p slate-indent-0" style="0px"></p><p class="slate-p slate-indent-0" style="0px">When a shipment is created, the API response will include a tracking number from the specified carrier.</p><p class="slate-p slate-indent-0" style="0px">With eHub's API there are two different ways to receive tracking events.</p><ol class="slate-ol " ><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Manually</strong></div><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">Make a GET request to <a href="https://app.theneo.io/ehub/ehub-api-test/shipments/retrieve-a-shipment" target="_self">/shipments</a> request to retrieve the shipment and all tracking events will be returned in the response.</div></li></ul></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Webhook</strong></div><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative"><a href="https://app.theneo.io/ehub/ehub-api-test/webhook-subscriptions/create-a-subscription" target="_self">Subscribe</a> to the shipment tracking webhook and receive tracking events as they are sent to eHub.</div></li></ul></li></ol><p class="slate-p " ></p><h3 class="slate-h3 " >Shipment Example <code class="slate-code">tracking_info</code> Array</h3><p class="slate-p " ></p><p class="slate-p " >The <code class="slate-code">tracking_info</code> array provides detailed information about the shipment's tracking status. This includes the shipment's current status, any updates on the shipment's location, and a list of tracking events that document the progress of the parcel through the carrier's network.</p><div class="code-block-wrapper"  style="width:60%" ><div class="code-block-header">Plain text</div><pre class="slate-CodeBlockElement slate-code_block" data-content=''><code class="language-json keep-markup drop-tokens"><div class="slate-code_line">"tracking_info": {</div><div class="slate-code_line">    "status": "manifested",</div><div class="slate-code_line">    "updated_at": "2024-08-16T12:00:00.000Z",</div><div class="slate-code_line">    "estimated_delivery_date": null,</div><div class="slate-code_line">    "delivery_date": null,</div><div class="slate-code_line">    "tracking_events": [</div><div class="slate-code_line">        {</div><div class="slate-code_line">            "event_date": "2024-08-16T12:00:00.000Z",</div><div class="slate-code_line">            "status": "manifested",</div><div class="slate-code_line">            "description": "Shipment information sent to FedEx (Processed by shipper and loaded in truck)",</div><div class="slate-code_line">            "city": "BUFFALO",</div><div class="slate-code_line">            "state": "NY",</div><div class="slate-code_line">            "postal_code": "14216",</div><div class="slate-code_line">            "country": "US"</div><div class="slate-code_line">        },</div><div class="slate-code_line">        {</div><div class="slate-code_line">            "event_date": "2024-08-16T08:13:57.000Z",</div><div class="slate-code_line">            "status": "manifested",</div><div class="slate-code_line">            "description": "Shipment information sent to FedEx",</div><div class="slate-code_line">            "city": null,</div><div class="slate-code_line">            "state": null,</div><div class="slate-code_line">            "postal_code": null,</div><div class="slate-code_line">            "country": null</div><div class="slate-code_line">        }</div><div class="slate-code_line">    ]</div><div class="slate-code_line">}</div></code></pre></div><h3 class="slate-h3 " >
Webhook Example <code class="slate-code">tracking_events</code> Array</h3><p class="slate-p " ></p><p class="slate-p " >The <code class="slate-code">tracking_events</code> array in the webhook response provides a real-time record of all tracking updates related to a shipment. Each event includes details such as the date, status, description of the event (e.g., "Out for Delivery"), and location information like city, state, postal code, and country. This allows you to monitor a shipment's journey as updates are received directly from the carrier.</p><div class="code-block-wrapper"  style="width:60%" ><div class="code-block-header">Plain text</div><pre class="slate-CodeBlockElement slate-code_block" data-content=''><code class="language-json keep-markup drop-tokens"><div class="slate-code_line">{</div><div class="slate-code_line">	"tracking_events": [</div><div class="slate-code_line">		{</div><div class="slate-code_line">			"event_date": "2021-08-06T10:06:00.000Z",</div><div class="slate-code_line">			"status": "available_for_pickup",</div><div class="slate-code_line">			"description": "Available for Pickup",</div><div class="slate-code_line">			"city": "MALTA",</div><div class="slate-code_line">			"state": "MT",</div><div class="slate-code_line">			"postal_code": "59538",</div><div class="slate-code_line">			"country": "US"</div><div class="slate-code_line">		},</div><div class="slate-code_line">		{</div><div class="slate-code_line">			"event_date": "2021-08-06T08:41:00.000Z",</div><div class="slate-code_line">			"status": "out_for_delivery",</div><div class="slate-code_line">			"description": "Out for Delivery, Expected Delivery by 9:00pm",</div><div class="slate-code_line">			"city": "MALTA",</div><div class="slate-code_line">			"state": "MT",</div><div class="slate-code_line">			"postal_code": "59538",</div><div class="slate-code_line">			"country": "US"</div><div class="slate-code_line">		},</div><div class="slate-code_line">		{</div><div class="slate-code_line">			"event_date": "2021-08-06T08:30:00.000Z",</div><div class="slate-code_line">			"status": "in_transit",</div><div class="slate-code_line">			"description": "Arrived at Post Office",</div><div class="slate-code_line">			"city": "MALTA",</div><div class="slate-code_line">			"state": "MT",</div><div class="slate-code_line">			"postal_code": "59538",</div><div class="slate-code_line">			"country": "US"</div><div class="slate-code_line">		}</div><div class="slate-code_line">	]</div><div class="slate-code_line">}</div></code></pre></div><p class="slate-p " ></p><p class="slate-p " ></p><p class="slate-p " ></p>

When a shipment is created, the API response will include a tracking number from the specified carrier.

With eHub's API there are two different ways to receive tracking events.

 array provides detailed information about the shipment's tracking status. This includes the shipment's current status, any updates on the shipment's location, and a list of tracking events that document the progress of the parcel through the carrier's network.

 array in the webhook response provides a real-time record of all tracking updates related to a shipment. Each event includes details such as the date, status, description of the event (e.g., "Out for Delivery"), and location information like city, state, postal code, and country. This allows you to monitor a shipment's journey as updates are received directly from the carrier.

Tracking

<p class="slate-p " ></p><p class="slate-p " >To create and ship a shipment all at once, you will need to use the Shipment Creation endpoint to buy and generate a label. Here’s how to structure the request, including the headers, parameters, and body data:</p><p class="slate-p " ></p><h3 class="slate-h3 " ><strong class="slate-bold">Key Elements</strong></h3><p class="slate-p " ></p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">shipment</strong>: The main object containing the shipment details.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">to_location</strong> and <strong class="slate-bold">from_location</strong>: The addresses of the sender and recipient.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">parcels</strong>: The details of the parcel(s), including dimensions, weight, and type.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">service_id</strong>: The ID of the shipping service you wish to use (can be retrieved via a rates request).</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">label_format</strong>: The format for the label (e.g., &quot;png&quot;, &quot;zpl&quot;).</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">label_size</strong>: The size of the shipping label (e.g., &quot;4x6&quot;).</div></li></ul><p class="slate-p " >Once you send this request, the API will return a response with the tracking number and the label, which you can use to ship the package.</p><p class="slate-p " ></p><div class="slate-div"></div><p class="slate-p " ></p><p class="slate-p " ></p><div class="slate-div"></div><p class="slate-p " ></p><p class="slate-p " ></p>

To create and ship a shipment all at once, you will need to use the Shipment Creation endpoint to buy and generate a label. Here’s how to structure the request, including the headers, parameters, and body data:

Once you send this request, the API will return a response with the tracking number and the label, which you can use to ship the package.

shipment

<p class="slate-p " ></p><p class="slate-p " >This endpoint allows you to create up to 10 shipments in a single request. It will buy and return labels for each shipment. The body of the request should be an array of shipment objects, formatted similarly to the <code class="slate-code">shipments/ship</code> endpoint.</p><p class="slate-p " ></p><h3 class="slate-h3 " ><strong class="slate-bold">Key Elements</strong></h3><p class="slate-p " ></p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">shipments</strong>: An array containing up to 10 shipment objects.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">shipment</strong>: Each shipment object includes <code class="slate-code">to_location</code>, <code class="slate-code">from_location</code>, <code class="slate-code">parcels</code>, and shipping service details.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">to_location</strong> and <strong class="slate-bold">from_location</strong>: Sender and recipient addresses for each shipment.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">parcels</strong>: Details of each package including dimensions, weight, and package type.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">service_id</strong>: Shipping service ID for the carrier.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">label_format</strong>: Specify the format for the label (e.g., &quot;png&quot;, &quot;zpl&quot;).</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">label_size</strong>: Size of the shipping label (e.g., &quot;4x6&quot;).</div></li></ul><p class="slate-p " >Once the request is sent, the API will return the tracking numbers and labels for each shipment in the array.</p><p class="slate-p " ></p><p class="slate-p " ></p><div class="slate-div"></div><p class="slate-p " ></p><p class="slate-p " ></p><div class="slate-div"></div><p class="slate-p " ></p><p class="slate-p " ></p>

Sections