This article explains how to connect the ShipBob integration to iPaaS.com and what each subscription setting controls. Once connected, the integration captures ShipBob reference and inventory data into iPaaS.com — locations, location groups, shipping methods, product inventory, product variant inventory, and order tracking — and creates orders in ShipBob from iPaaS.com transactions.
How to Connect
Prerequisites
Before setting up the ShipBob integration in iPaaS.com, make sure you have the following information:
API URL: the base URL for your ShipBob environment:
Sandbox environment: https://sandbox-api.shipbob.com/1.0
Production environment: https://api.shipbob.com/1.0
Auth API URL: the ShipBob authorization base URL used to sign in and grant access during authentication. Unless you have been given a different value, use https://auth.shipbob.com.
Inventory Match Method: when ShipBob inventory is captured into iPaaS.com, this value tells the integration which ShipBob product value to use when finding the matching iPaaS.com SKU. Choose one of:
Sku
ReferenceId
Name
Use the same value when creating orders in ShipBob so their shipments reflect the matching identifier. Refer to the transaction line mappings for details. - ShipBob account credentials: the email and password for a ShipBob account with permission to authorize the integration and select a sales channel.
Configure Subscription Settings
Navigate to the ShipBob subscription settings in iPaaS.com and provide the following information.
Field | Description | Required | Example |
Name | A unique name for identifying the ShipBob subscription. | Yes | ShipBob Integration |
Version | The iPaaS.com integration version to use. | Yes | v1.0 |
API URL | The base URL for your ShipBob environment (sandbox or production). | Yes | |
Auth API Url | The ShipBob authorization base URL used during sign-in and access grant. | Yes | |
Inventory Match Method | The ShipBob product value used to find the matching iPaaS.com SKU when inventory is captured (Sku, ReferenceId, or Name). | No | Sku |
Personal Access Token | A ShipBob access token, used only when a subscription is configured to authenticate with a token instead of the standard sign-in flow. | No | Your Access Token |
Authentication Methods
The ShipBob integration authenticates using a standard sign-in and access-grant flow. You sign in to ShipBob, choose the sales channel the integration should write to, and approve the requested permissions. iPaaS.com then receives an access token and a refresh token, and the integration refreshes the access token automatically as it expires — you do not need to re-authenticate for routine use.
Follow these steps to authenticate the ShipBob integration:
Define the API URL and Auth API URL:
Navigate to the ShipBob subscription settings in iPaaS.com.
Enter the appropriate API URL for your environment (sandbox or production) and the Auth API URL as noted in the prerequisites.
Save your settings.
Navigate back to the settings page and click the authenticate button.
Authenticate with ShipBob:
A login prompt appears. Enter your ShipBob credentials (email and password) to proceed.
Select or Create a Sales Channel:
Choose an existing sales channel or create a new one.
Approve all permissions.
Note: iPaaS.com will only write data (for example, orders) to the selected channel. 4. Authorize Integration: 1. Confirm the connection by clicking Allow & Install.
2. On successful authorization, a confirmation message appears.
5. Refresh the iPaaS.com Subscription: 1. Refresh your iPaaS.com subscription settings page. 2. Confirm that an API Access Token and Refresh Token are displayed in the settings.
If authentication does not complete, confirm that the API URL and Auth API URL are correct for your environment and that your ShipBob account has permission to authorize the integration, then repeat the steps above. Any errors raised during a transfer appear in Dashboard / Integration Monitoring / Error Logs.
Initialization Support
The following types of data support initialization and can be transferred in bulk:
Location TO iPaaS.com
Location Group TO iPaaS.com
Shipping Method TO iPaaS.com
For record types that do not support bulk initialization, you can seed a larger set of existing records using bulk sync using Postman.
Throttling
Throttling keeps the ShipBob API from being overwhelmed by excessive requests, preserving performance during heavy data transfers.
While the throttling fields are required, their values are pre-populated by the integration settings. For more details, refer to Subscription Configuration – Edit.