> For the complete documentation index, see [llms.txt](https://docs.pandium.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pandium.com/connectors/connectors-101/shipbob.md).

# ShipBob

Set up the ShipBob connector in Pandium using OAuth 2.0 so tenants can authenticate securely and sync order fulfillment, inventory, shipping, and warehouse data.

## **Connector Overview**

<figure><img src="https://4017407078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MfJn-9R_dn6dvcGNcdk%2Fuploads%2Fgit-blob-22b19770fbb62b0e1cb43d72f728ea4226f99b6d%2Fshipbob-logo.png?alt=media" alt="" width="377"><figcaption><p>ShipBob</p></figcaption></figure>

ShipBob offers a complete fulfillment solution for ecommerce businesses, featuring strategically located centers and advanced tools for managing inventory, orders, and shipments to ensure faster delivery and lower costs.

## **Authentication Type**

OAuth2

## **Webhook Supported**

Yes

## **Secrets**

* PAN\_SEC\_SHIPBOB\_TOKEN\_TYPE
* PAN\_SEC\_SHIPBOB\_REFRESH\_TOKEN
* PAN\_SEC\_SHIPBOB\_ID\_TOKEN
* PAN\_SEC\_SHIPBOB\_EXPIRES\_AT
* PAN\_SEC\_SHIPBOB\_SCOPE
* PAN\_SEC\_SHIPBOB\_ACCESS\_TOKEN
* PAN\_SEC\_SHIPBOB\_EXPIRES\_IN

## **API Client Supported**

Yes

## **Requirements for Provisioning**

In order to provision your connector, the following ShipBob information must be gathered:

* API Base URL
* Client ID
* Client Secret
* Scopes

To obtain the information required for provisioning ShipBob Connector, perform the following steps:

1. Request a Client ID and Secret for your Application using the respective ShipBob [form](http://andrea.12.11.2024.qa.php).
2. Once approved, ShipBob will email you the ID and secret, as well as your approved API scopes.
3. Additional Requirements:
   1. Request [permission](https://developer.shipbob.com/auth/#step-2-request-permission-to-see-users-data) to see ShipBob user data
   2. Implement your [ShipBob Callback URI](https://developer.shipbob.com/auth/#step-3-implement-your-callback-uri)
   3. Obtain your ShipBob [access token](https://developer.shipbob.com/auth/#step-4-get-your-access-token)
   4. Get your [channel ID](https://developer.shipbob.com/auth/#step-5-get-your-channel-id)

## **How to Connect Your Integration**

Upon successfully creating a tenant, you will use the following information to connect to ShipBob:

* Username
* Password

## **API Resources**

For more information on how to utilize the ShipBob API, feel free to reference the following [documentation](https://developer.shipbob.com/).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pandium.com/connectors/connectors-101/shipbob.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.