Migrate from the deprecated ShipBob endpoint

ShipBob is planning to deprecate the Get Warehouse Receiving Order(DEPRECATED) endpoint, which has been replaced with the Get Warehouse Receiving Order endpoint in the Receiving API. Even though you can use the existing endpoint, all the ShipBob administrators should migrate the existing endpoint with the new endpoint at the earliest opportunity, in advance of the soon-to-be-announced deprecation date.

As part of this migration, Celigo will remove the deprecated endpoint Get Warehouse Receiving Order(DEPRECATED)from Receiving API in integrator.io with the 2023.3.1 release, scheduled for early March 2023. 

This article explains how to find the existing deprecated endpoint in the existing flows and replace it with the new endpoint.

Additional references:

• ShipBob API documentation
• ShipBob release notes

Note: When you encounter a deprecated endpoint, first copy the path parameter (Receiving ID)  to a reference document as a backup when replacing the endpoint, following the instructions in the next sections.

ShipBob replacement endpoint

The following table lists the deprecated endpoint:

Changes to make in integrator.io

A. Find the endpoint in the existing flows

To find an export that uses a ShipBob connection:

1. Sign in to your integrator.io account.
2. Navigate to Resources > Connections.
3. Search for an existing ShipBob connection. From the Actions overflow ... menu, select Used by. A list of all items that use this connection appears.
4. Right-click the first flow step in the list and select your browser’s option to open it in a new tab.
5. Replace the configuration for the deprecated endpoint with the endpoint provided in the table above.

Path parameters used in the deprecated operation

B. Update flows to use replacement endpoint

For each export that is using a deprecated API, find its corresponding replacement API in the chart below, and select the new API name and operation.

Example of export deprecated operation and the replacement operation

Find each export of the flows that use a ShipBob connection; if it has the endpoint mentioned [Deprecated] follow the steps and update accordingly:

If the existing export is configured as follows:

• API name: Receiving
• Operation:  Get Warehouse Receiving Order(DEPRECATED)

Export used in the deprecated operation

Then, convert it according to the above table, as follows, and as shown in the images below:

• API name: Receiving
• Operation:  Get Warehouse Receiving Order

Export used in the replacement operation