Applied LabsDocs
Skip to Content

ShipBob Connector

Connect ShipBob so Applied can look up fulfillment context and run guided logistics workflows.

Use this Connector when support conversations depend on ShipBob orders, shipments, tracking details, inventory, or returns.

Common use cases

  • Look up ShipBob order and shipment status.
  • Check tracking details.
  • Inspect inventory details.
  • Cancel an order or shipment after approval.
  • Create or manage return workflows.

For operational actions like cancellation, use a Flow that confirms the order and captures approval before calling ShipBob.

Before you begin

Before connecting ShipBob, make sure:

  • You can access the ShipBob dashboard.
  • You know whether Applied should use production or sandbox.
  • You know which channel Applied should use for write workflows.
  • You know which scopes are required for orders, shipments, inventory, or returns.
  • You have a test order or shipment available for validation.

Get a ShipBob personal access token

ShipBob personal access tokens are created in the dashboard.

  1. In ShipBob, open Integrations.
  2. Go to API Tokens.
  3. Click Generate New Token.
  4. Name the token, such as Applied Labs.
  5. Select the scopes Applied needs.
  6. Generate and copy the token.

Applied uses the token as a bearer token.

Choose ShipBob scopes

ShipBob scopes control read and write access. Common scopes include:

  • orders_read for order lookups.
  • orders_write for order changes.
  • returns_read for return lookup.
  • returns_write for return creation or updates.
  • products_read and inventory_read for product and inventory context.
  • webhooks_read and webhooks_write only if webhook management is required.

For write workflows, ShipBob recommends using a channel whose scopes include the matching _write permissions. Keep the channel ID available if Applied support asks for it.

Connect ShipBob in Applied

  1. Open Connectors.
  2. Click New.
  3. Choose ShipBob.
  4. Paste the ShipBob personal access token into the API token field.
  5. Enter a channel ID if your setup requires channel-scoped write actions.
  6. Create the connection.

Production ShipBob API calls use https://api.shipbob.com. Sandbox calls use https://sandbox-api.shipbob.com when your setup is configured for sandbox.

Validate the connection

After setup:

  1. Look up a test order or shipment.
  2. Confirm status, tracking, and order IDs match ShipBob.
  3. If write actions are enabled, test with a sandbox or disposable order.
  4. Confirm the action appears in ShipBob.

Common issues

ShipBob says the token is unauthorized

Confirm the token is active and has the required scope for the endpoint Applied is calling.

Reads work, but writes fail

Add the matching _write scope and confirm the channel ID is allowed to perform that action.

Sandbox and production data do not match

Check which API base URL your Connector is using. Sandbox and production tokens and data are separate.

Provider docs

Next steps

Last updated on
Loop Returns ConnectorRecharge Connector